CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-polish

Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

70%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 pipeline is exceptionally actionable and clearly sequenced with strong validation checkpoints, error recovery, and sign-off gates — as an orchestration procedure it is close to exemplary. Its weaknesses are token efficiency (sustained defensive meta-prose justifying design decisions, with the routing and announcement rules stated multiple times) and progressive disclosure (long policy rationale inlined in SKILL.md instead of living in the already-referenced docs). Moving the three justification blockquotes and the team.size philosophy into a reference doc and cutting repetition would raise both dimensions without losing any executable guidance.

Suggestions

Move the 'Why production/ and not docs/', 'Why this does not violate the Collaboration Protocol', and team.size collapse-philosophy blocks into the already-referenced .claude/docs/ files, leaving one-line pointers — this would cut roughly a third of the body.

State the active-set routing rule once (in Phase 0) and reference it from Phase 2 and the announcement section instead of restating it three times.

Trim the duplicated 'See the Decision Points note above' phrasing and the closing maxim about surfaced constraints; the rule they restate is already explicit in the Decision Points paragraph.

DimensionReasoningScore

Conciseness

The body repeatedly explains and defends its own design rather than instructing: the "Why `production/` and not `docs/`" and "Why this does not violate the Collaboration Protocol" blockquotes, the "The collapse is correct" meta-commentary, and the closing maxim "a constraint that is enforced but never surfaced is indistinguishable..." are padded justification a competent reader does not need at this length. The active-set routing rule is stated three times (Phase 0 team.size, the announce-the-active-set note, and Phase 2), and the automation-mode paragraph says "See the Decision Points note above" twice in adjacent sentences. This matches anchor 2 — noticeably verbose with several unnecessary or padded sections — rather than 3, because the excess is sustained across multiple sections, not isolated.

2 / 5

Actionability

Guidance is fully executable: exact `subagent_type` names, a verbatim per-agent return contract, a fill-in template for the active-set announcement, a per-agent destination table with concrete file-naming patterns (`production/polish/[area]-report-[date].md`), and a phase-by-phase pipeline with explicit outputs. Every instruction Claude needs to run the skill is concrete and copy-paste ready, with none of it left as pseudocode.

5 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with parallelism explicitly marked (Phases 3 and 4 with Phase 2), and validation is thorough: Phase 0 resolves config before any spawn, the Error Recovery Protocol mandates verifying the named artifact is on disk before treating a phase as done, Phase 5 regression-tests each Phase 2–4 change by name, and Phase 6's sign-off ranking (NEEDS MORE WORK > NOT ASSESSED > READY FOR RELEASE) with named-gap reporting closes the loop. Error-recovery feedback (resume the agent naming the unmet contract) and the BLOCKED handling match the top anchor.

5 / 5

Progressive Disclosure

Section structure is good and external references (`.claude/docs/automation-modes.md`, `config-resolution.md`, `error-recovery-protocol.md`) are clearly signaled one level deep, but the ~230-line body inlines substantial policy content that belongs in those reference files — the full bounded-exception justification, the team.size scoping philosophy, and the production/-vs-docs/ rationale. That matches anchor 3: some structure, references present and signaled, but content that should be separate is inline; it is not 4 because the inlined policy blocks are large enough to obscure the pipeline itself.

3 / 5

Total

15

/

20

Passed

Description

58%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 about who acts and what happens, with a distinctive named-team framing, but it omits any explicit "when to use this" trigger guidance and lacks natural keyword variations users would say. Adding a "Use when polishing or optimizing a feature, improving frame rate, VFX, audio, or hardening before release" style clause would lift both completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when polishing or optimizing a feature before release — performance, frame rate, VFX, audio, or hardening' — to move completeness from 3 to 5.

Include natural trigger synonyms users would actually say (performance, frame rate, lag, VFX, audio, regression testing) rather than relying solely on agent names and 'polish'/'harden'.

State one or two of the concrete sub-actions (profiling against frame budgets, edge-case and regression testing) so the capability list is comprehensive rather than implied by roster names.

DimensionReasoningScore

Specificity

"Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area" names the concrete actor composition and two specific actions (optimize, harden). It falls just short of the 5 anchor because the action list itself is thin — profiling, VFX, audio, and testing capabilities are only implied via the agent names, not stated.

4 / 5

Completeness

The "what" is clear (orchestrate a named four-agent team to optimize and harden a feature), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely missing rather than merely implicit.

3 / 5

Trigger Term Quality

Natural terms like "polish", "optimize", "harden", "feature", and "area" are present, but common variations a user would actually say — "improve performance", "frame rate", "lag", "VFX", "audio", "regressions" — are absent. Keywords exist but coverage of synonyms and variations is incomplete, matching the anchor at 3 rather than the comprehensive coverage at 5.

3 / 5

Distinctiveness Conflict Risk

The named team roster and the "polish / optimize and harden" framing carve a fairly clear niche with distinct triggers. Minor overlap risk remains with sibling orchestrators in the same ecosystem (e.g. team-qa, team-release) whose descriptions would also open with "Orchestrate the [X] team", so it does not reach the clear-niche bar of 5.

4 / 5

Total

14

/

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-polish/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.