Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thin catalogue stub that advertises an upstream skill rather than providing actionable guidance. It is reasonably organized and concise but lacks executable instructions, a real workflow, and local reference material.
Suggestions
Replace the URL pointer with concrete, executable steps for the core task (e.g., how to fetch a Figma frame via the MCP server and emit component code), or vendor the upstream reference files into ./references/ and link to them.
Add a concrete install command instead of "inspect the upstream README for exact paths", and include a validation step confirming the skill is available before invocation.
Remove the duplicated "What it does" section that restates the frontmatter description to recover tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and avoids explaining concepts Claude already knows, but it repeats the frontmatter description verbatim in "What it does" and spends tokens on catalogue metadata, so it could be tightened. | 2 / 3 |
Actionability | The body offers no executable guidance for the actual task; the only command is `open https://github.com/figma/skills`, and it describes/advertises rather than instructs, matching the level-1 anchor. | 1 / 3 |
Workflow Clarity | A minimal install-then-invoke sequence is present, but the install step is vague ("inspect the upstream README for exact paths") with no validation or checkpoints, fitting the level-2 anchor. | 2 / 3 |
Progressive Disclosure | Sections are clearly organized, but the real instructions are deferred to an external upstream URL rather than provided as well-signaled local bundle references, and no bundle files exist to navigate to. | 2 / 3 |
Total | 7 / 12 Passed |