Agent skill
find-lead-account-owner
Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
From zapier/gtm-cheat-codes · 17 skills · 329 · pushed 2026-07-13
What it does when it runs
Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
Read from the skill and the 5 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
- mcp.zapier.com
- 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/zapier/gtm-cheat-codes.git /tmp/gtm-cheat-codes git -C /tmp/gtm-cheat-codes sparse-checkout set "skills/gtm-ops/find-lead-account-owner" mkdir -p ~/.claude/skills/find-lead-account-owner cp -R "/tmp/gtm-cheat-codes/skills/gtm-ops/find-lead-account-owner/." ~/.claude/skills/find-lead-account-owner/
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 ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 17 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add zapier/gtm-cheat-codes /plugin
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 zapier/gtm-cheat-codes/blob/022a2884f40316ef22269e29fd61b8a0f0c4cb4a/skills/gtm-ops/find-lead-account-owner/SKILL.md, which is licensed MIT (repository). 155 words, 5 headings.
Find Lead Account Owner
Use this helper when a lead audit, hand-raiser workflow, or SDR worklist needs authoritative owner enrichment.
Resolution Order
- Contact owner.
- Company owner.
- Deal owner.
- None assigned.
Workflow
- Open the contact record.
- Check contact owner first.
- If missing, inspect primary company owner.
- If missing, inspect relevant open or recent deal owner.
- Enrich owner segment, team, manager, and account size from approved systems.
Zapier MCP And SDK Role
- Use Zapier MCP to read CRM contact, company, deal, and ownership data.
- Use Zapier SDK only when this helper becomes part of a repeatable lead audit, routing workflow, or SDR worklist.
- Do not change owner assignments without explicit approval.
Guardrails
- Do not infer owner from timeline activity.
- Do not use a lower-priority owner field when a higher-priority field exists.
- Preserve provenance for every returned owner.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
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.
- lead-magnets by coreyhaines31 · 45,947
- lead-dossier by ericosiu · 3,449
- lead-magnet by OpenClaudia · 664
- lead-scoring by shawnpang · 308
- lead-enrichment by janskuba · 199
- lead-qualification by louisblythe · 136
- lead-qualification-logic by louisblythe · 136
- territory-account-launch by louisblythe · 136
Need help setting it up?
This page tells you what find-lead-account-owner 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.