Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add daymade/claude-code-skills --skill qa-expertgit clone --depth 1 https://github.com/daymade/claude-code-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/daymade/claude-code-skills/qa-expert)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/qa-expert"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/qa-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/qa-expert"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/qa-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00086 | $0.02876 |
| Opus 5.5 | $0.00034 | $0.01150 |
| Sonnet 5.5 | $0.00017 | $0.00575 |
| Haiku 4.5 | $0.00009 | $0.00288 |
Grade A, and why
qa-expert scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
95% identical to test-suite-architect — 102 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Expert
Set up test cases, execution tracking, bug reports and QA handoffs using AAA test structure and OWASP security categories.
When to Use This Skill
Trigger this skill when:
- Setting up QA infrastructure for a new or existing project
- Writing standardized test cases (AAA pattern compliance)
- Executing comprehensive test plans with progress tracking
- Implementing security testing (OWASP Top 10)
- Filing bugs with proper severity classification (P0-P4)
- Generating QA reports (daily summaries, weekly progress)
- Calculating quality metrics (pass rate, coverage, gates)
- Preparing QA documentation for third-party team handoffs
- Enabling autonomous LLM-driven test execution
Quick Start
One-command initialization:
uv run <qa-expert-dir>/scripts/init_qa_project.py <project-name> <project-root>
What gets created:
- Directory structure (
tests/docs/,tests/e2e/,tests/fixtures/) - Tracking CSVs (
TEST-EXECUTION-TRACKING.csv,BUG-TRACKING-TEMPLATE.csv) - Documentation templates (
BASELINE-METRICS.md,WEEKLY-PROGRESS-REPORT.md) - Master QA Prompt for autonomous execution
- README with preparation steps and links to the generated files
The output directory is the project root; the script appends tests/. Use a fresh
destination: initialization overwrites its template files. Replace example CSV
rows, write test specifications and bind the project harness before execution.
Resolve <qa-expert-dir> from this loaded Skill's directory, not the target project.
For autonomous execution: Follow the master prompt for preparation, bounded execution and interruption recovery. Initialization creates templates; it does not run tests or install a scheduler.
Core Capabilities
1. QA Project Initialization
Initialize QA directories and templates:
uv run <qa-expert-dir>/scripts/init_qa_project.py <project-name> <project-root>
Creates directory structure, tracking CSVs, documentation templates, and master prompt for autonomous execution.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/TEST-CASE-TEMPLATE.md 4.4 KB
- references/async-edit-conflict-acceptance.md 6.4 KB
- references/day1_onboarding.md 9.4 KB
- references/file-persistence-cli-acceptance.md 7.8 KB
- references/google_testing_standards.md 5.0 KB
- references/ground_truth_principle.md 9.6 KB
- references/llm_prompts_library.md 16 KB
- references/master_qa_prompt.md 5.5 KB
- references/migration-fixture-acceptance.md 3.7 KB
- references/transaction-recovery-acceptance.md 5.2 KB
- scripts/calculate_metrics.py 2.8 KB runs code
- scripts/init_qa_project.py 9.0 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +5 lines 655a99db4d28
- 5d ago Changed · +15 lines 416218900684
- 26d ago Changed · +5 lines · -2 tokens per session cd5c71f74166
- 1mo ago First seen · 289 lines · 88 tokens per session scan A 9c38813fe3b9
qa-expert is a skill published in the GitHub repository daymade/claude-code-skills (1,477 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 2,876 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to test-suite-architect, differing in 102 lines, and is treated as a copy.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.