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 tidy catalogue stub that outsources the real workflow to an upstream GitHub repo, so structure and brevity score well while actionability and workflow clarity are weak.
Suggestions
Replace or augment the `open https://github.com/figma/skills` hint with the concrete install command for the upstream bundle (e.g., the exact skills-directory path and clone/copy step).
Inline a minimal executable Code Connect example (e.g., a sample figma.config.json snippet or `npx figma-mcp` command) so the skill is usable without leaving the file.
Add a verification step (e.g., confirm the component mapping renders or that the bundle is discoverable by name) to give the rough sequence a real checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-sectioned without explaining concepts Claude already knows; only the meta sentence about advertising in Open Design could be trimmed. | 4 / 5 |
Actionability | The only command is `open https://github.com/figma/skills`, which merely points to the upstream README; the actual Code Connect task has no concrete executable steps. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect upstream, install bundle, invoke skill) but the key install step has no real command and no checkpoints, leaving large gaps. | 2 / 5 |
Progressive Disclosure | Content is cleanly split into What it does / Source / How to use with a clearly signaled one-level pointer to the upstream repo; minor gaps only because no local bundle files exist. | 4 / 5 |
Total | 12 / 20 Passed |