team-testing

Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on "team testing".

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/team-testing/SKILL.md

Quality

Content

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 orchestration skill that provides clear, actionable guidance for a multi-agent testing pipeline. Its strengths are the explicit delegation lock, concrete spawn templates, and clear progressive disclosure through role files. The main weakness is moderate verbosity—some sections could be tightened without losing clarity, particularly the model selection guide and completion action block.

Suggestions

Compress the Model Selection Guide table by removing the '(default)' repetition and merging the rationale into a single note about cost optimization overrides.

Consider moving the full Completion Action request_user_input block to a referenced file, keeping only a brief description in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill is fairly long but most content is structural (tables, templates, diagrams) that serves a purpose. However, some sections like the Model Selection Guide with '(default)' repeated four times and the verbose Completion Action block with full UI code add bulk without proportional value. The Delegation Lock table is thorough but could be more compact.	2 / 3
Actionability	The skill provides concrete, copy-paste-ready spawn_agent templates, specific tool call patterns, exact file paths, timeout values, and explicit allowed/blocked tool tables. The worker spawn template, parallel generation pattern, and timeout cascade are all directly executable.	3 / 3
Workflow Clarity	The multi-step pipeline (strategist -> generator -> executor -> analyst) is clearly sequenced with an ASCII architecture diagram, explicit validation via the Delegation Lock check, agent health reconciliation steps, timeout cascades (wait 30min -> STATUS_CHECK 3min -> FINALIZE 3min -> close), and GC loop coordination for error recovery. The error handling table provides explicit fallback paths.	3 / 3
Progressive Disclosure	The SKILL.md acts as a clear router/overview with well-signaled one-level-deep references to role files (roles/coordinator/role.md, roles/strategist/role.md, etc.) and spec files (specs/pipelines.md, specs/team-config.json). The Role Registry table provides a clean navigation index. Content is appropriately split between this overview and the referenced role/spec files.	3 / 3
	Total	11 / 12 Passed

Description

25%

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 description relies heavily on internal jargon and abstract concepts rather than concrete, user-facing actions. It fails to describe what specific testing tasks it performs and uses an artificial trigger phrase ('team testing') that users would rarely say naturally. The description would benefit significantly from listing concrete capabilities and including natural trigger terms.

Suggestions

Replace jargon like 'Generator-Critic loops' and 'dynamic layer selection' with concrete actions such as 'generate unit tests', 'identify untested code paths', 'validate test coverage metrics'.

Replace the artificial trigger 'team testing' with natural user phrases like 'write tests', 'improve test coverage', 'unit tests', 'integration tests', 'test suite'.

Add a clear 'Use when...' clause with realistic scenarios, e.g., 'Use when the user asks to write tests, increase test coverage, or generate test cases for their code.'

Dimension	Reasoning	Score
Specificity	The description uses abstract, jargon-heavy language like 'Generator-Critic loops', 'shared memory', and 'dynamic layer selection' without describing concrete actions. It does not list specific tasks the skill performs (e.g., 'generate unit tests', 'run test suites', 'measure coverage').	1 / 3
Completeness	It attempts to answer both 'what' (progressive test coverage through Generator-Critic loops) and 'when' (triggers on 'team testing'), but the 'what' is vague/jargon-laden and the 'when' trigger is artificially narrow and not a natural user phrase. The trigger clause exists but is weak.	2 / 3
Trigger Term Quality	The only explicit trigger is 'team testing', which is not a natural phrase users would say. It lacks common terms like 'unit tests', 'test coverage', 'write tests', 'integration tests', or 'test suite' that users would naturally use.	1 / 3
Distinctiveness Conflict Risk	The specific jargon ('Generator-Critic loops', 'shared memory', 'dynamic layer selection') and the narrow trigger phrase 'team testing' make it unlikely to conflict with other skills, but the domain of 'testing' is broad enough that it could overlap with other test-related skills.	2 / 3
	Total	6 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: catlog22/Claude-Code-Workflow
Commit: 07491b0

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