smithery/gtmagents

workflow-testing

Use when validating automation builds before launch or after significant changes.

Installation

$ npx skills add smithery/gtmagents --skill workflow-testing

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,380 B
  • docs SUMMARY.md 105 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Workflow Testing & QA Skill

When to Use

  • Any new automation or major revision prior to go-live.
  • Regression testing after data, asset, or logic changes.
  • Investigating deliverability, conversion, or routing anomalies.

Framework

  1. Unit Tests – confirm each branch, wait step, and action path with seed contacts.
  2. Integration Tests – verify webhook/API calls, CRM updates, enrichment, scoring.
  3. Content QA – links, tracking, personalization tokens, accessibility, localization.
  4. Compliance – consent, suppression, GDPR/CASL/CCPA rules, regional requirements.
  5. Performance – throttle checks, concurrency, error handling, failover.

Checklist

  • Seed list matrix (personas, stages, regions, consent flags).
  • Device/browser testing for email/SMS/push rendering.
  • Logging + alerting validation.
  • Rollback and kill switches documented.

Templates

  • QA evidence log (screenshot, recipient, status, owner).
  • Incident runbook for automation failures.
  • Release checklist referencing stakeholders.

Tips

  • Automate regression tests via APIs or synthetic users.
  • Store test data separately and purge regularly to avoid reporting noise.
  • Use feature flags to stage rollouts before full scale.