Agent skill
cadence-design
Use when spacing, sequencing, and pacing multi-touch email programs.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/cadence-design
SKILL.md
Email Cadence Design Skill
When to Use
- Planning nurture, onboarding, or expansion sequences with multiple branches.
- Auditing send frequency to reduce fatigue and unsubscribes.
- Coordinating cross-channel touches (email, in-app, SMS, sales assist).
Framework
- Goal Alignment – map KPIs per stage (activation, education, expansion, retention).
- Signal-Based Timing – trigger on behavior (opens, clicks, product events), not fixed delays.
- Frequency Guardrails – define daily/weekly send caps per persona + lifecycle stage.
- Channel Mix – pair emails with supporting channels; document ownership and SLAs.
- Recovery Paths – add detours for inactivity, hard bounces, or sales handoffs.
Templates
- Cadence matrix (day, trigger, message purpose, CTA, channel).
- Fatigue model calculator (touches vs engagement trend).
- Suppression logic checklist (recent send, opportunity stage, consent).
Tips
- Front-load value but leave whitespace before high-ask CTAs.
- Reuse proven send windows per persona while testing incrementally.
- Share cadence plan with SDR/CSM teams to prevent overlap.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?