create-color
Generate color annotation specifications mapping UI elements to design tokens. Use when the user mentions "color", "color annotation", "color spec", "tokens", "design tokens", or wants to document which color tokens a component uses.
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.cursor/skills/create-color/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description with an explicit 'Use when...' clause and strong trigger term coverage. Its main weakness is that the 'what' portion could be more specific by listing additional concrete actions beyond the single high-level capability. Overall, it's a strong description that would perform well in skill selection.
Suggestions
Add 2-3 more specific actions to the 'what' portion, e.g., 'Generate color annotation specifications mapping UI elements to design tokens, produce token-to-hex reference tables, and create component-level color documentation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (color annotation specifications) and one core action (mapping UI elements to design tokens), but doesn't list multiple concrete actions like generating token tables, exporting specs, or validating token usage. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate color annotation specifications mapping UI elements to design tokens) and 'when' (explicit 'Use when...' clause with specific trigger terms and a scenario description). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'color', 'color annotation', 'color spec', 'tokens', 'design tokens', and the use-case phrase 'document which color tokens a component uses' covers how users would naturally phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | This is a very specific niche — color annotation specs and design token mapping — that is unlikely to conflict with general design, theming, or code generation skills. The trigger terms are distinct and narrowly scoped. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent workflow clarity, providing complete executable code and a well-structured multi-step process with validation checkpoints. However, it is severely hampered by its monolithic structure — at 700+ lines with duplicated code blocks and inline scripts that should be external files, it wastes enormous context window space. The Notes section largely repeats information from the workflow steps, further inflating token cost.
Suggestions
Extract the large JavaScript code blocks (Step 4b extraction script, Strategy A/B rendering scripts) into separate referenced files (e.g., scripts/extraction.js, scripts/render-strategy-a.js) and reference them with clear links
Deduplicate shared utility functions (loadAllFonts, loadFontWithFallback, enableNestedBooleans) into a single shared utilities reference rather than repeating them in both Strategy A and Strategy B scripts
Remove or drastically reduce the Notes section at the end — most bullet points restate information already present in the workflow steps
Consider moving the MCP adapter table to a separate shared reference file since it likely applies across multiple skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~700+ lines with massive inline JavaScript code blocks that could be referenced as external files. There is significant duplication between Strategy A and Strategy B scripts (loadAllFonts, loadFontWithFallback, enableNestedBooleans are repeated verbatim). The Notes section at the end repeats information already stated in the workflow steps. | 1 / 3 |
Actionability | The skill provides fully executable JavaScript code for every step, with specific placeholder patterns, concrete MCP tool calls, and copy-paste ready scripts. Every step has precise, executable guidance with no ambiguity about what to run. | 3 / 3 |
Workflow Clarity | The workflow has a clear numbered checklist with explicit validation steps (Step 8 audit, Step 12 visual validation with up to 3 fix iterations). Multi-step processes are well-sequenced with clear dependencies between steps, and the MCP adapter table provides clear branching logic. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of content with massive code blocks inline. The extraction script alone is ~150 lines, and Strategy A/B rendering scripts are each ~150+ lines. These should be in separate referenced files. The MCP adapter table, while useful, adds significant length. Only one external reference exists (agent-color-instruction.md) but the skill itself desperately needs to offload code to external files. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1191 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- redongreen/uSpec
- Commit
b1213ef
- 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.