qa-expert
tessl i github:daymade/claude-code-skills --skill qa-expertThis 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
85%This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is moderate verbosity - some sections explain concepts Claude already knows (severity classifications, OWASP categories) and include generic guidance that could be inferred. The skill excels at providing concrete, executable patterns and clear navigation to detailed references.
Suggestions
Remove or condense the severity classification definitions (P0-P4) since Claude understands these concepts - just reference the classification system without explaining each level
Trim the OWASP coverage targets section to just list the categories without descriptions, or move detailed explanations to the referenced google_testing_standards.md file
| 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 Claude could infer. | 2 / 3 |
Actionability | Provides concrete, executable commands (python scripts/init_qa_project.py), specific file paths, clear templates, and copy-paste ready patterns. The Common Patterns section gives step-by-step actionable workflows that are immediately usable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The Ground Truth Principle section emphasizes critical validation steps, and workflows include feedback loops (e.g., 'Update CSV immediately after EACH test', auto-escalate P0 bugs). Quality gates provide clear pass/fail criteria. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview in main file and well-signaled 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 |
Activation
100%This is a strong skill description that clearly articulates specific QA testing capabilities with explicit trigger conditions. It uses third person voice appropriately, includes domain-specific terminology that users would naturally use, and distinguishes itself from general development skills through specific methodologies and standards references.
| 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 | Clearly 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 explicit 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 specifically on QA testing processes with distinct triggers like 'P0-P4 classification', 'Google Testing Standards', 'OWASP security testing', and 'QA team handoffs' that are unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
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.