octopus-ui-ux-design

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-ui-ux-design/SKILL.md

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 a highly actionable, well-sequenced workflow with strong validation gates, but it is token-heavy due to inlined scripts and ships no bundle files, leaving referenced materials external and progressive disclosure only partially realized.

Suggestions

Move the Step 8 persistence script into scripts/persist-design.sh and inline only the one-line invocation plus the DESIGN_BODY contract, cutting roughly 120 lines from SKILL.md.

Ship skills/blocks/design-taste.md (or a local references/design-taste.md) in the bundle so the repeatedly-invoked slop checklist is actually available, and link it once rather than referencing an external plugin path.

Extract the Step 5b critique prompt and Step 4b shotgun dispatch prompt into references/ files referenced by name, keeping SKILL.md as an overview that points one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable rather than explanatory, but inlining a ~130-line defensive persistence shell script (flock/lockf + sha256sum/shasum fallbacks, noclobber, traps) and full AskUserQuestion templates makes it noticeably longer than a skill overview needs to be.	3 / 5
Actionability	Guidance is fully executable and copy-paste ready: exact search.py invocations with flags, a contrast-check.py command with exit-1 semantics, complete AskUserQuestion option sets, and a concrete persistence routine — with clearly marked placeholders for user-specific values.	5 / 5
Workflow Clarity	Steps 1–8 are explicitly sequenced with hard gates and validation checkpoints — the Step 3 preflight ("Only continue ... when preflight returns READY"), the Step 7 contrast checker (exit 1 → fix → re-run), and "Do NOT proceed with an uncritiqued direction" provide the feedback loops and checklists the 5 anchor calls for.	5 / 5
Progressive Disclosure	Section/step structure exists and references are signaled by path, but no bundle files are shipped (references/, scripts/, assets/ absent), the repeatedly-cited skills/blocks/design-taste.md is not bundled, and large scripts/prompts that belong in separate files are inlined.	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 distinctive, naming four concrete deliverables, but lacks an explicit "Use when..." trigger clause, which caps its completeness and leaves a few natural synonyms absent.

Suggestions

Append an explicit trigger clause, e.g. ". Use when the user asks to design a UI, create a design system, pick a color palette, choose fonts, or specify components for a new interface."

Add natural synonyms users actually say ("fonts", "colors", "design system") alongside "typography" and "palettes" to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete deliverables — "style guides, palettes, typography, and component specs" — but rests on a single verb ("Design"), so it falls just below the multi-action comprehensiveness of a 5.	4 / 5
Completeness	It clearly states the "what" (design UI/UX systems with named deliverables) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural terms like "UI/UX", "design", "palettes", "typography", and "component specs" give good keyword coverage, though common synonyms ("fonts", "colors", "design system") and extensions are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	"UI/UX systems ... component specs for new interfaces" carves a clear niche with low conflict risk, with only minor overlap against generic design or frontend-build skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: f9b8c92

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.