SKILLEMALL.ai

BC figma-create-new-file

Always use this skill when the user wants to create a new Figma Design, FigJam, or Slides file. You MUST invoke this skill BEFORE every `create_new_file` tool call.

The skillemall take

The skill intercepts Figma file creation requests and runs itself before the main tool. Contains 399 tokens without scripts. Tests show grade B: quality 84%, process 62%, safety 100%. No critical errors, linter clean.

No sandbox runs or model tests. Works across Claude, Cursor, Gemini, and others. Install if you need a pre-creation hook before file generation—the code is solid and doesn't break. Just confirm you actually need this layer of control.

anomalyco/opencode Claude Code author: anomalyco MIT 1 file body ≈ 399 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Always use this skill when the user wants to create a new Figma Design, FigJam, or Slides file.

As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

GeneratorFigmaDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: opencode

How to improve

    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: 1. 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 62/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
    • 30Running it twice. 10 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 8 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 399 tokens

    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 164: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 8 items
    • +4Has examples (1 code blocks)

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