Agent skill
gtm-buying-committee-map
Map the buying committee at a target account and get verified emails for the people who matter.
Filed under CRM and RevOps.
From loootai/gtm-skills · 15 skill entries · 0 · pushed 2026-10-08
What it does when it runs
Map the buying committee at a target account and get verified emails for the people who matter. Use when the user says "who should I contact at acme.com", "map the buying committee", "find the decision makers at these accounts", "multi-thread this deal", "who signs off on a CRM at Acme". Searches people by role at the domain, picks one to three per role, finds and verifies their work emails through looot, about $0.02 to $0.05 per account.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- api.looot.ai
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/loootai/gtm-skills.git /tmp/gtm-skills git -C /tmp/gtm-skills sparse-checkout set "skills/gtm-buying-committee-map" mkdir -p ~/.claude/skills/gtm-buying-committee-map cp -R "/tmp/gtm-skills/skills/gtm-buying-committee-map/." ~/.claude/skills/gtm-buying-committee-map/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from loootai/gtm-skills/blob/1cb22eede6829b8f9fa87a78e6957a97e4032bd5/skills/gtm-buying-committee-map/SKILL.md, which is licensed MIT (repository). 553 words, 9 headings.
Buying committee map
Deals with one contact stall. This skill finds the people behind each role in a purchase (economic buyer, champion, user, technical evaluator) at an account, and returns them with verified emails and a short note on why each one is on the map.
Needs looot connected (MCP server https://api.looot.ai/mcp, or the looot skill from npx skills add loootai/looot-skills). Searching and inspecting are free; runs are paid from the prepaid balance.
Ask for these inputs
- Account domains (1 to 50).
- What the user sells, so the roles fit. Example for a sales tool: economic buyer = VP Sales or CRO, champion = Sales Ops or RevOps lead, user = SDR or AE manager, technical = Sales Systems or IT.
- How many people per role (default 1, max 3).
Steps and prices
Prices are the cheapest live provider in the public looot catalog on 2026-10-08. inspect shows the live price.
| # | Job id | Input | Price on 2026-10-08 |
|---|---|---|---|
| 1 | people.search | domain plus a query per role ("VP Sales") | $0 per call, from $0.00036 per result |
| 2 | people.email.find | first_name, last_name, domain, linkedin_url when known | from $0.0036 per call |
| 3 | people.email.verify | email | from $0.00145 per call |
| 4 (optional) | linkedin.person.profile | linkedin_url, to confirm the current title | from $0.0012 per call |
Expected total per account with 4 roles × 1 person: about $0.005 search + 4 × $0.005 emails ≈ $0.025; with profile checks ≈ $0.03.
Quote before you run
- Accounts × roles × people per role × (steps 2 + 3), plus the searches.
- Tell the user the total and the
balance; wait for a yes. More than 100 runs: an explicit yes. - Cap each run with
fallback.maxCostUsd(0.03).
Run it
run {"endpointId": "job:people.search", "input": {"domain": "acme.com", "query": "VP Sales"}, "idempotencyKey": "bcm-acme.com-economic", "fallback": {"maxAttempts": 3, "maxCostUsd": 0.03}}
Pick per role: current title matches the role words, most senior first for the economic buyer, most specific title first for the champion. Drop people whose current company is not the account. Then find and verify emails only for the people you picked:
run {"endpointId": "job:people.email.find", "input": {"first_name": "Jane", "last_name": "Doe", "domain": "acme.com"}, "idempotencyKey": "bcm-acme.com-jane-doe-find", "fallback": {"maxAttempts": 3, "maxCostUsd": 0.03}}
Output format
## Example Inc (example.com), cost $0.027
| Role | Name | Title | LinkedIn | Email | Status | Why |
|---|---|---|---|---|---|---|
| Economic buyer | Jane Doe | VP Sales | https://... | [email protected] | valid | owns the sales budget |
| Champion | Sam Lee | RevOps Manager | https://... | [email protected] | catch_all | runs the tools the product replaces |
| User | | | | | | not found |
Plus one CSV with all rows for import. Empty roles stay in the table as "not found".
Cost and stop rules
- Never find emails for people you did not pick.
- A role with no match: do not widen to unrelated titles without asking.
- Two failures in a row on step 1: stop and report.
When not to use this skill
- One person's email:
looot-find-professional-emails. Everyone at a domain:looot-enrich-a-companyorpeople.domain.search.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- linkedin-job-post-to-buyer-pain-map by Varnan-Tech · 674
- map-your-market by Varnan-Tech · 674
- inbound-lead-audit-cx-map by zapier · 342
- decision-makers-map by explorium-ai · 200
- buying-signal-amplification by louisblythe · 179
- positioning-map by pmalliance · 75
- buying-signals-6 by Frontal-so · 6
- clay-buying-signals-5 by Frontal-so · 6
Need help setting it up?
This page tells you what gtm-buying-committee-map does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.