BD figma-generate-diagram
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
Promises a prerequisite loader that fires before `generate_diagram` calls — meant to be a gatekeeper for Figma diagram work. Description cuts off mid-sentence, but the intent is clear: route to type-specific guidance and enforce Mermaid constraints.
Grade B with quality_score 78, but process_score dropped to 47 — red flag for logic issues. No model runs or sandbox tests. Eight files present, yet broken_references signals missing links. No critical findings, but absence of sandbox data leaves real-world behavior unclear.
Install if you're willing to verify the skill on your model first. The missing reference chain could break your diagram pipeline.
MANDATORY prerequisite — load this skill BEFORE every generatediagram tool call.
As a process D 47/100 · Unfinished process — References files that are not bundled: ../figma-use-figjam/SKILL.md
The same skill appears in 1 more place: opencode
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../figma-use-figjam/SKILL.md
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: ../figma-use-figjam/SKILL.md
- 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
- 30Running it twice. 9 mutating operations with no state check
- 70Failures and branches. 7 branches
- 85Steps. 30 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2345 tokens
- high The skill tells the model to perform an irreversible action with no human approval
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
- +1No license
- +2Single-language instructions
- +3Description length 778: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 30 items
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.