---
name: gtmagents-nurture-testing
description: "Use when planning, executing, and logging nurture experiments and regression tests."
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "c36ab181-2336-439c-b6e5-c10c5d2ebc55"
  decimalai-version-id: "5a412355-8f67-4a0b-9716-2d9265a6426e"
  decimalai-version: "1"
  decimalai-body-sha256: "5d52b6f3efee8a82d7ea5eeaf9fb776f004566b4f60f621a1ec20e36fb5d774d"
  decimalai-name: "gtmagents/nurture-testing"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "marketing"
  decimalai-source: "https://app.decimal.ai/s/gtmagents-nurture-testing@1/SKILL.md"
---
# 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.

---