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, but it contains almost no executable guidance for the skill's advertised purpose — every substantive step is delegated to an upstream GitHub repository. What remains is essentially metadata plus a link, which leaves both actionability and workflow clarity weak.
Suggestions
Inline the minimal concrete steps for running a Figma Plugin API script (or bundle the upstream scripts/references into scripts/ and references/ and link them explicitly), instead of deferring everything to the GitHub URL.
Replace the non-portable `open https://...` snippet with an actually executable command (e.g. a git clone or download step with the target path in the skills directory).
Remove the verbatim duplication of the description and source URL between the frontmatter and the body to tighten the token budget further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and lean with clear sections, but the "What it does" section repeats the frontmatter description verbatim and the "Source" section duplicates the upstream URL already in the frontmatter, so a few tokens could be trimmed. | 4 / 5 |
Actionability | The only command is `open https://github.com/figma/skills`, which does not advance the advertised task, and "install the upstream bundle into your active agent's skills directory" gives no path, command, or concrete steps — high-level hints with the actual executable detail missing. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect upstream README → install the bundle → invoke by name or trigger), but the middle step — actually running Figma Plugin API scripts — is entirely deferred to an external repo, and no validation or verification checkpoints are described. | 2 / 5 |
Progressive Disclosure | The body is under 50 lines with no bundle files present and is organized into clear sections (What it does / Source / How to use); however, the single reference is an external URL rather than a well-signaled one-level-deep bundle file, leaving minor organization gaps. | 4 / 5 |
Total | 12 / 20 Passed |