CC design-theme-guide
Design-token register: colour, typography, spacing and radius tokens with light and dark values, contrast ratio and WCAG level. Use for design system documentation.
Promises a design-token registry with colour, typography, spacing, and radius values for light and dark modes, complete with contrast ratios and WCAG levels for design system docs.
Quality score of 69 out of 100 with process score at 58 signals content exists but structure needs work. No critical issues, but two medium-to-low findings logged. Passed validation on Claude and Hermes without blocks, yet never ran on live models—sandbox only. Single file, no scripts.
Use if your team needs a token registry as a starting template. Install if you're prepared to refine: verify structure, bring process up to standard.
Design-token register: colour, typography, spacing and radius tokens with light and dark values, contrast ratio and WCAG level.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 164 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 5947 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
edit-residuethe text marks something as outdated (lines 234, 301, 428): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 5947 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 59 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 164: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.