test-suite-architect

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

80%

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 ./skills/test-suite-architect/SKILL.md

The canonical home for this skill is qa-expert in daymade/claude-code-skills

Quality

Content

71%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.

The body is well-structured with strong progressive disclosure and mostly actionable, validated workflows. Its main weakness is conciseness: marketing fluff and repeated re-explanation of autonomous execution inflate the token budget.

Suggestions

Remove marketing language ('world-class', 'proven methodologies', '100x faster/speedup', '⭐ Recommended') and consolidate the autonomous-execution explanation into a single section instead of repeating it in Quick Start, Core Capability #3, the Autonomous Execution section, and the Common Patterns.

Tighten the Quality Metrics and Security Testing sections to rely more on the bundled references rather than restating OWASP threat lists inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and actionable, but padded with marketing language ('world-class', 'proven methodologies', repeated '100x faster/speedup' claims, '⭐ Recommended') and the autonomous-execution concept is re-explained in four separate sections, so it could be tightened.	3 / 5
Actionability	Provides concrete executable commands ('python scripts/init_qa_project.py', 'python scripts/calculate_metrics.py'), real scripts, and specific formats (TC-[CATEGORY]-[NUMBER], bug fields, quality-gates table) with only minor gaps left to reference files.	4 / 5
Workflow Clarity	Numbered sequences with validation checkpoints (quality gates, Ground Truth Principle, 'never batch' instruction, metrics feedback loop) are present, so the batch-operation cap does not bind; only minor validation gaps remain.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references—all referenced files in references/, scripts/, and assets/templates/ verified to exist—and dedicated Reference/Assets/Scripts sections making navigation easy.	5 / 5
	Total	16 / 20 Passed

Description

88%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.

The description is specific, complete, and trigger-rich, clearly stating both capabilities and when to invoke the skill. Its only weakness is somewhat broad phrasing and a lack of keyword synonyms, which slightly raises conflict risk.

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…generating progress reports' plus 'OWASP security testing' and '90% coverage targets'—giving comprehensive coverage rather than just several.	5 / 5
Completeness	Explicitly answers both what (the enumerated QA actions) and when ('This skill should be used when…', 'Use when creating test strategies, writing test cases…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-keyword coverage ('test strategies', 'test cases', 'bug tracking', 'quality metrics', 'OWASP', 'coverage'), but it lacks common synonyms and file-extension variants, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Google Testing Standards / OWASP / P0-P4 / quality-metrics triggers carve a clear QA niche, but 'any software project' breadth leaves minor overlap risk with general testing skills.	4 / 5
	Total	18 / 20 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: zebbern/claude-code-guide
Path: skills/test-suite-architect/SKILL.md
Commit: 9d252b3

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