smithery/gtmagents

lifecycle-cadence

Use when defining nurture pacing, triggers, and suppression logic.

Installation

$ npx skills add smithery/gtmagents --skill lifecycle-cadence

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,315 B
  • docs SUMMARY.md 91 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Lifecycle Cadence Systems Skill

When to Use

  • Designing new nurture programs or refreshing existing cadences.
  • Auditing fatigue, suppression, or timing conflicts across journeys.
  • Coordinating MAP and CRM routing for multi-channel touches.

Framework

  1. Lifecycle Stage Alignment – ensure cadence matches funnel stage (MQL, SAL, SQL, post-sale).
  2. Trigger Definition – entry signals (form fills, intent spikes, product milestones, campaign responses).
  3. Pacing Rules – waiting periods, fallback content, stop logic for engagement or conversions.
  4. Suppression & Priority – handle conflicting journeys, global caps, sales stages, manual pauses.
  5. Monitoring – alerts for high unsubscribe/bounce, low engagement, or SLA breaches.

Templates

  • Cadence planner (stage, delay, channel, CTA, exit criteria).
  • Suppression matrix (journey priority, conflicts, resolution rules).
  • Monitoring checklist (metrics, thresholds, escalation owners).

Tips

  • Reassess cadences quarterly as product/offers evolve.
  • Keep a single decision table for suppression rules to avoid MAP drift.
  • Align with sales/CS to pause nurtures when opps advance or risks arise.