Content
86%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 an exemplary overview skill: lean, high-signal, packed with FigJam-specific gotchas and exact error messages Claude cannot infer, with a clean one-level reference architecture. The only real weaknesses are minor — key recipes (text mutation, upload_assets payload) are delegated to the companion skill's references, and batch-modify workflows lack an inline validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious facts Claude cannot know — exact error strings ("TypeError: figma.createPage no such property", "Cannot write to node with unloaded font"), tool failure modes ("get_metadata does NOT work on FigJam files"), and defaults ("sticky → Inter Medium"). Nearly every token earns its place, fitting anchor 5 rather than anchor 4. | 5 / 5 |
Actionability | Concrete, executable guidance dominates: a copy-paste-ready "ToolSearch query=\"select:use_figma,get_figjam,…\"" snippet, specific instructions ("load from node.text.fontName rather than hardcoding"), and exact tool behaviors for upload_assets. Minor gaps keep it below anchor 5 — the canonical text-mutation recipe and the upload_assets request/response shape are delegated to the figma-use references rather than shown. | 4 / 5 |
Workflow Clarity | A coherent sequence is laid out — inspect with get_figjam upfront to get IDs, batch-load schemas and references, then mutate following load font → await → mutate → return IDs — with explicit error-recovery guidance ("If you forgot to return an ID… call get_figjam"). It stops short of anchor 5 because there is no explicit validation checkpoint around batch/destructive mutations (batch-modify is delegated to a reference). | 4 / 5 |
Progressive Disclosure | The Reference Docs section lists all 13 bundle files (all verified to exist) with one-line scope descriptions, plan-board-content is clearly positioned as the delegating entry point, and cross-links to ../figma-use stay one level deep with no nested reference chains. This matches anchor 5: clear overview with well-signaled one-level-deep references and easy navigation. | 5 / 5 |
Total | 18 / 20 Passed |