Initial commit

skills/cadence-design/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: cadence-design
+description: Use when spacing, sequencing, and pacing multi-touch email programs.
+---
+
+# 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.
+
+---

skills/qa-gates/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: qa-gates
+description: Use before launching sequences to validate content, data, compliance,
+  and monitoring.
+---
+
+# Email QA Gates Skill
+
+## When to Use
+- Prior to activating new nurture or lifecycle programs.
+- After major changes to segmentation, personalization tokens, or deliverability settings.
+- During post-incident reviews to ensure fixes remain in place.
+
+## Framework
+1. **Content & Personalization** – placeholders resolved, links tracked, dynamic content fallback tested.
+2. **Data & Routing** – trigger logic, smart lists, suppression rules, CRM fields synced.
+3. **Compliance** – footer language, preference center links, consent status, regional routing.
+4. **Tracking & Analytics** – UTM/tagging consistency, BI/warehouse pipes, alert webhooks.
+5. **Monitoring Hooks** – dashboards referenced, alert thresholds set, rollback plan documented.
+
+## Templates
+- QA runbook with owner, status, evidence links for each checklist item.
+- Proofing matrix (persona × email × device × ISP) for screenshot validation.
+- Launch readiness form requiring sign-off from marketing, ops, legal, and RevOps.
+
+## Tips
+- Pair with `deliverability-ops` to confirm authentication and inbox monitoring.
+- Automate regression tests via API where possible (token validation, link health).
+- Store QA evidence (screenshots, logs) alongside sequence assets for audits.
+
+---