anysite-people-sourcing
Source people in bulk from Anysite's LinkedIn profile database (search_sql_users) with ~60 filters - derived seniority/function, company domain/id incl. past employers (alumni), career-shape (new in role, tenure, promotions), education, skills, deterministic territory buckets. Use when the user wants to find people in bulk - persona lists, buyers/candidates by role and company traits, competitor alumni, "new VP hires", recruiting searches - "найди людей", "собери список персон", "кто недавно сменил работу". For company lists first use anysite-company-sourcing; for one known person use linkedin/user; for CRM push use anysite-crm-prospect.
Install
With your agent
Install OMGSkills skill "anysiteio/agent-skills:plugins/anysite-gtm/skills/anysite-people-sourcing" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/anysiteio/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/plugins/anysite-gtm/skills/anysite-people-sourcing ~/.claude/skills/anysite-people-sourcing
From README
People Sourcing linkedin/search/sql/users (endpoint searchsqlusers) searches a very large profile database with filters no live LinkedIn search has: derived seniority and function, career-shape maths (tenure, promotions, months in role), past-employer alumni, company domains and deterministic bucketing. It is the bulk people workhorse; live searchusers stays the tool for one-off lookups and namesake disambiguation. Verified live: filters compose correctly (senioritymin=head + function=sales + US + 51–500 headcount + new-in-role returned exactly that, role histories fresh to the current quarter; alumni via pastcompanyid returns people whose role at that company has an end date, never current staff). Two semantics that change how you work An over-count result is an unbiased SAMPLE, and repeating the request returns the SAME people (verified: two identical calls → identical 5 aliases; and raising count only appends — the list is prefix-stable, not reshuffled).
More from this repo
anysite-buying-committee
Map the buying committee at one target account - economic buyer, champion candidates, technical evaluators, users and...
anysite-company-sourcing
The craft of sourcing companies from Anysite's 70M+ LinkedIn company database (search_sql_companies) - turning a fuzzy...
anysite-crm-account-brief
Pre-meeting brief for an account that lives in the connected CRM - what the CRM already knows (fields, contacts,...
