agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/exa-people-research/SKILL.md

exa-people-research

Skill9 starsChanged 6 months agoMITView on GitHub

People research using Exa search. Finds LinkedIn profiles, professional backgrounds, experts, team members, and public bios. Use when searching for people, finding experts, or looking up professional profiles.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call the native MCP tool exa-search__web_search_advanced_exa directly.

    line 11
  2. Very specific:

    Do NOT use: startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, excludeDomains, includeText, excludeText.

    line 30
  3. Very specific:

    If content is auth-gated (private LinkedIn, etc.) → use browser tool with logged-in session.

    line 61

≈ “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

People Research (Exa)

Tool

Call the native MCP tool exa-search__web_search_advanced_exa directly. Parameters go in a JSON object.

Critical Rules

  • Never run searches in main context. Spawn subagents or run sequentially.
  • Query variation: 2-3 phrasings, run in parallel, deduplicate.
  • Dynamic numResults: "a few" → 10-20, "comprehensive" → 50-100.

Categories

CategoryUse for
peopleLinkedIn profiles, public bios (primary)
personal siteBlogs, portfolios, about pages
newsPress mentions, interviews, speaker bios
(none)General web, broader context

Restrictions with category=people

Do NOT use: startPublishedDate, endPublishedDate, startCrawlDate, endCrawlDate, excludeDomains, includeText, excludeText. includeDomains → LinkedIn only: ["linkedin.com"].

Call Examples

Tool: exa-search__web_search_advanced_exa

# Find people by role
{ query: "VP Engineering AI infrastructure", category: "people", numResults: 20, type: "auto" }

# Deep dive on specific person
{ query: "Dario Amodei Anthropic CEO background", type: "auto", livecrawl: "fallback", numResults: 15 }

# News mentions
{ query: "Dario Amodei interview 2024", category: "news", numResults: 10, startPublishedDate: "2024-01-01" }

# LinkedIn only
{ query: "Machine learning engineer San Francisco", category: "people",
  includeDomains: ["linkedin.com"], numResults: 25 }

Output Format

Return:

  1. Results — name, title, company, location (if available)
  2. Sources — profile URLs
  3. Notes — profile completeness, verification status

Browser Fallback

If content is auth-gated (private LinkedIn, etc.) → use browser tool with logged-in session.

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.