New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Workflow Testing

by gtmagents in gtmagents/gtm-agents

A skill your agent uses when validating automation builds before launch or after significant changes.

Apache-2.0Auto-check passedTesting & QA

Install Workflow Testing

skills CLI
$ npx skills add gtmagents/gtm-agents --skill workflow-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gtmagents/gtm-agents workflow-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/marketing-automation/skills/workflow-testing .claude/skills/workflow-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-testing
GitHub stars
413
Used in
1 other repo
Token cost
~343 tokens
SKILL.md length
148 words
Files
1
Skills in repo
127
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when validating automation builds before launch or after significant changes.

  • Works in 5 steps: Unit Tests – confirm each branch, wait… → Integration Tests – verify webhook/API… → Content QA – links, tracking,… → …
  • Validating automation builds before launch
  • SKILL.md covers When to Use, Framework, Checklist and Templates, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow Testing is an agent skill from gtmagents/gtm-agents. Use when validating automation builds before launch or after significant changes.

Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. The repository describes itself as: Production-ready collection of GTM agents and specialized skills for claude code. Covers sales, marketing, customer success, and revenue operations workflows. The licence is Apache-2.0.

When your agent uses it

  • Validating automation builds before launch
  • After significant changes

Example prompts

  • “/workflow-testing”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 78e0419. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Testing loads about 343 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 148 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~343

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gtmagents/gtm-agents at commit 78e0419, republished under its Apache-2.0 licence (© gtmagents). 148 words, ~343 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-testing/SKILL.md (or your agent's skills folder).
name
workflow-testing
description
Use when validating automation builds before launch or after significant changes.

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.

© gtmagents, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/marketing-automation/skills/workflow-testing of gtmagents/gtm-agents.

Open the folder on GitHubat commit 78e0419

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gtmagents/gtm-agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Workflow Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Testing this skillgtmagents/gtm-agents4131 repos~343Automated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    380 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-check passed

More from gtmagents/gtm-agents

All 127 skills in this repo

  • Enrichment Data Sourcing

    gtmagents/gtm-agents

    Chooses and orders data providers for email, phone, company and intent enrichment, with waterfall sequences and credit-saving tactics across 150+ sources.

    413 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

  • Cold Email Personalization

    gtmagents/gtm-agents

    Writes personalized B2B cold emails from prospect research, using a gated workflow, a quality rubric and follow-up sequences.

    413 GitHub starsUsed in 1 repo~853 tokens
    Auto-check passed

  • Discovery Call Playbook

    gtmagents/gtm-agents

    Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.

    413 GitHub starsUsed in 1 repo~368 tokens
    Auto-check passed

  • Lifecycle Mapping for Automation

    gtmagents/gtm-agents

    Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.

    413 GitHub starsUsed in 1 repo~927 tokens
    Auto-check passed

  • Social Selling

    gtmagents/gtm-agents

    A skill your agent uses when engaging prospects through LinkedIn, communities, and social channels to spark warm conversations and meetings.

    413 GitHub starsUsed in 1 repo~431 tokens
    Auto-check passed

  • Drip Campaigns

    gtmagents/gtm-agents

    A skill your agent uses when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.

    413 GitHub starsUsed in 1 repo~310 tokens
    Auto-check passed

Categories

Questions about Workflow Testing

What does Workflow Testing do?

A skill your agent uses when validating automation builds before launch or after significant changes. Workflow Testing is an agent skill from gtmagents/gtm-agents. Use when validating automation builds before launch or after significant changes.

When should I use Workflow Testing?

Workflow Testing fits situations like: validating automation builds before launch; after significant changes.

How do I install Workflow Testing in Claude Code?

Run `npx skills add gtmagents/gtm-agents --skill workflow-testing -a claude-code`. Or copy the skill folder (plugins/marketing-automation/skills/workflow-testing in gtmagents/gtm-agents) into .claude/skills/workflow-testing in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Testing in Codex?

Run `npx skills add gtmagents/gtm-agents --skill workflow-testing -a codex`. Or copy the skill folder (plugins/marketing-automation/skills/workflow-testing in gtmagents/gtm-agents) into .agents/skills/workflow-testing in your project. Codex loads it when a task matches its description.

Can I use Workflow Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gtmagents/gtm-agents --skill workflow-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-testing, .gemini/skills/workflow-testing, .github/skills/workflow-testing and .opencode/skills/workflow-testing in your project.

What does Workflow Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Testing is instructions for the agent only.

Does Workflow Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflow Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workflow Testing use?

Workflow Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Testing use?

About 343 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow Testing?

Skills that share tags, products or a category with Workflow Testing: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Testing?

gtmagents (a GitHub user) maintains it in gtmagents/gtm-agents, which has 413 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on April 3, 2026.

Source: gtmagents/gtm-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.