Agent QA Authoring

Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.

912 stars 23 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vostride/agent-qa --skill agent-qa-authoring
Manual install
git clone --depth 1 https://github.com/vostride/agent-qa.git /tmp/agent-qa
mkdir -p ~/.claude/skills
cp -r /tmp/agent-qa/skills/agent-qa-authoring ~/.claude/skills/agent-qa-authoring

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# agent-qa Authoring

## Workflow

1. Discover the surface from the protocol itself: `tools/list` names every tool, and every caller
   sees and may call the same set. For the full picture — the capability catalog and this
   workspace's posture — run `npx agent-qa init --agent`, which prints one JSON document and writes
   nothing.
2. Read the workspace posture from that same manifest: whether this workspace has a configuration
   that reads. No MCP tool reads configuration.
3. Load `references/agent-qa-contracts.json` when you need exact schema fields or ID contracts.
4. Never mint an ID and never hand-write one. IDs are minted host-side where the entity is written:
   name what you want, then read the id back off the entity card `agent_qa_get_entity` returns.
5. Never validate an ID by hand either. The one URI codec validates every `agentqa://` reference as
   it is parsed, including the one `agent_qa_get_entity` resolves — a reference that comes back
   resolved is a reference that was well-formed.
6. Validate before you write. `agent_qa_refine_test`'s verify arm returns the same verdict that
   gates the write; there is no standalone linter over pasted text, on purpose, because a second
   validator can disagree with the one that gates.
7. Authoring changes apply in the call, and each answer names what it wrote:
   - A new test or suite file: `agent_qa_write_test`, which names the suite file the draft joins and
Read the full skill on GitHub

Details

Skill name
agent-qa-authoring
Repository
vostride/agent-qa
Path
skills/agent-qa-authoring/SKILL.md
Repo updated
31 October 2026
Listed in
heilcheng/awesome-agent-skills, karanb192/awesome-claude-skills

FAQ

What does the Agent QA Authoring skill do?

Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.

How do I install the Agent QA Authoring skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add vostride/agent-qa --skill agent-qa-authoring. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Agent QA Authoring popular?

It lives in vostride/agent-qa, which has 912 GitHub stars and 23 forks, and is included in 2 curated skill lists.

Related skills

Grill Me

1.3k

RobMitt/grill-me-skill

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Testing & QA106

Provider Test Patterns

910

hashicorp/agent-skills

Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing, or debugging provider acceptance tests, including questions about statecheck, plancheck, TestCheck

Testing & QAIn 2 lists134

Test Fixing

689

mhattingpete/claude-skills-marketplace

Detects failing tests and proposes fixes. Automatically identify test failures and suggest solutions.

Testing & QAIn 3 lists99

Product Strategy Session

7.8k

deanpeters/Product-Manager-Skills

Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.

Testing & QAIn 3 lists940

Squadra

1.1k

dagoSte/squadra

Coordinates work entrusted to several Codex, Claude, Cursor or mixed windows, with tasks, acknowledgements, proofs, a non-author reviewer and a persistent registry. Includes squadra dash to view the activity and squadra selftest to test the protocol. Use when the owner asks for a squad (squadra), a coordinator/builders/reviewer, resuming a squad or its dashboard; it does not impose this scheme on ordinary changes in a single window.

Testing & QA91

Pol Probe

7.8k

deanpeters/Product-Manager-Skills

Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product.

Testing & QAIn 3 lists940

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.