agentleFS
Sign inStart free
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/person-lookup/SKILL.md

person-lookup

Skill9 starsChanged 6 months agoMITView on GitHub

Look up a person's background: work history, education, social profiles, contact info. Use when asked 'who is [person]?' or need to research someone before a meeting. For finding their email specifically, see find-email-by-name. For enriching a lead with full contact data, see lead-enrichment.

1 other project uses a version of this.

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, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Before helping, check MEMORY.md for current contacts and relationships.

    line 9
  2. Distinctive:

    Use LinkedIn URL if available for exact match

    line 37
  3. Distinctive:

    If researching before a meeting, add:

    line 62

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

[YOUR_PRODUCT] Context

Before helping, check MEMORY.md for current contacts and relationships. Output in Russian (names, titles, company names in original). For chat platforms: bio-style summary, not raw data dump.

Person Lookup

Find detailed background on a person: work history, education, social profiles, contact info.

Usage

Search by Name + Company (Nyne)

orth run nyne /person/search -d '{"query": "FULL_NAME COMPANY"}'

NOTE: Nyne searches are async. The POST returns a request_id. Poll with:

orth run nyne /person/search -q request_id=REQUEST_ID

Retry every 3-5 seconds until status is complete. Usually takes 5-15 seconds.

Search Tips

  • Include company name: "Dario Amodei Anthropic"
  • Include title for common names: "John Smith CTO Acme"
  • Use LinkedIn URL if available for exact match

Response Fields

  • Full name and current title
  • Current employer and role
  • Work history (previous companies, roles, dates)
  • Education (schools, degrees)
  • Location
  • Social profiles (LinkedIn, Twitter)
  • Skills and expertise

Output Format

**[Name]** — [Current Title] @ [Current Company]

Background:
- Previously: [role] @ [company] ([years])
- Education: [school], [degree]
- Location: [city]

Profiles: [LinkedIn], [Twitter]

If researching before a meeting, add:

Meeting prep notes:
- [relevant background detail]
- [shared connection or interest]
- [topic to discuss]

Error Handling

  • Async timeout — if no result after 30 seconds, report partial data
  • Multiple results — add company or title to narrow down
  • No results — try alternate name spelling, or use Fiber people-search as fallback:
orth run fiber /v1/people-search -d '{"searchParams": {"full_name": "FULL_NAME", "company_names": ["COMPANY"]}}'

Related Skills

  • meeting-prep — pre-meeting briefings combining person + company + pipeline context
  • find-email-by-name — find their email address
  • lead-enrichment — full contact enrichment (email + phone + company)
  • company-intel — research their company
  • exa-people-research — web-based person research via Exa
  • sales-qualification — qualify them as a lead

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