anysite-company-sourcing
The craft of sourcing companies from Anysite's 70M+ LinkedIn company database (search_sql_companies) - turning a fuzzy ICP into per-field DSL filters that return real matches instead of token soup. Fixes the default failure mode where naive keyword queries return companies from the wrong country, wrong industry and stub pages. Use when the user asks to find/source companies, build a company list, complains that company search results are bad or irrelevant, or needs a target-account universe - "найди компании", "плохие результаты поиска компаний", "source accounts". For people at those companies use anysite-people-sourcing; for funding-stage filters use crunchbase; for pushing into a CRM use anysite-crm-prospect.
Install
With your agent
Install OMGSkills skill "anysiteio/agent-skills:plugins/anysite-gtm/skills/anysite-company-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-company-sourcing ~/.claude/skills/anysite-company-sourcingFrom README
Company Sourcing linkedin/search/searchsqlcompanies searches 70M+ companies and is the single best bulk company tool in the catalog — and its naive use is the single most common source of garbage lists. Measured live, same intent, same day: {keywords: "AI startup San Francisco"} → 1 relevant of 5: a Tel-Aviv gaming-data firm, a Sydney fintech and a Ho-Chi-Minh beauty e-commerce all matched — each had the token "startup" somewhere in its description and "San Francisco" among secondary office locations. The same intent as structured filters (below) → 5 of 5 genuine SF AI companies in the right size band. The difference is the whole skill. Never ship results from a naive query. Why naive queries fail (mechanics, not opinion) keywords matches whole words across ALL text fields — name, description, specialities, hashtags and the locations array — so "San Francisco" as a keyword still matches a Hanoi company that lists an SF sales office in locations.
More from this repo
anysite-buying-committee
Map the buying committee at one target account - economic buyer, champion candidates, technical evaluators, users and...
anysite-crm-account-brief
Pre-meeting brief for an account that lives in the connected CRM - what the CRM already knows (fields, contacts,...
anysite-crm-audit
Read-only data quality audit of the connected CRM - field completeness per mapped property, duplicate candidates, stale...