Content
40%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized but essentially empty catalogue stub: it duplicates frontmatter metadata and points to an external GitHub repo instead of providing any executable guidance for the design-to-code task. Conciseness and structure are acceptable, but actionability and workflow clarity are low because no usable steps or commands exist.
Suggestions
Replace the "## How to use" meta-commentary with the actual upstream workflow steps or concrete commands (e.g. exact clone/copy paths and an install command) so the skill is actionable on its own.
Bundle or inline the core guidance (e.g. how to fetch a Figma frame via MCP and translate it to code) instead of only linking to the remote repository, which currently leaves actionability and workflow clarity near the bottom of the scale.
Remove the verbatim repetition of the description in "## What it does" and the duplicated upstream/category metadata in "## Source" to tighten the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short but not tight: "## What it does" repeats the frontmatter description verbatim ("Translate Figma designs into production-ready code with 1:1 visual fidelity. Useful for handing off Figma frames straight to a frontend agent."), and "## Source" restates the upstream URL and category already in the frontmatter. Mostly efficient with unnecessary duplication, matching anchor 3 rather than 4, which expects only minor trims. | 3 / 5 |
Actionability | The only executable content is a code block containing a comment and `open https://github.com/figma/skills`; the actual instruction "install the upstream bundle into your active agent's skills directory" gives no commands or steps, and the skill's real task (design-to-code translation) has no guidance at all. This is minimal concrete guidance with missing execution steps, matching anchor 2 rather than 3, which would require some concrete, usable guidance. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect upstream README → install the bundle → invoke by name or trigger phrase), but the steps are poorly defined with no install procedure, no handling of what to do after invocation, and no checkpoints. This matches anchor 2 (rough sequence, many gaps); it is not anchor 1 because a coherent ordering is present. | 2 / 5 |
Progressive Disclosure | The body is under 50 lines with clear sections (What it does, Source, How to use) and a single clearly signaled one-level pointer to the upstream repository. No local bundle files are referenced (references/, scripts/, assets/ do not exist, consistent with the body). It falls short of anchor 5 because the detailed material lives in a remote repo URL rather than a well-signaled bundled reference, making navigation dependent on an external resource. | 4 / 5 |
Total | 11 / 20 Passed |