Agent skill
trigger-cadence
Builds outbound sequences that start from a specific buying trigger (funding, hiring, tech change, leadership move, product usage) instead of a static persona list, with a routing table that picks the cadence for each trigger.
Filed under Outbound email.
From varunk130/ai-gtm-skill-library · 37 skill entries · 6 · pushed 2026-09-19
What it does when it runs
Builds outbound sequences that start from a specific buying trigger (funding, hiring, tech change, leadership move, product usage) instead of a static persona list, with a routing table that picks the cadence for each trigger. Use when: outbound sequence, cold email cadence, signal-based outbound, trigger-based prospecting, sales sequence, follow-up cadence, re-engagement campaign.
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
- No third-party host appears in the skill or its bundled files.
- 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/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library git -C /tmp/ai-gtm-skill-library sparse-checkout set "gtm-skills/trigger-cadence" mkdir -p ~/.claude/skills/trigger-cadence cp -R "/tmp/ai-gtm-skill-library/gtm-skills/trigger-cadence/." ~/.claude/skills/trigger-cadence/
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 varunk130/ai-gtm-skill-library/blob/158f12c03830dca454576eb1a78b1e4a34ae83e3/gtm-skills/trigger-cadence/SKILL.md, which is licensed MIT (repository). 508 words, 8 headings.
Trigger Cadence (SPARK Framework)
Persona-only sequences send the same five emails to everyone who matches a title. Trigger Cadence starts from why this account might buy now, routes each trigger to its own cadence, and makes every touch reference the trigger so the outreach reads as timely rather than templated.
Core Principle
No trigger, no sequence. An account without a current reason to talk goes to nurture, not to a rep's inbox queue.
The SPARK Framework
| Letter | Step | The Question |
|---|---|---|
| S | Signal | What changed at the account in the last 30 days? |
| P | Point of view | What does that change likely break or unlock for them? |
| A | Ask | What is the smallest useful next step (a teardown, a benchmark, 15 minutes)? |
| R | Route | Which cadence fits this trigger's urgency and buyer? |
| K | Keep-warm rule | When does the sequence pause and hand the account to nurture? |
Trigger Routing Table
| Trigger | Buyer | Cadence | Touches / days |
|---|---|---|---|
| New funding | Founder / VP | Fast: email, LinkedIn, email, call | 4 / 10 |
| Hiring for the role you replace or support | Hiring manager | Medium: email, email, LinkedIn, email | 4 / 14 |
| Tech stack change | Technical owner | Medium: email with teardown, follow-up, call | 3 / 12 |
| New executive | New leader | Slow: congrats + POV, value asset, ask | 3 / 21 |
| Product usage spike (PLG) | Active user, then admin | Fast: in-app, email, call | 3 / 7 |
Process
- Detect - pull triggers from signal sources; discard any older than 30 days
- Write the POV - one sentence per account linking the trigger to a specific consequence
- Route - pick the cadence from the table; one active sequence per account at a time
- Draft touches - every touch names the trigger or its consequence; no touch without new value
- Set the keep-warm rule - no reply after the last touch, or trigger resolved → nurture for 60 days
- Review - sample 10 drafts; any that would make sense sent to a different account get rewritten
Output
Save to outputs/trigger-cadence-[segment]-[YYYY-MM-DD].md
| Artifact | Description |
|---|---|
| Trigger list | Account, trigger, date, POV sentence |
| Routed cadences | Touch-by-touch copy per trigger type |
| Keep-warm and handoff rules | When sequences pause and where accounts go next |
Tips
- The swap test - if a touch works for any account, it is a template, not outreach
- Short beats clever - under 90 words per email
- Measure by trigger - reply rate per trigger type shows which signals are worth buying
Pairs With
- signal-radar - supplies market-level triggers
- context-anchor - supplies Audience and Voice for tone
- battle-scanner - supplies competitor-switch triggers
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.
- named-account-trigger-radar by zapier · 339
- trigger-finder by Othmane-Khadri · 310
- trigger-event-detection by louisblythe · 159
- trigger-mapping by kenny589 · 64
- operating-cadence-designer by NEON-Rutger · 48
- revenue-operating-cadence by NEON-Rutger · 48
- operating-cadence by beingsmit · 44
- 19-signal-based-outreach-trigger by SimonTheSalesBooster · 40
Need help setting it up?
This page tells you what trigger-cadence 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.