Agent skill
named-account-trigger-radar
Identify named accounts with timely buying or expansion signals and recommend next actions.
Filed under Prospecting and list building.
From zapier/gtm-cheat-codes · 17 skills · 329 · pushed 2026-07-13
What it does when it runs
Identify named accounts with timely buying or expansion signals and recommend next actions.
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/sales-revops/named-account-trigger-radar" mkdir -p ~/.claude/skills/named-account-trigger-radar cp -R "/tmp/gtm-cheat-codes/skills/sales-revops/named-account-trigger-radar/." ~/.claude/skills/named-account-trigger-radar/
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/sales-revops/named-account-trigger-radar/SKILL.md, which is licensed MIT (repository). 159 words, 4 headings.
Named Account Trigger Radar
Use this skill to decide which named accounts sales or marketing should work now, why they are timely, and what action should happen next.
Workflow
- Define the account pool and separate new-logo, recovery, and expansion motions.
- Gather company-approved evidence first, then add public triggers when useful.
- Score accounts based on actionability, recency, fit, and next-step clarity.
- Return a short ranked list, not a generic market summary.
- Label weak or stale evidence rather than forcing a recommendation.
Zapier MCP And SDK Role
- Use Zapier MCP to read CRM, account lists, approved account signals, public research, and collaboration context.
- Use Zapier SDK for scheduled account watchlists, account-priority logging, and approved owner notifications.
- Keep CRM updates and outbound recommendations human-reviewed.
Guardrails
- Do not recommend accounts solely because they are large.
- Do not fabricate ownership, intent, or titles.
- Use absolute dates for trigger recency.
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.
- territory-account-launch by louisblythe · 136
- trigger-event-detection by louisblythe · 136
- account-structure-review by thatrebeccarae · 119
- account-qualification by kenny589 · 63
- trigger-mapping by kenny589 · 63
- account-research-brief by Othmane-Khadri · 55
- account-qualification by Salesably · 48
- trade-show-competitor-radar by LensmorOfficial · 48
Need help setting it up?
This page tells you what named-account-trigger-radar 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.