BD figma-code-workflows
Import or upload local HTML or project files into Figma, choose editable Design frames, runnable Code Layers or standalone Code (also known as Make), and repair imported previews. Use only when the user explicitly names editable Design layers, a runnable Code Layer, or a standalone Code/Make file, or supplies a Figma file key/link as the import destination. Generic code or code-component requests need output clarification before using this workflow.
The skill promises to import HTML and projects into Figma, select editable frames, and run code from layers. It only works if you explicitly name a Design Layer, Code Layer, or provide a Figma file link—otherwise it asks for clarification.
Grade B with 77% quality indicates working state, but rough edges show. No critical errors, though process score of 49% suggests the workflow logic needs refinement. Supports many platforms including Claude and Cursor; single compact file (1009 tokens). No model runs or sandbox tests—unclear how it handles real Figma files.
Install if you work with Figma and can give precise commands. Vague requests like "put code in design" will get a request to rephrase.
Import or upload local HTML or project files into Figma, choose editable Design frames, runnable Code Layers or standalone Code (also known as Make), and…
As a process D 49/100 · Unfinished process — weak spots: steps, result and completion, failures and branches
How to improve
- 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 49/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1009 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 453: enough signal without eating the budget
- +4Structure: 3 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.