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

92%

Does it follow best practices?

Impact

94%

1.51x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

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.

This is a strong skill description that clearly articulates specific QA testing capabilities with concrete actions, standards, and metrics. It includes explicit 'Use when' guidance with natural trigger terms that users would actually say. The description is distinctive enough to avoid conflicts with other skills while being comprehensive about its scope.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'creating test strategies, writing test cases, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, generating progress reports.' Also mentions specific standards (Google Testing Standards, OWASP) and concrete targets (90% coverage).	3 / 3
Completeness	Explicitly answers both what (comprehensive QA testing processes, test strategies, test cases, bug tracking, metrics, reports) AND when ('Use when creating test strategies, writing test cases...') with clear trigger guidance at the start.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'QA testing', 'test strategies', 'test cases', 'test plans', 'bugs', 'quality metrics', 'progress reports', 'security testing', 'coverage'. Good coverage of terms a user seeking QA help would naturally use.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused on QA/testing processes with distinct triggers like 'P0-P4 classification', 'Google Testing Standards', 'OWASP security testing', 'QA team handoffs'. Unlikely to conflict with general coding or documentation skills.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

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

This is a well-structured, highly actionable skill with excellent progressive disclosure and clear workflows. The main weakness is moderate verbosity - some sections explain concepts Claude already knows (severity classifications, OWASP categories) and the 'Adapting for Your Project' section adds generic guidance that could be trimmed. Overall, it's a strong skill that would benefit from tightening.

Suggestions

Remove or condense the severity classification explanations (P0-P4) - Claude understands these concepts; a simple reference to the template would suffice

Trim the OWASP Top 10 listing to just reference the security testing standards document rather than enumerating all categories inline

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what P0-P4 means when Claude knows severity classifications, listing all OWASP categories). Some sections could be tightened, particularly the 'Adapting for Your Project' section which provides generic guidance.	2 / 3
Actionability	Provides concrete, executable commands (python scripts/init_qa_project.py), specific file paths, clear templates, and copy-paste ready patterns. The numbered steps and code blocks are immediately actionable.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with explicit validation checkpoints. The 'Ground Truth Principle' section emphasizes critical validation, Pattern 1-4 provide clear step sequences, and the autonomous execution workflow includes auto-resume and error handling.	3 / 3
Progressive Disclosure	Excellent structure with clear overview sections pointing to one-level-deep references (references/master_qa_prompt.md, references/google_testing_standards.md, etc.). Content is appropriately split between quick start, core capabilities, and detailed reference documents.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: fernandezbaptiste/claude-code-skills
Commit: 4f0eae8

Reviewed: 30 days 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.