Content
47%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 lean, well-organized catalogue stub that points to an upstream repo, but it provides almost no executable guidance or an actual workflow for the skill's stated purpose. Everything actionable is delegated to an external README that the reader must fetch and interpret.
Suggestions
Replace the vague install instruction with concrete steps: the exact git clone command, the target skills-directory path, and a one-line verification that the skill was installed.
Add a minimal 'Generating a screen' workflow (input → component/token mapping → validate against the design system) so the file carries some of the skill's own guidance rather than only a redirect.
Drop the verbatim repetition of the frontmatter description in 'What it does' or replace it with genuinely new detail (supported input types, output structure).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short with clear sections and no padding about concepts Claude already knows, so it broadly respects the token budget. Not 5 because the 'What it does' section repeats the frontmatter description verbatim and 'Curated from Figma's MCP server guide' plus the OpenDesign catalogue explanation add little actionable value. | 4 / 5 |
Actionability | The only concrete command is a bash block containing a bare 'open https://github.com/figma/skills', while the actual instruction — 'install the upstream bundle into your active agent's skills directory' — is left as a high-level hint with no paths, commands, or steps. Not 3 because there is no executable or complete guidance for even the setup task; not 1 because at least one concrete command and a specific repo URL are given. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect the upstream README → install the bundle → invoke the skill), but the steps are poorly defined — there is no actual workflow for building or updating Figma screens, no validation of a successful install, and the 'how' is deferred entirely to an external README. Not 3 because the gaps are too large for the sequence to be followed as written. | 2 / 5 |
Progressive Disclosure | The body is well-organized into short sections and the pointer to detailed material (the upstream repo URL) is clearly signaled and only one level deep; no bundle files exist in references/, scripts/, or assets/ to organize. Not 5 because the detailed content lives behind an external GitHub URL rather than bundled, on-disk references, so navigation is not self-contained. | 4 / 5 |
Total | 12 / 20 Passed |