CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-ui

Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish. Uses /ux-design, /ux-review, studio templates.

Quality

73%

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-ui/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 body is an exceptionally actionable, well-gated orchestration pipeline with explicit validation and error-recovery loops — actionability and workflow clarity are top-tier. Its weaknesses are token weight (heavy inline justification prose) and structure (a monolithic single file where policy rationale is inlined and templates are named without paths).

Suggestions

Move the multi-line rationale blocks (the Collaboration Protocol exception justification, the team.size collapse philosophy, the repeated NOT ASSESSED policy) into a reference doc under the skill bundle and keep only the operative rule inline, cutting the body substantially.

Give the four studio templates (ux-spec.md, hud-design.md, interaction-pattern-library.md, accessibility-requirements.md) explicit paths or bundle locations so they are discoverable rather than name-only references.

State the NOT ASSESSED carry-forward rule once (Phase 1a) and reference it from Phase 4 and Output instead of restating the full wording in all three places.

DimensionReasoningScore

Conciseness

The body is dense and project-specific with no explanation of concepts Claude already knows, but carries substantial defensive rationale that could be trimmed — the "Why this does not violate the Collaboration Protocol" blockquote, the ~20-line team.size collapse justification, the twice-stated "enforced but never surfaced" philosophy, and NOT ASSESSED rules repeated across Phase 1a, Phase 4, and Output. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than 2, since the padding is load-bearing policy rationale rather than generic filler.

3 / 5

Actionability

Guidance is fully executable: verbatim return-contract prompt text, verbatim announce-the-active-set and NOT ASSESSED report strings, an exact per-agent write-path table, exact AskUserQuestion option sets, and an exact Phase 0 bash command. Specific templates cover the common cases (HUD vs spec, pattern library present vs absent, engine configured vs not), matching the top anchor for an instruction-only skill.

5 / 5

Workflow Clarity

Phases 0–5 are explicitly sequenced with validation checkpoints (Phase 1c APPROVED gate, verify-artifact-before-phase-done, report every input document's status) and genuine feedback loops (NEEDS REVISION → revise the same spec → re-run review; BLOCKED → surface, partial report, resume naming the unmet contract). This matches "clear sequence with explicit validation steps; feedback loops for error recovery".

5 / 5

Progressive Disclosure

Deep material is correctly delegated one level deep with explicit paths ("Full procedure: .claude/docs/error-recovery-protocol.md", automation-modes.md, config-resolution.md), but the skill is a single ~300-line monolith with no bundle, inlining long policy rationale that belongs in reference files, and the named templates (ux-spec.md, hud-design.md, interaction-pattern-library.md, accessibility-requirements.md) are listed with no resolvable path or location. This lands on "some structure but could be better organized; content that should be separate is inline".

3 / 5

Total

16

/

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 clearly states what the skill does and carves a distinct niche, but has no "Use when..." trigger guidance and few natural user phrasings, which caps both completeness and trigger-term quality. Adding an explicit when-to-use clause with concrete trigger phrases (screen, menu, HUD, UI feature) would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or redesigning a UI feature — screens, menus, HUDs — that needs the full design-through-polish pipeline; use /quick-design for small UI changes."

Include the natural terms users would say ("screen", "main menu", "HUD", "interface", "UI feature") so the skill surfaces for those phrasings instead of only "UI/UX pipeline" jargon.

State the concrete actions the orchestration performs (spawn UX/design/implementation/review agents, gate phases on user decisions) rather than only naming the pipeline stages.

DimensionReasoningScore

Specificity

"authoring, visual design, implementation, review, polish" lists five concrete pipeline actions and names the sub-skills used (/ux-design, /ux-review), matching the "several specific actions; minor gaps" anchor. Not 5 because the actions are stage names rather than fully elaborated capabilities, and what the skill concretely does (multi-agent delegation, gating, review passes) is only implied.

4 / 5

Completeness

The "what" is clear ("Orchestrate the UI team through the UX pipeline — authoring, visual design, implementation, review, polish"), but there is no "Use when..." clause or equivalent trigger guidance; "Uses /ux-design, /ux-review, studio templates" describes tooling, not invocation conditions, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ("UI", "UX", "visual design", "implementation", "review", "polish") but the natural phrases a user would actually say — "screen", "menu", "HUD", "interface", "build a UI" — are absent, matching "some relevant keywords but missing common variations or synonyms". Not 4 because the coverage of natural user phrasing is thinner than "PDF files, forms, document extraction"-style coverage.

3 / 5

Distinctiveness Conflict Risk

The full-pipeline team-orchestration niche is clearly distinct from generic skills and is positioned against the named /ux-design and /ux-review, giving "mostly distinct; minor overlap risk with closely related skills". Not 5 because with no trigger phrases, distinguishing it from closely related /ux-design or /quick-design for a request like "design the inventory screen" relies on subtle wording.

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