AC design-hub
Create and operate a local Design System Hub that stores multiple design systems, generates complete entries from screenshots, URLs, or written style descriptions, and exposes browsable documentation, live mocks, copied tokens, DESIGN.md, standalone HTML, and JSON APIs. Use when the user asks to initialize a local design-system site or service, add or extract a design system, analyze UI screenshots into tokens and components, manage a design-system library, or export design-system documentation.
Create and operate a local Design System Hub that stores multiple design systems, generates complete entries from screenshots, URLs, or written style…
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenassets/template/src/data/qoderwork.ts:144High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){ name: 'Extensions', label: '扩展与技能', paths: ['M9 4h6v…V4Z'] },quoted
Files scanned: 25. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/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
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 63 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2673 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (13 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 500: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 63 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.