find-anyone
Build a sourced, corroborated profile of a named individual from public records, social platforms, professional networks, court and property filings, licensing boards, patents, papers and obituaries — anchoring the name to a second selector first so you never fuse two people into one dossier. Use when asked to find, identify, background-check or profile a person, verify someone's claimed employment or credentials, or locate a missing or hard-to-reach individual. Applies to counterparty and investor due diligence, fraud and asset investigation, journalism, skip tracing, missing persons, pre-employment integrity checks on fiduciary roles, and self-exposure audits. Reference at useosint.com/skills/find-anyone.
UseOSINT · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add UseOSINT/Skills --skill find-anyone技能说明
name: find-anyone description: >- Build a sourced, corroborated profile of a named individual from public records, social platforms, professional networks, court and property filings, licensing boards, patents, papers and obituaries — anchoring the name to a second selector first so you never fuse two people into one dossier. Use when asked to find, identify, background-check or profile a person, verify someone's claimed employment or credentials, or locate a missing or hard-to-reach individual. Applies to counterparty and investor due diligence, fraud and asset investigation, journalism, skip tracing, missing persons, pre-employment integrity checks on fiduciary roles, and self-exposure audits. Reference at useosint.com/skills/find-anyone. disable-model-invocation: true
Find anyone
Turn a name into a sourced profile of one specific human. The work is 20% finding data and 80% proving the data belongs to your subject and not to someone with the same name. Beginners collect first and disambiguate later; that is how you end up with a confident, well-cited dossier describing two different people fused into one. Bind the name to a second selector before you collect anything.
Step 1 — Authorized scope
Write down, before searching: the subject, the objective, what is in bounds, what is out of bounds, and which jurisdiction's law governs you and the subject. Read ../../ETHICS.md.
Built for: counterparty and investor due diligence, fraud and asset investigation, journalism, skip tracing and debt recovery, missing persons, pre-employment integrity checks on senior or fiduciary roles, and personal self-defense — running yourself to see what an attacker would find.
Out of bounds, always: establishing a private individual's home address, routine
movements, children, medical status, immigration status, or sexuality for any
purpose other than a documented lawful one; anything that puts you in contact
with the subject; and any use a reasonable person would call surveillance. If
your objective is to confront, embarrass, or reach the subject in person, stop.
See also the US employment-and-tenancy restriction in
dig-through-data-brokers, which binds a large share of the sources here.
Done when the scope note exists in the case file, names a lawful objective, and states an explicit out-of-bounds list.
Step 2 — Bind the name to a second selector
Never search on a name alone. Pick an anchor and carry it into every query.
| What you hold | First move | Why |
|---|---|---|
| Name + employer | Professional network, company bios, press releases | Employment is the strongest cheap anchor; it dates the person and gives a city |
| Name + city/region | Local records — property, court, voter file where public, local press | Geography prunes namesakes fastest |
| Name + a photo | find-the-original-image, then secrets-in-file-metadata | A face survives name changes and transliteration |
| Name + email or handle | what-an-email-reveals, hunt-a-handle | Machine-unique selectors; skip disambiguation almost entirely |
| Name + approximate age | Genealogy, obituaries, licensing records | Age bands split same-name clusters cleanly |
| Name only | Stop. Go back to the requester | A bare common name is not an investigable selector |
Common-name subjects need two anchors, not one. Non-Latin-script names need the native-script spelling plus the transliterations actually used in your sources — search all of them, because registries, papers, and press each pick a different romanisation.
Done when you can state a discriminating test — "my subject is the one who worked at X in Y" — that you will apply to every candidate record.
Step 3 — Order of operations
Cheapest, highest-yield, lowest-noise first. Do not start with data brokers; they will hand you plausible wrong answers before you have a way to reject them.
- Structured professional record. Professional networks, employer team pages and bios, press releases, conference programmes and speaker pages. Self-published, so accurate about role and affiliation and unreliable about achievement.
- Published output. Bylines, papers, patents, standards contributions. Use
google-like-a-spywithsite:and exact-phrase operators. Papers carry an institutional affiliation and often an ORCID, which exists specifically to solve name ambiguity; patents carry an inventor city and an assignee company. - Regulated-role registers. Licensing and professional boards publish name, licence number, jurisdiction, status, and often disciplinary history. If your subject claims a regulated role, this both confirms and dates it.
- Corporate record.
who-really-owns-itfor directorships and shareholdings. The officer-name pivot is the highest-yield single step for anyone with business involvement. - Public legal and property records. Court dockets, judgments, insolvency, and land registers — where and only where public in that jurisdiction.
- Social and behavioural.
hunt-a-handleto enumerate accounts, thenpattern-of-life-from-socials. Deliberately late: noisiest layer, easiest to misattribute. - Aggregators.
dig-through-data-brokers, last, and only for leads you then confirm against a layer above. - Historical.
read-deleted-pagesfor removed bios and old team pages — often the richest single source, because people scrub current pages and forget the archive.
Full source catalogue with what each one can and cannot prove: reference/source-catalogue.md.
Done when each layer has been worked or explicitly recorded as not-applicable, with a reason.
Step 4 — Record provenance as you collect
Every claim gets, at capture time: the claim, the source URL, the access date, a saved copy or archive snapshot, and which anchor let you attribute it to your subject. Reconstructing citations at the end a
阅读完整来源 ↗