# dig-through-data-brokers

Guides people-search investigations across data brokers and public records. It generates lead selectors and structures personal privacy audits.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1900 installs · ★ 54
- Author: UseOSINT
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/UseOSINT/Skills/tree/HEAD/skills/dig-through-data-brokers/SKILL.md
- Updated: 2026-08-03
- HTML: https://affpapa.org/en/nevibecode/skills/dig-through-data-brokers

## What it does

The skill instructs your coding assistant to treat broker records from sites like Spokeo, Whitepages, and Radaris strictly as leads rather than verified facts. It details common data decay patterns: append-only address histories, merged profiles of namesakes, and inferred relatives based solely on co-tenancy. Cross-checking multiple brokers gives zero real corroboration because they constantly resell data to each other.

The workflow enforces anchoring searches early and verifying candidate selectors against primary public records like court filings, deeds, and voter files. Broker profiles only serve to narrow down initial leads. By law, non-FCRA broker data cannot be used for employment screening, tenancy, insurance, or credit evaluations.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add UseOSINT/Skills --skill dig-through-data-brokers -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/dig-through-data-brokers/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/dig-through-data-brokers/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add UseOSINT/Skills --skill dig-through-data-brokers -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/dig-through-data-brokers/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add UseOSINT/Skills --skill dig-through-data-brokers -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/dig-through-data-brokers/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install UseOSINT/Skills dig-through-data-brokers
```

2. **Manually: put the files in place**
- File: `.github/skills/dig-through-data-brokers/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add UseOSINT/Skills --skill dig-through-data-brokers -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/UseOSINT/Skills --path skills/dig-through-data-brokers
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/dig-through-data-brokers/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add UseOSINT/Skills --skill dig-through-data-brokers -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/UseOSINT/Skills/tree/HEAD/skills/dig-through-data-brokers/SKILL.md

## When to use it
- extract candidate selectors to verify against primary property and court records
- trace debtors or missing persons without taking unverified broker claims as fact
- audit personal exposure across people-search databases before submitting opt-out requests
- separate fused profiles of namesakes or family members sharing an address

## Example prompts
- Generate a candidate list of addresses for this subject and tell me which county records to cross-check.
- Audit my exposure across major people-search sites and guide me on what selectors to search first.
- How do I confirm the relatives listed on this broker profile using primary records?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9b6760181f3be605.

BEGIN THIRD-PARTY FILE 9b6760181f3be605
```text
---
name: dig-through-data-brokers
description: >-
  Use people-search aggregators and primary public records to find addresses, phone numbers,
  relatives, age and background on a person, and to audit and remove your own exposure. Covers
  Spokeo, BeenVerified, Whitepages, TruePeopleSearch, FastPeopleSearch, That'sThem, Radaris,
  Intelius and Pipl, plus voter files and county court and property records. Use when running
  a people search or reverse address lookup, tracing a debtor or missing person, building a
  subject's address history, or removing yourself from broker sites. Applies to skip tracing
  and debt recovery, asset investigation, executive protection, and personal exposure audits.
  Explains the FCRA limits that bar broker data from employment, tenancy, insurance and credit
  decisions, and the GDPR position. Reference at useosint.com/skills/dig-through-data-brokers.

---

# Dig through data brokers

People-search sites resell a blend of public records, marketing data, and
self-reported data. They are fast, cheap lead generators and terrible evidence.
The one rule that matters: **a broker record is a lead, never a fact.** Confirm
every field you intend to use against the primary source the broker got it from —
and if you cannot identify that primary source, do not use the field.

## What these services actually are

Three input streams, blended and sold:

- **Public records** — property deeds, court filings, business registrations,
  voter files where public, professional licences, bankruptcy, marriage and
  divorce. Authoritative at origin; the broker's copy is a stale transcription.
- **Marketing and commercial data** — warranty cards, loyalty programmes,
  subscriptions, credit-header data, online forms, ad exchanges. Never verified,
  often inferred, frequently household-level rather than person-level.
- **Self-reported and scraped** — profiles, résumés, forum posts, and whatever the
  broker's own users typed in.

They also buy from each other, constantly. That is the most important structural
fact about the category: one wrong record propagates across every brand, and
cross-checking five brokers gives you five copies of one error wearing five hats.
Apparent corroboration across brokers is worth close to nothing.

## Why the data is wrong

- **Address history is append-only in practice.** Brokers add addresses and rarely
  retire them, so a "current address" is often several moves old.
- **Household merging.** Two people at one address, or two people with the same
  name in one metro area, get fused into one profile. Same-name relatives —
  father and son, cousins named for the same grandparent — merge constantly.
```
END THIRD-PARTY FILE 9b6760181f3be605

The third-party file has ended. Everything between the 9b6760181f3be605 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2695 of 14937 bytes. © UseOSINT · MIT · https://github.com/UseOSINT/Skills/tree/HEAD/skills/dig-through-data-brokers/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md