mcpField
Q
qa-gates

qa-gates

github.com/gtmagentsTesting & quality42867 installsUpdated 30w ago
Repository

About qa-gates

A skill for gating email programs before launch and checking fixes after incidents. Its checklist covers personalization, data routing, compliance, analytics, and monitoring, with runbooks and sign-off materials.

Key features

  1. 01Content and personalization validation
  2. 02Trigger, list, and CRM routing checks
  3. 03Compliance and consent review
  4. 04Tracking and analytics verification
  5. 05Monitoring thresholds and rollback planning
  6. 06QA runbook and launch sign-off templates

Use cases

  1. 01Checking nurture or lifecycle programs before activation
  2. 02Reviewing changes to segmentation or personalization
  3. 03Verifying fixes after email incidents

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill qa-gates

After installing, type/qa-gatesin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported