SKILLEMALL.ai
GitHub ↗ RU Sign in

CB understand-figma

Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.

Egonex-AI/Understand-Anything Claude Code author: Egonex-AI MIT 3 files · 2 scripts body ≈ 953 tokens Open the sourcegithub.com↗ analyzed 7 d ago

Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design…

As a process B 65/100 · Nearly there — weak spots: result and completion, when it triggers

IntegrationFigmaDesigntype 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
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
When it triggers w 12
20
Failures and branches w 10
55
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: Understand-Anything

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. 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")
  • note edit-residue the text marks something as outdated (lines 17): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 65/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 100Steps. 16 steps
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 953 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 197: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (4 code blocks)

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

In the sandbox The scripts kept to themselves

The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

Запущено 2 скрипта; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

figma-merge.mjsничего за пределами своей папки
figma-scan.mjsничего за пределами своей папки

20 Oct 2026