SKILLEMALL.ai
GitHub ↗ RU Sign in

BB atelier

Orchestrating design-to-implementation pipelines (code to visual to code closed loop), persisting a project design system across agents. Not for a single prototype (Forge) or direction only (Vision).

simota/agent-skills Agent Skills author: simota 2 files body ≈ 5 981 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Orchestrating design-to-implementation pipelines (code to visual to code closed loop), persisting a project design system across agents.

As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice

ProcedureFigmaSoftware developmentInfrastructureAI 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
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
B
68/100
Nearly there
Inputs and preconditions w 11
30
Running it twice w 4
30
When it triggers w 12
50
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5981 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 68/100

  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 5 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5981 tokens
  • 85Steps. 108 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 199: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 108 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (1 of 1)

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