SKILLEMALL.ai
GitHub ↗ RU Sign in

CD frontend-slides

OpenDesign as a worked AI-workflow example: how local agents read your files and design on your desktop — concretely. Built as a decision-grade AI literacy deck for teams new to AI, leadership.

nexu-io/open-design Agent Skills author: nexu-io Apache-2.0 7 files body ≈ 1 291 tokens Open the sourcegithub.com↗ analyzed 6 d ago

OpenDesign as a worked AI-workflow example: how local agents read your files and design on your desktop — concretely.

As a process D 44/100 · Unfinished process — References files that are not bundled: references/viewport-base.css

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: references/viewport-base.css
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/viewport-base.css
  • note frontmatter-key unknown frontmatter key "en_name"
  • note frontmatter-key unknown frontmatter key "zh_name"
  • note frontmatter-key unknown frontmatter key "en_description"
  • note frontmatter-key unknown frontmatter key "zh_description"
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "od"

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: references/viewport-base.css
  • 0Tools and files. 1 referenced file(s) missing: references/viewport-base.css
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 24 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1291 tokens
  • 100Running it twice. No mutating operations

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)
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 193: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 24 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.