qa-expert

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

1.51x

Quality

—

Does it follow best practices?

Impact

94%

1.51x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with real bundle files and strong feedback-loop workflows. Its main weakness is conciseness — repeated marketing language and the autonomous-execution flow duplicated across four sections could be consolidated.

Suggestions

Consolidate the autonomous-execution material into a single section; it currently appears in Quick Start, section 3 ('Test Execution & Tracking'), the dedicated 'Autonomous Execution' section, and Common Pattern 2 — keep one authoritative description and cross-reference it.

Remove marketing fluff such as 'world-class', '100x faster'/'100x speedup', 'zero human error', and '⭐ Recommended' — state what the master prompt does without the hype.

Tighten the OWASP list (section 7) into a compact table or a pointer to references/google_testing_standards.md rather than a partial inline enumeration that omits A06/A08/A09/A10 without explanation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but padded with marketing fluff ('world-class', '100x faster'/'100x speedup' repeated, 'zero human error', '⭐ Recommended') and the autonomous-execution flow is restated in four places (Quick Start, section 3, a dedicated section, and Common Patterns). Not a 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Fully executable commands referencing real scripts — 'python scripts/init_qa_project.py <project-name> [output-directory]' and 'python scripts/calculate_metrics.py <path/to/TEST-EXECUTION-TRACKING.csv>' — plus a concrete quality-gates table and severity definitions; copy-paste ready.	3 / 3
Workflow Clarity	Clear sequences with explicit feedback checkpoints for the batch test-execution workflow: 'Update TEST-EXECUTION-TRACKING.csv immediately after EACH test (never batch)', file a bug on failure, P0 escalation stops testing, and quality gates that must all pass to release.	3 / 3
Progressive Disclosure	Well-signaled one-level-deep references to real bundle files (all five references/, assets/templates/TEST-CASE-TEMPLATE.md, and both scripts/ exist), gathered in dedicated 'Reference Documents', 'Assets & Templates', and 'Scripts' sections for easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, natural trigger terms, explicit 'Use when' guidance, and a distinct QA niche. Minor over-claims ('achieves 90% coverage targets', 'complete documentation templates') slightly pad it, but not enough to drop any dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated QA actions) and when ('Use when creating test strategies, writing test cases...'), satisfying the explicit-trigger requirement for the top anchor.	3 / 3
Trigger Term Quality	Good coverage of natural terms a user would say — 'test strategies', 'test cases', 'test plans', 'bugs', 'P0-P4 classification', 'quality metrics', 'progress reports', 'OWASP security testing', 'coverage targets'.	3 / 3
Distinctiveness Conflict Risk	Clear QA-testing niche anchored by Google Testing Standards, OWASP, and P0-P4 severity — distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: daymade/claude-code-skills
Commit: e5ac7ba

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.