Skip to main content
Generalgtmagents

nurture-testing

Use when planning, executing, and logging nurture experiments and regression

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--nurture-testing
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/lead-nurture-orchestration/skills/nurture-testing/SKILL.md -o .claude/skills/nurture-testing.md

Drops the SKILL.md into .claude/skills/nurture-testing.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Nurture 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

  1. Test Design – hypothesis, variable, control, variant, KPI, sample size, duration.
  2. QA Checklist – links, tokens, segmentation, tracking, device/browser coverage, accessibility.
  3. Evidence Logging – screenshots, seed inbox captures, MAP logs, CRM task verification.
  4. Significance & Rollout – evaluation method (frequentist/Bayesian), rollout criteria, holdback rules.
  5. 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-logic and marketing-ops-partner to catch edge cases early.