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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/octopus-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 highly actionable with a clearly sequenced, validation-gated workflow, but it is verbose with enforcement rhetoric and monolithic — substantial content (the persistence script, critique prompt) is inlined rather than split into bundle files.

Suggestions

Move the ~130-line persistence bash script into a scripts/ file and reference it, cutting the largest inline block from SKILL.md.

Trim redundant enforcement framing ('MANDATORY - CANNOT SKIP', 'HARD-GATE', repeated 'You MUST') to one clear statement per gate.

Extract the design-taste checklist and full critique prompt into references/ files referenced one level deep, so SKILL.md reads as an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly real instruction and executable code rather than concept explanation, but it carries noticeable enforcement-rhetoric padding ('MANDATORY - CANNOT SKIP', 'HARD-GATE', repeated 'You MUST') and a ~130-line inlined persistence bash script that could be tightened or externalized.	3 / 5
Actionability	Provides copy-paste-ready AskUserQuestion blocks with exact options, concrete search.py invocations with flags and file paths, a contrast-check.py call with argument syntax, and a complete persistence script — fully executable with examples covering the common cases.	5 / 5
Workflow Clarity	An explicitly sequenced STEP 1→8 pipeline with validation checkpoints (Step 3 preflight terminating on MISSING, Step 7 contrast audit with exit-1→fix→re-run, slop and completeness checks) and feedback loops for error recovery.	5 / 5
Progressive Disclosure	Section headers and inline-code reference signaling exist, but the skill ships no bundle (no references/scripts/assets) and inlines large content that belongs in separate files — the persistence script and full critique prompt — while its references point to external plugin paths rather than a local bundle.	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 clearly states what the skill produces and lists concrete deliverables, but it omits any explicit 'when to use' trigger clause, which caps completeness and limits trigger clarity.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when designing a new interface, building a design system, or choosing colors, typography, and component specs').

Add common synonyms users say ('design system', 'color scheme', 'wireframes') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names four concrete deliverables — 'style guides, palettes, typography, and component specs' — which is several specific actions, though the leading verb 'Design UI/UX systems' stays somewhat abstract, keeping it just below comprehensive.	4 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance; 'for new interfaces' only weakly implies the trigger, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('UI/UX', 'style guides', 'palettes', 'typography', 'component specs', 'interfaces'), but lacks synonyms and file-extension variants that would push it to full coverage.	4 / 5
Distinctiveness Conflict Risk	The UI/UX-design niche with concrete deliverable lists is mostly distinct from other skills, with only minor overlap risk against general design or frontend skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (603 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: skills/octopus-ui-ux-design/SKILL.md
Commit: 805d58c

Reviewed: 24 hours 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.