GTM Engineering
tech-leads-club/agent-skills
Designs go-to-market automation and AI agent workflows for revenue teams, built on the idea that architecture and context matter more than any single tool.
Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
Install Find Lead Account Owner
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-owner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .claude/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .claude/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-ownerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-owner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .agents/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .agents/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-owner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .cursor/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .cursor/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/zapier/gtm-cheat-codes.git --path skills/gtm-ops/find-lead-account-owner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-owner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .gemini/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .gemini/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-ownerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .github/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .github/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/gtm-cheat-codes find-lead-account-owner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/gtm-cheat-codes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/gtm-ops/find-lead-account-owner .opencode/skills/find-lead-account-owner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "find-lead-account-owner" agent skill from https://github.com/zapier/gtm-cheat-codes/tree/main/skills/gtm-ops/find-lead-account-owner into .opencode/skills/find-lead-account-owner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-lead-account-owner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
find-lead-account-owner- GitHub stars
- 342
- Token cost
- ~275 tokens
- SKILL.md length
- 144 words
- Files
- 6
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
- Works in 4 steps: Contact owner. → Company owner. → Deal owner. → …
- Tasks that involve Go-to-market strategy
- SKILL.md covers Resolution Order, Workflow, Zapier MCP And SDK Role and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Find Lead Account Owner is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
Its SKILL.md is about 280 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `ONBOARDING-PROMPT.md`, `README.md` and `SCHEMA-MAP.md`).
It sits in Productivity & Automation, covering Go-to-market strategy and Workflow automation. It works with Zapier. The repository describes itself as: A field guide for go to market teams using coding agents. Installable skills for campaign planning, CRM context, customer proof, and reviewable agent workflows. The licence is MIT.
When your agent uses it
- Tasks that involve Go-to-market strategy
- Tasks that involve Workflow automation
Example prompts
- “/find-lead-account-owner”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Contact owner.
- Company owner.
- Deal owner.
- None assigned.
What it can do on your machine
Read from SKILL.md and the folder at commit 022a288. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Find Lead Account Owner loads about 275 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 144 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from zapier/gtm-cheat-codes at commit 022a288, republished under its MIT licence (© zapier). 144 words, ~275 tokens.
Download SKILL.mdSave it as
.claude/skills/find-lead-account-owner/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- find-lead-account-owner
- description
- Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
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.
© zapier, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files in skills/gtm-ops/find-lead-account-owner of zapier/gtm-cheat-codes.
- SKILL.md
- ONBOARDING-PROMPT.md
- README.md
- SCHEMA-MAP.md
- SETUP.md
- metadata.yaml
Open the folder on GitHubat commit 022a288
Compare with similar skills
Find Lead Account Owner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Find Lead Account Owner this skillzapier/gtm-cheat-codes | 342 | — | ~275 | Automated safety check: Pass | MIT | |
| GTM Engineeringtech-leads-club/agent-skills | 7k | — | ~4.8k | Automated safety check: Pass | Custom licence | |
| Zapier SDKzapier/sdk | 264 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Zapier Demozapier/zapier-mcp | 430 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Zapier Explorezapier/zapier-mcp | 430 | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Zapier SDK
zapier/sdk
Zapier SDK for TypeScript. An agent skill from zapier/sdk.
- Official
Zapier Demo
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
- Official
Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
- Official
Zapier Explore
zapier/zapier-mcp
Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions…
- Official
Zapier Onboard
zapier/zapier-mcp
Onboard a new user to Zapier MCP — introduce what it can do, walk through authentication, and route into the right flow based on the state of their setup.
More from zapier/gtm-cheat-codes
All 21 skills in this repo- Official
Customer Deck Builder
zapier/gtm-cheat-codes
Builds a tailored sales or customer success deck from approved CRM context and generates it in Gamma through Zapier MCP for calls like QBRs or renewals.
- Official
Customer Story Writer
zapier/gtm-cheat-codes
Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.
- Official
Customer Social Proof Finder
zapier/gtm-cheat-codes
Finds approved case studies, quotes, stats, logos and peer examples for campaigns, decks, emails and sales conversations, and flags anything that still needs approval.
- Official
Install Zapier
zapier/gtm-cheat-codes
Works out whether you need Zapier MCP, the SDK or the CLI, then walks through installing and verifying that one path step by step.
- Official
Media Inbox Triage
zapier/gtm-cheat-codes
Sorts a shared Gmail inbox for press, partnership and high-intent requests, scores urgency, suggests an owner and routes items through Zapier MCP for human review.
- Official
MCP Sheet Cache Bridge
zapier/gtm-cheat-codes
Designs an event-driven Google Sheets cache tab that mirrors a Zapier Tables source of truth, so spreadsheet-based tools keep working without direct API reads.
Related
Works with
Categories
Questions about Find Lead Account Owner
What does Find Lead Account Owner do?
Resolve the right account owner for a lead using contact, company, and deal ownership evidence. Find Lead Account Owner is an agent skill from zapier/gtm-cheat-codes, published by the product's own GitHub organization. Resolve the right account owner for a lead using contact, company, and deal ownership evidence.
When should I use Find Lead Account Owner?
Find Lead Account Owner fits situations like: tasks that involve Go-to-market strategy; tasks that involve Workflow automation.
How do I install Find Lead Account Owner in Claude Code?
Run `npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a claude-code`. Or copy the skill folder (skills/gtm-ops/find-lead-account-owner in zapier/gtm-cheat-codes) into .claude/skills/find-lead-account-owner in your project. Claude Code loads it when a task matches its description.
How do I install Find Lead Account Owner in Codex?
Run `npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a codex`. Or copy the skill folder (skills/gtm-ops/find-lead-account-owner in zapier/gtm-cheat-codes) into .agents/skills/find-lead-account-owner in your project. Codex loads it when a task matches its description.
Can I use Find Lead Account Owner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zapier/gtm-cheat-codes --skill find-lead-account-owner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-lead-account-owner, .gemini/skills/find-lead-account-owner, .github/skills/find-lead-account-owner and .opencode/skills/find-lead-account-owner in your project.
What does Find Lead Account Owner need to run?
SKILL.md names no scripts, command-line tools or credentials: Find Lead Account Owner is instructions for the agent only.
Does Find Lead Account Owner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Find Lead Account Owner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Find Lead Account Owner use?
Find Lead Account Owner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Find Lead Account Owner use?
About 275 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Find Lead Account Owner?
Skills that share tags, products or a category with Find Lead Account Owner: GTM Engineering (tech-leads-club/agent-skills, 7k stars), Zapier SDK (zapier/sdk, 264 stars), Zapier Demo (zapier/zapier-mcp, 430 stars) and Zapier Status (zapier/zapier-mcp, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Find Lead Account Owner?
zapier (a GitHub organization, an official publisher) maintains it in zapier/gtm-cheat-codes, which has 342 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 13, 2026.
Source: zapier/gtm-cheat-codes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.