About nurture-testing
nurture-testing is a skill for teams testing and checking marketing nurture flows. It covers experiment design, pre-launch QA, evidence logging, rollout criteria, and recurring regression checks.
Key features
- 01Experiment design and tracking
- 02Link, token, and segment QA
- 03Evidence capture and logging
- 04Significance and rollout criteria
- 05Scheduled regression checks
Use cases
- 01Testing nurture flow experiments
- 02Checking flows before launch or updates
- 03Preparing QA evidence for audits
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/nurture-testingin Claude Code to confirm it loaded.
Details
From the project READMENurture Testing & QA Skill
When to Use
- Running experiments (subject lines, timing, offers, personalization) in nurture flows.
- Performing regression tests before go-live or updates.
- Documenting QA evidence for compliance/audits.
Framework
- Test Design – hypothesis, variable, control, variant, KPI, sample size, duration.
- QA Checklist – links, tokens, segmentation, tracking, device/browser coverage, accessibility.
- Evidence Logging – screenshots, seed inbox captures, MAP logs, CRM task verification.
- Significance & Rollout – evaluation method (frequentist/Bayesian), rollout criteria, holdback rules.
- Regression Cadence – schedule for periodic audits, triggered when assets/tokens change.
Templates
- Experiment brief + tracker.
- QA matrix (scenario, expected result, status, owner).
- Evidence archive folder structure.
Tips
- Always include control groups or holdouts for long-running nurtures.
- Automate reminders to re-run QA after major MAP/CRM updates.
- Pair with
personalization-logicandmarketing-ops-partnerto catch edge cases early.
Comments
Markdown supported