CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

octopus-ui-ux-design

Design UI/UX systems with style guides, palettes, typography, and component specs for new interfaces

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/skill-ui-ux-design/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.

This is a highly operational, well-gated workflow: every phase has executable commands, explicit validation checkpoints, and error-recovery loops, and conditional branches state their activation conditions precisely. Its weaknesses are repetition of the enforcement mandates, a ~130-line bash script inlined where a bundled script should be, and no use of bundle files to keep SKILL.md closer to an overview. Tightening the repeated mandates and moving the persistence script and audit question sets into scripts/ and references/ files would improve both conciseness and progressive disclosure.

Suggestions

Move the Step 8 persistence logic into a bundled script (e.g., scripts/persist-design.sh) and invoke it with the design body, cutting ~130 lines from SKILL.md and fixing the largest progressive-disclosure gap.

State the "minimum 3 search.py calls" requirement once (in the HARD-GATE or Step 4) and remove the duplicated mandate from the enforced-mode preamble and step headers.

Extract the Step 7b AI Surface Audit questions and the Step 1 question sets into a references/ file, keeping only the summary and pointer inline, so SKILL.md reads as an overview with one-level-deep references.

DimensionReasoningScore

Conciseness

The body is mostly dense, actionable instruction with no basic-concept padding, but it repeats the "at least 3 search.py calls" mandate three times (the HARD-GATE block, the enforced-mode paragraph, and Step 4's "This is NOT optional") and inlines a ~130-line defensive bash persistence script in Step 8. This fits "mostly efficient but could be tightened" — it is not 2 because there is no concept explanation Claude already knows, and not 4 because the repeated mandates and the inlined script exceed minor over-explanation.

3 / 5

Actionability

Nearly every step ships copy-paste-ready material: exact bash with "${CLAUDE_PLUGIN_ROOT:-...}" fallback chains, seven concrete search.py invocations per domain, the full critique prompt, and the contrast-check.py call with argument format ("'<text-hex>:<bg-hex>' ... ':large'"). It falls short of 5 because Step 4b says "Dispatch to different providers for maximum diversity" without the actual dispatch command (unlike Step 5b's orchestrate.sh spawn), and Step 5's direction document format is left abstract ("Write the design direction as a structured section").

4 / 5

Workflow Clarity

Steps 1-8 are explicitly sequenced with blocking gates, conditional branches carry clear activation/skip conditions ("When fewer than 3 providers are available, skip to Step 5"), and validation is explicit with feedback loops: preflight terminates on MISSING_SEARCH_PY/MISSING_PYTHON, "Exit 1 means at least one pair fails WCAG AA — fix the palette and re-run before delivering", and the critique step mandates triage, revision, and a displayed diff. This matches the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

Step headers are clear, but no bundle files exist (no references/, scripts/, or assets/), and substantial content that belongs in separate files is inlined: the ~130-line persistence script (Step 8) should be a bundled script, and the ~45-line AI Surface Audit (Step 7b) and the full question sets belong in reference files. References to skills/blocks/design-taste.md and vendored search.py are clearly signaled but point outside this skill's bundle. This fits "some structure but content that should be separate is inline" — not 4, because the inlined script and absent bundle structure are more than minor organization gaps.

3 / 5

Total

15

/

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.

A solid, specific description that names its domain and four concrete deliverable types in natural language, but it omits any explicit "use when" trigger guidance, which caps completeness and limits trigger quality. The separate frontmatter trigger field contains strong trigger phrases, but the description itself must stand alone for discovery. Adding a "Use when the user wants to design a UI, pick a color palette, or create a style guide" clause would raise both completeness and trigger coverage.

Suggestions

Append an explicit trigger clause to the description, e.g., "Use when the user wants to design a UI, create a design system, pick a color palette, or choose fonts for an interface" — this addresses the completeness cap and mirrors the strong phrases already in the trigger field.

Include the natural synonym variations users actually say ("fonts", "colors", "design system", "dashboard") to lift trigger term coverage toward comprehensive.

Mention the remaining deliverables the skill produces (design tokens, page layouts, accessibility validation) to close the specificity coverage gap.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "style guides, palettes, typography, and component specs" — matching the anchor for several specific actions with minor gaps. It is not 5 because coverage is incomplete (design tokens, page layouts, and accessibility validation from the body are absent), and not 3 because it names more than 1-2 concrete actions.

4 / 5

Completeness

The "what" is clear ("Design UI/UX systems with style guides, palettes, typography, and component specs"), but there is no "Use when..." clause or equivalent; "for new interfaces" is a scope qualifier that only weakly implies when. Per the judging guideline, a missing explicit trigger clause caps completeness at 3 — it is not 4 because the "when" is at best weakly implied.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "style guides", "palettes", "typography", "UI/UX", "component specs". A few natural terms are missing (e.g., "fonts", "colors", "design system", "dashboard"), which fits the good-coverage-with-gaps anchor rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — designing UI/UX systems and deliverables "for new interfaces" — making it mostly distinct with only minor overlap risk against general frontend/styling skills. It is not 5 because no explicit distinct trigger phrases are given and adjacent web-design skills could still compete for the same requests.

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

skill_md_line_count

SKILL.md is long (627 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-ui-ux-design/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.