smithery.ai

cadence-design

Use when spacing, sequencing, and pacing multi-touch email programs.

First seen Apr 10, 2026

Installation

$ npx skills add https://smithery.ai

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.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

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,263 B
  • docs SUMMARY.md 90 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

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

  1. Goal Alignment – map KPIs per stage (activation, education, expansion, retention).
  2. Signal-Based Timing – trigger on behavior (opens, clicks, product events), not fixed delays.
  3. Frequency Guardrails – define daily/weekly send caps per persona + lifecycle stage.
  4. Channel Mix – pair emails with supporting channels; document ownership and SLAs.
  5. 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.