octopus-ui-ux-design

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and clearly sequenced with strong validation feedback loops, but it is longer than necessary and keeps sizable template/critique material inline rather than offloading it to bundle files. Extracting the banner, comparison-board, and critique-prompt templates into references would improve both conciseness and progressive disclosure.

Suggestions

Extract the large display-banner and comparison-board templates into a references/ file (e.g. templates.md) and link to it, reducing inline padding.

Move the full adversarial-critique prompt block into a separate reference and keep only the dispatch logic and dimensions list inline.

Tighten the provider-availability prose; the repeated MANDATORY/HARD-GATE framing is effective but could be condensed without losing the enforcement signal.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence and avoids explaining basic concepts, but it carries padded template blocks (banner text, full comparison-board mockups, provider dispatch loops) that could be tightened, so it is mostly rather than maximally efficient.	2 / 3
Actionability	It provides fully executable bash/python commands with concrete flags (search.py --domain, --variance/--motion/--density, contrast-check.py with exit-1 semantics) and copy-paste AskUserQuestion calls, matching the anchor for copy-paste-ready guidance.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (STEP 1-8) with mandatory validation checkpoints and feedback loops: the accessibility audit is 'do not eyeball' with contrast-check exit 1 forcing fix-and-rerun, and the adversarial critique step requires revise-before-commit.	3 / 3
Progressive Disclosure	No bundle files exist in references/scripts/assets, yet the body is a single ~400-line file with full critique prompts and template blocks inline; external paths (skills/blocks/design-taste.md, vendors/.../search.py) are one level deep and signaled, but content that could be split out is not.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 about UI/UX design deliverables, but it lacks an explicit 'Use when...' trigger clause and misses several common user-facing terms (design system, tokens, wireframes). Adding a use-when clause and broader trigger vocabulary would lift completeness and trigger-term quality to the top level.

Suggestions

Add an explicit 'Use when...' clause naming the situations that should trigger this skill (e.g., 'Use when designing a new interface, building a design system, or defining tokens and component specs').

Broaden trigger terms to include common variations users actually say: 'design system', 'design tokens', 'color palette', 'wireframes', and 'component library'.

Keep the concrete deliverables list but pair each with the corresponding trigger term so both what and when are explicit.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete deliverables — 'style guides, palettes, typography, and component specs' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It clearly answers what the skill does but provides no 'Use when...' clause; the only trigger cue ('for new interfaces') is implied rather than explicit, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	It covers natural design terms ('UI/UX systems', 'style guides', 'palettes', 'typography') but omits very common variations a user would say such as 'design system', 'design tokens', and 'wireframes', which the body itself treats as central.	2 / 3
Distinctiveness Conflict Risk	The UI/UX-design niche is well-defined with distinct design-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-ui-ux-design/SKILL.md
Commit: 9f39f0c

Reviewed: 2 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.