find-anyone

Build a sourced, corroborated profile of a named individual from public records and social platforms.

38|2|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/UseOSINT/Skills --skill find-anyone-useosint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-anyone
Source: https://github.com/UseOSINT/Skills/tree/main/skills/find-anyone
Command: npx skills add https://github.com/UseOSINT/Skills --skill find-anyone-useosint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigating a person by name alone produces confident dossiers that fuse two different people into one. This Skill enforces a disciplined OSINT workflow that anchors a name to a second selector before collecting anything, then corroborates every claim against independent sources. ## Core Features & Use Cases - Identity disambiguation: Bind the name to an employer, city, photo, email, or age band before searching, and maintain a documented candidate set so namesakes are split out rather than merged. - Layered source workflow: Work through professional records, published output, licensing registers, corporate filings, court and property records, social accounts, data brokers, and web archives in a cheapest-first order. - Confidence grading: Grade every claim as confirmed, probable, unconfirmed, or rejected, with identity attribution graded separately from the claim itself. - Use Case: Run pre-investment due diligence on a named CTO by anchoring to the employer, pivoting through conference bios and corporate officer records, and flagging an uncorroborated prior-employer claim as a diligence question. ## Quick Start Ask the agent to build a sourced profile of a named person, providing the name plus one anchor such as their employer or city, and state the lawful objective and out-of-bounds limits.

Frequently Asked Questions about find-anyone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a person online using public records?▼

Start by anchoring the name to a second selector such as an employer, city, or email, then work through professional profiles, licensing registers, corporate filings, and court records in that order. Record a source URL and access date for every claim and require two independent sources before calling anything confirmed.

How do I avoid confusing two people with the same name?▼

Define a discriminating test up front, such as employer plus city plus age band, and apply it to every candidate record. Maintain a documented candidate set, split records that fail the test into separate candidates, and watch for conflicting middle initials, implausible locations, or overlapping full-time roles.

What sources verify someone's employment and credentials?▼

Licensing and professional board registers are the strongest credential check, since they are primary records with status and disciplinary history. Employer pages, press releases, and conference programmes confirm roles at a date, while ORCID, patents, and court or corporate filings add independent corroboration.

Can data broker sites be used for background checks?▼

Data broker aggregators should be used last and only as leads, because they resell each other's data and propagate errors that then look corroborated. In the US, using aggregator data for employment, tenancy, insurance, or credit decisions outside a regulated consumer reporting agency is a compliance violation.

Is it legal to profile a person from public information?▼

In the EU and UK, profiling a living person is processing personal data and requires a lawful basis such as journalism, legal claims, or legitimate interests, each with distinct limits. The Skill requires a written scope with a lawful objective and explicit out-of-bounds list before any searching begins.

Why does a person search return no results?▼

A sparse footprint can mean a private person, a non-English or non-Latin-script presence, a recent name change, or closed registries, and it is not evidence of concealment. Search native-script spellings and transliterations, check archived pages for removed bios, and consider that a tidy, shallow footprint may indicate a synthetic identity.