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

78%

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

57%

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

The skill is well-structured with excellent progressive disclosure and good sequencing, but it is verbose and promotional, and its core workflows lean on references rather than inline executable guidance. Tightening marketing language and adding explicit validation loops for batch tracking would raise the weaker dimensions.

Suggestions

Trim promotional repetition ('100x faster', 'world-class', '⭐ Recommended') to reduce token overhead and respect Claude's intelligence on QA basics.

Inline a minimal copy-paste test-case example and autonomous-execution command instead of only describing them and pointing to references.

Add an explicit validate-fix-retry feedback loop for batch test execution tracking (e.g., verify CSV row matches test doc after each update before proceeding).

Dimension	Reasoning	Score
Conciseness	The ~280-line body is padded with promotional language ('world-class', '100x faster execution', '⭐ Recommended') and repeats the autonomous-execution value proposition across multiple sections, though it stops short of teaching foundational concepts Claude already knows.	2 / 3
Actionability	Concrete executable commands exist for init and metrics, but the core workflows (test-case writing, autonomous execution) are described abstractly and delegated to bundled references rather than given as copy-paste-ready code inline.	2 / 3
Workflow Clarity	Multi-step processes are clearly numbered and the Ground Truth Principle plus quality gates provide some checkpoints, but batch test-execution tracking lacks an explicit validate-fix-retry feedback loop, which the rubric caps at 2 for batch operations.	2 / 3
Progressive Disclosure	SKILL.md serves as a clear overview with well-signaled one-level-deep references to real bundle files (all referenced paths in references/, scripts/, and assets/templates/ exist), organized into dedicated navigation sections.	3 / 3
	Total	9 / 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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a distinct QA-testing niche. Minor over-claims ('comprehensive', 'achieves 90% coverage') slightly dilute precision but do not change the rating.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'writing test cases following Google Testing Standards', 'tracking bugs with P0-P4 classification', 'calculating quality metrics', and 'OWASP security testing', matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (establishing QA testing processes with listed capabilities) and 'when' via 'This skill should be used when...' and 'Use when...' trigger clauses.	3 / 3
Trigger Term Quality	Uses natural user-facing terms including 'test strategies', 'test cases', 'test plans', 'tracking bugs', 'quality metrics', and 'progress reports' that a user needing QA would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear QA-testing niche with distinct triggers (Google Testing Standards, OWASP, P0-P4, quality gates) unlikely to overlap with other skills, despite the broad 'any software project' framing.	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: zebbern/claude-code-guide
Path: skills/test-suite-architect/SKILL.md
Commit: af7d491

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