playbooks

home / skills / gtmagents / gtm-agents / qa-gates

qa-gates skill

/plugins/email-sequence-orchestration/skills/qa-gates

This skill helps QA-gates validate content, data, compliance, and monitoring before launching nurture programs across campaigns.

npx playbooks add skill gtmagents/gtm-agents --skill qa-gates

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.4 KB
---
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.

---

Overview

This skill validates sequences and campaigns before launch to reduce errors, compliance risk, and measurement gaps. It codifies a repeatable QA gate across content, data, compliance, tracking, and monitoring so teams can launch with confidence. The skill includes templates and checklist logic to capture evidence and sign-offs.

How this skill works

The skill runs a sequence of inspections that check content personalization, link health, and dynamic content fallbacks. It validates data and routing rules, suppression lists, and CRM field syncs. Compliance checks confirm footer language, preference links, and consent status by region. Finally it verifies tracking tags, analytics pipelines, and monitoring hooks with rollback plans and alert thresholds.

When to use it

  • Before activating new nurture or lifecycle programs
  • After major segmentation, personalization, or deliverability changes
  • During post-incident reviews to confirm fixes and prevent regressions
  • When adding new integrations or altering data routing rules
  • Prior to large-scale promotions or regulatory-driven campaigns

Best practices

  • Use the QA runbook template with a named owner and evidence links for every checklist item
  • Include a proofing matrix (persona × email × device × ISP) to capture screenshots and rendering issues
  • Automate repeatable checks via API for token resolution, link validation, and suppression logic
  • Pair with deliverability monitoring to confirm authentication and inbox placement
  • Store QA evidence alongside assets for auditability and retrospective reviews

Example use cases

  • Validating a new welcome series with dynamic tokens and regional footers
  • Checking segmentation and suppression changes after a CRM migration
  • Confirming tracking tags and BI pipeline connections before a major campaign
  • Running a post-incident QA to ensure routing and consent fixes remain effective
  • Collecting sign-offs from marketing, ops, legal, and RevOps for launch readiness

FAQ

What evidence should I collect for each QA item?

Collect screenshots, token resolution logs, link check reports, suppression query results, and a timestamped sign-off from the owner.

Can checks be automated?

Yes. Automate token validation, link health, suppression queries, and API-based rendering checks where possible to reduce manual effort.