How do I install the QA Eval skill?

Run npx skillmds@latest add ashermahonin/qa-eval in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is QA Eval safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA Eval?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is QA Eval free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published QA Eval?

ashermahonin (@ashermahonin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA Eval by ashermahonin — Agent Skill

Name: QA Eval
Author: ashermahonin

QA Eval

Plan and run verification gates for unit, integration, browser, contract, migration, security, performance, accessibility, smoke, acceptance, and eval scenarios. Use before merge or release, after implementation, when validation evidence is missing, when quality scenarios need proof, or when artifacts `32-test-strategy.md`, `33-evaluation-plan.md`, and release readiness notes must be produced.

ashermahonin Updated Sep 21, 2026

File contents

QA and Eval

Purpose

Prove the important behavior works and the important risks are covered. Make verification practical, visible, and tied to acceptance criteria.

Change context

Collect requirements, acceptance criteria, changed files, and risk notes.
Identify the minimum test set that covers the behavior and highest risks.
Separate automated checks from manual smoke checks.
Decide what cannot be verified in this environment and how to report it honestly.

Change method

Map each acceptance criterion to a validation method.
Run existing tests before inventing new ones when that gives useful signal.
Add focused tests when behavior changed and no existing test covers it.
For UI work, verify real rendering and main workflows when possible.
For migrations or data changes, verify rollback or safe failure behavior.
Summarize pass/fail evidence with commands, scenarios, and residual risk.

Engineering constraints

Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.

Evidence

Validation plan
Commands run
Acceptance evidence
Bugs or regressions found
Release readiness recommendation

Ready when

Do not treat compilation as full QA.
Do not hide skipped checks.
Tie every critical risk to a test, smoke check, or explicit residual risk.
Keep bug reports reproducible.

Handoff

Hand off evidence, failures, skipped checks, and release recommendation to PR review or release docs.

References

references/eval-plan.md: Use this for test and eval planning.

---name: qa-evaldescription: Plan and run verification gates for unit, integration, browser, contract, migration, security, performance, accessibility, smoke, acceptance, and eval scenarios. Use before merge or release, after implementation, when validation evidence is missing, when quality scenarios need proof, or when artifacts `32-test-strategy.md`, `33-evaluation-plan.md`, and release readiness notes must be produced.---# QA and Eval## PurposeProve the important behavior works and the important risks are covered. Make verification practical, visible, and tied to acceptance criteria.## Change context- Collect requirements, acceptance criteria, changed files, and risk notes.- Identify the minimum test set that covers the behavior and highest risks.- Separate automated checks from manual smoke checks.- Decide what cannot be verified in this environment and how to report it honestly.## Change method1. Map each acceptance criterion to a validation method.2. Run existing tests before inventing new ones when that gives useful signal.3. Add focused tests when behavior changed and no existing test covers it.4. For UI work, verify real rendering and main workflows when possible.5. For migrations or data changes, verify rollback or safe failure behavior.6. Summarize pass/fail evidence with commands, scenarios, and residual risk.## Engineering constraints- Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.## Evidence- Validation plan- Commands run- Acceptance evidence- Bugs or regressions found- Release readiness recommendation## Ready when- Do not treat compilation as full QA.- Do not hide skipped checks.- Tie every critical risk to a test, smoke check, or explicit residual risk.- Keep bug reports reproducible.## HandoffHand off evidence, failures, skipped checks, and release recommendation to PR review or release docs.## References- `references/eval-plan.md`: Use this for test and eval planning.

Frequently asked questions