Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

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 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add UseOSINT/Skills --skill find-anyone

About this skill


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 holdFirst moveWhy
Name + employerProfessional network, company bios, press releasesEmployment is the strongest cheap anchor; it dates the person and gives a city
Name + city/regionLocal records — property, court, voter file where public, local pressGeography prunes namesakes fastest
Name + a photofind-the-original-image, then secrets-in-file-metadataA face survives name changes and transliteration
Name + email or handlewhat-an-email-reveals, hunt-a-handleMachine-unique selectors; skip disambiguation almost entirely
Name + approximate ageGenealogy, obituaries, licensing recordsAge bands split same-name clusters cleanly
Name onlyStop. Go back to the requesterA 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.

  1. 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.
  2. Published output. Bylines, papers, patents, standards contributions. Use google-like-a-spy with site: 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.
  3. 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.
  4. Corporate record. who-really-owns-it for directorships and shareholdings. The officer-name pivot is the highest-yield single step for anyone with business involvement.
  5. Public legal and property records. Court dockets, judgments, insolvency, and land registers — where and only where public in that jurisdiction.
  6. Social and behavioural. hunt-a-handle to enumerate accounts, then pattern-of-life-from-socials. Deliberately late: noisiest layer, easiest to misattribute.
  7. Aggregators. dig-through-data-brokers, last, and only for leads you then confirm against a layer above.
  8. Historical. read-deleted-pages for 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

Read the complete source ↗