agentleFS
Sign inStart free
Reload-AppsReload-Apps/deepsearch-mcp/skills/deep-search/SKILL.md

deep-search

Skill1 starsChanged 3 months agoMITView on GitHub

Research a person's public online footprint from a name, phone, email, or username. Use when looking up people, building a sourced dossier, or asking a specific question about someone. Public web only; never for employment, credit, housing, or insurance decisions.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. tarsluna/my-custom-skills★ 9same name
    2. chenghaoYang/parallel-search-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Look up real people from a name, phone, email, or username using the hosted Deep Search MCP tools.

    line 8
  2. Distinctive:

    Do not use this skill for surveillance, stalking, or harassment.

    line 15
  3. Very specific:

    Search first: Call search_people with one identifier (name, phone, email, or username).

    line 19
  4. Distinctive:

    Pick a person: If several candidates look plausible, show them and ask the user which one.

    line 20
  5. Distinctive:

    If a tool result says the user must sign in, subscribe, or add credits, relay that message and its URL, then retry after they finish.

    line 29
  6. Distinctive:

    Prefer sourced claims. When a dossier or answer includes a source URL, keep it.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep Search

Look up real people from a name, phone, email, or username using the hosted Deep Search MCP tools. Public web sources only.

When to use

  • Journalism, reconnecting with someone, or business research that is not for hiring, credit, housing, or insurance decisions
  • The user gives a name, phone, email, or username and wants candidates, a sourced profile, or one fact

Do not use this skill for surveillance, stalking, or harassment. Do not use it to make employment, credit, housing, or insurance decisions. Deep Search is not a consumer reporting agency and its output is not a consumer report.

Workflow

  1. Search first. Call search_people with one identifier (name, phone, email, or username). It returns ranked, distinct people with confidence scores — not pages to reconcile yourself.
  2. Pick a person. If several candidates look plausible, show them and ask the user which one. Do not merge same-name results into one person.
  3. Then dossier or ask.
    • build_dossier — full public footprint: identity, contact, social accounts, work, education, relatives, locations, web mentions. Every claim is linked to a source page.
    • ask_about_person — one specific question, cheaper than a full dossier. Use this when the user wants a single fact.

Auth and billing

The plugin connects to https://deepsearch.app/api/mcp (streamable HTTP). Claude Code discovers OAuth 2.1 and dynamic client registration automatically. No API key belongs in this plugin.

  • If a tool result says the user must sign in, subscribe, or add credits, relay that message and its URL, then retry after they finish.
  • A 401 means the token is missing, expired, or invalid — tell the user to re-authorize via /mcp (Claude Code) or the plugin connector page (Cowork).
  • Optional API keys (dsk_…) are created at https://deepsearch.app/api. Do not invent or request that the user paste a key into chat unless they choose that path.

Output

Prefer sourced claims. When a dossier or answer includes a source URL, keep it. People can opt out at https://deepsearch.app/remove-my-info.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free