CD auto-design
Auto-select and apply design systems from awesome-design-md based on project type and task context
Auto-select and apply design systems from awesome-design-md based on project type and task context
As a process D 38/100 · Unfinished process — References files that are not bundled: design-extractor
ProcedureStripeMarketingAI and agentsDesigntype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: design-extractor
Process rating: all ten parameters 38/100
Will not run. References files that are not bundled: design-extractor
- 0Tools and files. 1 referenced file(s) missing: design-extractor
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (auto-design) differs from the folder (auto-design-clawhub)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 63 steps
- 100Execution cost. Instruction body is 2136 tokens
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 98: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 35 headings
- +3Step-by-step instructions: 63 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: suspicious
The skill has a coherent design-assistant purpose, but it should be reviewed because it can auto-activate broadly, fetch mutable remote Markdown, write project files, and includes instructions that can persist itself into an agent skill directory.
LLM: suspicious (high) · VirusTotal: · 16 Sept 2026