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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./qa-expert/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

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

Actionable and well-structured with clear workflows and verified one-level-deep references, but it suffers from significant repetition (especially around autonomous execution) and marketing-style padding that inflate the token budget.

Suggestions

Consolidate the autonomous-execution instructions into a single canonical section; they currently appear in Quick Start, §3, a dedicated 'Autonomous Execution' section, and Pattern 2 with overlapping 'copy master prompt / paste / 100x faster' content — cross-reference one instead of repeating.

Remove marketing/padded phrasing ('100x faster', 'world-class', '⭐ Recommended', 'Innovation: 100x faster vs manual + zero human error') that adds context-load without actionable guidance.

Drop the standalone 'Reference Documents' list (and trim 'Assets & Templates'/'Scripts' sections) since each file is already signaled inline where it is used; rely on inline references to reduce redundant tokens.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose and padded: autonomous execution is described in four separate places (Quick Start, §3, a dedicated section, and Pattern 2) with repeated 'copy master prompt / paste / 100x faster' content, plus marketing fluff ('100x faster', 'world-class', '⭐ Recommended', 'Innovation: ... zero human error').	2 / 5
Actionability	Provides concrete executable commands ('python scripts/init_qa_project.py <project-name>', 'python scripts/calculate_metrics.py <path>'), specific file paths, and concrete tables (gates, severity); test-case writing defers to the template file rather than giving a complete inline example, a minor gap.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced with checkpoints ('Update tracking CSV immediately after EACH test (never batch)', quality gates table, P0 auto-escalation, Day 1 checkpoint); error-recovery/fix-retry feedback loops are only lightly elaborated, keeping it just below 5.	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references with a dedicated Reference Documents section; all referenced paths (references/, scripts/, assets/templates/*) verified to exist. Minor gaps from inlined detail tables and the duplicated autonomous-execution section.	4 / 5
	Total	14 / 20 Passed

Description

92%Weight 40%Scale 1-5

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, specific, third-person description that clearly states both capabilities and trigger conditions with concrete QA-domain terms. Minor room to add a few more natural synonyms for trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with comprehensive coverage: 'creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics... generating progress reports' plus 'Implements OWASP security testing and achieves 90% coverage targets'.	5 / 5
Completeness	Explicitly answers both what and when with concrete trigger phrases — 'This skill should be used when establishing comprehensive QA testing processes...' and a 'Use when creating test strategies, writing test cases...' clause; voice is third-person, so no specificity penalty applies.	5 / 5
Trigger Term Quality	Good coverage of natural phrases users would say ('test strategies', 'test cases', 'test plans', 'quality metrics', 'progress reports', 'OWASP security testing'), but a few common variations/synonyms (e.g. 'regression testing', 'test automation', 'test suites') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear QA-testing niche with distinctive terminology (Google Testing Standards, OWASP, P0-P4 classification, master prompts, autonomous execution, third-party handoffs) that minimizes overlap with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: daymade/claude-code-skills
Path: qa-expert/SKILL.md
Commit: b8556f2

Reviewed: 3 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.