CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-qa

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/team-qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 content is an exceptionally actionable, well-gated orchestration pipeline — every phase has concrete inputs, exact paths, decision points, and verification steps. Its weaknesses are token efficiency (multiple defensive rationale blockquotes that read as design documentation) and progressive disclosure (a monolithic single file where rationale and templates could be split into reference files).

Suggestions

Move the multi-paragraph "Why..." rationale blockquotes (Collaboration Protocol exception, verdict precondition, Phase 4 path naming) into a reference file such as references/rationales.md, or compress each to a single line, keeping SKILL.md focused on executable instruction.

Split the sign-off report template, evidence protocol details, and the announce-the-active-set worked example into reference files, keeping the body as a phase-by-phase overview.

Tighten the Phase 0 team.size discussion — the "phase gate" definition and collapse rationale restate the same point several times and could be roughly halved without losing the rule.

DimensionReasoningScore

Conciseness

The body is dense with project-specific policy and never explains concepts Claude already knows, but several multi-paragraph rationale essays ("Why this does not violate the Collaboration Protocol", "Why the precondition exists", the team.size collapse discussion) are design justification rather than executable instruction and could be tightened or moved out; it is above 2 because nearly every sentence carries project-specific instruction rather than generic padding.

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact glob patterns ("production/sprints/sprint-*.md"), exact output paths ("production/qa/test-cases/[story-slug]-cases.md"), full AskUserQuestion option blocks, report templates, and precise naming rules ("BUG-[NNNN].md", highest ID plus one, zero-padded) — fully executable for an orchestration skill.

5 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with explicit validation checkpoints: smoke-check gating before proceeding, artifact-on-disk verification before a phase counts as done ("a named artifact that is not on disk is a failed phase"), verdict cross-checking before writing, and a full error-recovery protocol — matching the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

Section structure and phase headers are good and external detail docs (.claude/docs/automation-modes.md, error-recovery-protocol.md, templates/test-evidence.md) are referenced, but the skill is a monolithic ~370-line file with no bundle directory: rationale essays, the announce-the-active-set example, and full report templates are inlined where a reference file would serve better; it is above 2 because structure exists and references are clearly signaled, below 4 because substantial content that belongs in separate files is inline.

3 / 5

Total

16

/

20

Passed

Description

66%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 and action-oriented, clearly conveying a multi-agent QA orchestration workflow with concrete phase activities. Its main weakness is the complete absence of any "when to use this" trigger guidance, which caps completeness and limits discoverability. Adding an explicit trigger clause would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to run a QA cycle, test a sprint or feature, or produce a QA sign-off report."

Broaden trigger terms with natural variations users would say: "quality assurance", "manual QA", "test cases", "regression testing".

Mention bug report filing and evidence capture in the capability list to round out coverage of what the cycle actually produces.

DimensionReasoningScore

Specificity

"qa-lead strategy and test plan, qa-tester case writing, execution, sign-off" lists several concrete, distinct actions, matching the anchor for several specific actions with minor gaps; it stops short of anchor 5 because it omits capabilities the body covers (bug report filing, evidence capture, config resolution).

4 / 5

Completeness

The "what" is clear and concrete (orchestrating a QA team through a named cycle with subagent roles), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the judging guidelines; it is above 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Natural terms a user would say are present — "QA", "testing cycle", "test plan", "sign-off" — giving good keyword coverage, but common variations like "quality assurance", "manual QA", or "regression testing" are missing, so it does not reach comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The full-cycle orchestration niche with named subagents (qa-lead, qa-tester) is mostly distinct, with only minor overlap risk against closely related QA-family skills the project also defines (e.g. /smoke-check, /bug-report); it is not 5 because those adjacent skills share trigger vocabulary like "testing" and "QA".

4 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/team-qa/SKILL.md

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.