anysite-buying-committee
Map the buying committee at one target account - economic buyer, champion candidates, technical evaluators, users and blockers (legal, security, procurement, finance) - from the 856M-profile database and live profiles, cross-checked against the CRM, with recently appointed people flagged, coverage gaps and single-thread risk called out, and an order to engage them. Use when the user asks who to talk to at a company, who the decision makers are, to multi-thread a deal, map stakeholders or an org chart for a sale, or prepare account-based outreach - "кто принимает решение", "карта ЛПР", "buying committee", "stakeholder map". For a pre-meeting brief use anysite-crm-account-brief; for people across many companies use anysite-people-sourcing.
Install
With your agent
Install OMGSkills skill "anysiteio/agent-skills:plugins/anysite-gtm/skills/anysite-buying-committee" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, 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-buying-committee ~/.claude/skills/anysite-buying-committeeFrom README
Buying Committee B2B deals are decided by several people, and a deal that runs through one contact dies when that person goes quiet or leaves. This skill maps who is likely in the room at ONE account, what role each plays, and where the gaps are — so the user reaches the right people in the right order. Step 0 — Purpose and hypotheses Ask (or take from the request) what the map is for: a new-logo pursuit, an open deal that stalled, an expansion. Take the personas and the "role in the deal" from anysite-gtm-profile when it exists. If the user names people they believe matter ("the CFO signs", "Anna is our champion"), write each down as a hypothesis — the map reports every one as confirmed, contradicted or unresolved. Step 1 — Resolve the account companies/resolve {website: , count: 3} → the right candidate → company: (anysite-mcp → Domain → company). Company name only → resolve the domain first; never map a namesake.
More from this repo
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,...
anysite-crm-audit
Read-only data quality audit of the connected CRM - field completeness per mapped property, duplicate candidates, stale...