agentleFS
LeadMagicLeadMagic/leadmagic-skills/skills/people-search/SKILL.md

people-search

Skill0 starsChanged 4 months agoMITView on GitHub

LeadMagic People Search v3 via POST /v3/people/search and its variants (employees, by-title, lookalike, ICP). Use when building audiences or ICP lists, filtering by job function, title, level, company, or geo, sizing a segment for free before revealing rows, or debugging empty or unexpected people search results. For the one person holding a specific role at a company, use Role Finder first (people-enrichment).

  • Reads credentials
  • Sends data out

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Never combine cursor with a nonzero offset — the API rejects it, and next_cursor is only minted on the offset-0 form.

    line 67
  2. Very specific:

    Stop when next_cursor is null / has_more is false.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

LeadMagic — People Search (v3)

Canonical discovery endpoint: POST /v3/people/search. Same body shape on the variants: /v3/people/company-search, /full-search, /mixed-search, /icp-search, /employees, /by-title, /contacts-by-title, /lookalike.

Docs: People Search

Billing & plan awareness

  • 1 credit per returned result row. Free on Professional (≤5 req/s) and Ultimate (≤10 req/s) — their plans include credit-free Search API throughput.
  • Size before revealing (free on every plan): POST /v3/search/stats with the same filters returns match counts. On Basic–Growth, always size first and keep per_page small.

Request

curl -sS -X POST "https://api.leadmagic.io/v3/people/search" \
  -H "X-API-Key: $LEADMAGIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_filters": { "company_domain": ["acme.com"] },
    "people_filters": {
      "contact_job_function": ["Sales"],
      "contact_job_level": ["Director", "VP"]
    },
    "page": 1,
    "per_page": 25
  }'

Filter families

FamilyExamples
Companycompany_domain, company_name, company_industry, company_size/company_sizes, company_country/company_countries, funding
Rolecontact_job_title, contact_job_function, contact_job_level, contact_persona, min_seniority
Personname fields, B2B Profile URL/username, headline, contact_email_domain

Company filter aliases (normalized server-side):

Client aliasCanonical
company_size / company_sizes / employee_countemployee_ranges (+ min_employees / max_employees)
employee_min / employee_maxmin_employees / max_employees
company_country / company_countrieshq_country_code (ISO)

Title matching: "VP Sales" is substring/FTS. Wrap in brackets for exact title equality — "[VP of Sales]" / "[CEO]". Mixed arrays allowed. For list totals, pass include_total: true (capped COUNT on supported paths).

Cursor pagination

  • First page: filters + limit (≤50 on cursor pages). No cursor; offset 0 or omitted.
  • Response carries next_cursor (opaque, ≤4096 chars) and has_more.
  • Next page: same filters + "cursor": "<next_cursor>". Changing filters mid-cursor invalidates it.
  • Never combine cursor with a nonzero offset — the API rejects it, and next_cursor is only minted on the offset-0 form. If you were paging by offset, restart at offset 0.
  • Stop when next_cursor is null / has_more is false. Dedupe rows on person_uid.

Job function (contact_job_function)

  • Accepts short names (Sales, Marketing, Product) or full canonical labels (Sales & Business Development).
  • Matching is exact after short-name expansion (not substring). "Product" does not match "Manufacturing & Production".
  • Response rows always return the canonical label (request Sales → response Sales & Business Development). Expected.
RequestLabel returned
SalesSales & Business Development
MarketingAdvertising & Marketing
ProductProduct Management
EngineeringEngineering

When not to use this skill

  • Single-person email / mobile / profile lookup → email-enrichment or people-enrichment
  • Company firmographics or company lists → company-enrichment
  • CSV enrichment of known rows → bulk-jobs
  • Full list-build recipe with dedupe + waterfall → outbound-recipes

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.