CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ux-review

Validate a UX spec, HUD design or pattern library — accessibility, GDD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.

Quality

77%

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/ux-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

This is a strong, highly actionable review-gate skill: a clearly sequenced five-phase workflow, concrete file paths and tool invocations, explicit edge-case and fallback logic, and a complete output template. The only meaningful costs are token weight from inlining all three document-type checklists and some rule-justification prose that could be trimmed or moved to a reference. It would score higher on progressive disclosure if the 3B/3C checklists and policy notes were split into one-level-deep reference files.

DimensionReasoningScore

Conciseness

The checklists are terse and everything is project-specific policy Claude could not know; there is no general-knowledge padding. Minor instances of over-explanation could be trimmed: the NOT ASSESSED ranking rationale ("a gap somebody found is more actionable than one nobody could look for, so it must not displace them") and meta-commentary like "The same rule lives in /team-ui Phase 4 and is mirrored here so the two cannot drift". Fits anchor 4; not 5 because those passages spend tokens justifying rules rather than stating them.

4 / 5

Actionability

Fully executable for an instruction-only skill: exact file paths (design/ux/hud.md, design/accessibility-requirements.md, project.yaml platform keys), an exact tool invocation ("Grep tool (pattern ^#, content mode)"), concrete fallback/classification rules, and a copy-paste-ready Phase 4 report template covering all four verdicts. Specific examples cover the common cases (per-file, all, hud, patterns, no argument).

5 / 5

Workflow Clarity

Clear five-phase sequence with explicit checkpoints: argument parsing with per-case routing, context loading with fallback chains, three document-type checklists, a templated verdict, and a collaborative protocol. Error-recovery paths are explicit (unreadable file or missing source of truth → NOT ASSESSED with the named missing input; re-run only on new inputs). The skill is read-only, so the destructive/batch validation cap does not apply, and "all" batch mode defines its output ordering.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized with clear phase headers, so navigation is easy. Minor gaps: all three checklists (3A/3B/3C) are inlined so validating one document type carries all three in context, and ~30 lines of NOT ASSESSED/N/A policy blockquotes could live in a reference file. Fits anchor 4; not 3 because nothing that clearly belongs in a separate file is buried, and not 5 because the inlined per-document-type checklists and inline policy prose exceed a lean single-file overview.

4 / 5

Total

18

/

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 and distinctive within its game-dev UX niche, clearly stating what it validates and the verdict vocabulary it produces. Its main weakness is the complete absence of "when to use it" guidance and natural trigger phrasing, which caps both completeness and trigger-term quality. Adding a "Use when..." clause with the skill's natural invocation contexts (after /ux-design, before handoff, "review this UX spec") would lift it substantially.

Suggestions

Add an explicit "when" clause, e.g.: "Use when a UX spec, HUD design, or interaction pattern library needs review before implementation handoff — after /ux-design, before ui-programmer/art-director handoff, or at the Pre-Production gate check."

Include natural trigger phrasings users would actually say ("review this UX spec", "check the HUD design", "audit accessibility of this screen") to improve trigger-term coverage.

Briefly state the output (a review report with blocking/advisory issues and a gate verdict) so the "what" covers the deliverable, not just the checked dimensions.

DimensionReasoningScore

Specificity

Names several concrete specifics — "Validate a UX spec, HUD design or pattern library", the review dimensions "accessibility, GDD alignment, readiness", and the four verdict levels — but stops short of comprehensive coverage (e.g., no mention of the report/gate output or blocking-vs-advisory findings). More specific than anchor 3's 1-2 actions, not the full action coverage of anchor 5.

4 / 5

Completeness

The "what" is clear (validate three named document types across three named dimensions with four named verdicts), but there is no "when" clause — no "Use when..." or equivalent trigger guidance — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"UX spec", "HUD design", "pattern library", and "GDD" are natural domain keywords, but the description omits common variations and synonyms users would say ("review my spec", "check accessibility", "audit the HUD") and has no use-when phrasing. Fits anchor 3: some relevant keywords, missing variations.

3 / 5

Distinctiveness Conflict Risk

"HUD design", "GDD alignment", and "pattern library" carve a distinct game-dev UX niche with dedicated triggers, leaving only minor overlap risk with closely related skills (e.g., a generic accessibility-audit or design-review skill). Fits anchor 4; not 5 because "accessibility" and "readiness" alone could pull in general design-review requests.

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/ux-review/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.