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 FigJam companion skill: it leads with critical FigJam-vs-Design gotchas (no createPage, get_metadata unsupported), batches tool-schema and reference loading, and delegates per-node-type detail to 13 real, well-described reference files. The only notable gap is that no single end-to-end board-creation sequence or minimal inline code example anchors the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense with non-obvious, tool-specific facts (exact error strings, get_metadata incompatibility, sublayer font defaults, upload_assets semantics, batch-read patterns). Nothing explains concepts Claude already knows, so it matches 'Lean and efficient; every token earns its place'; the one-line rationale for ToolSearch batching is minor and useful, not a 4-level padding. | 5 / 5 |
Actionability | Guidance is largely executable: a copy-paste ToolSearch query string, exact error messages to avoid triggering, the canonical font-load → await → mutate → return recipe, and concrete upload_assets instructions. It falls short of 5 because the core creation workflows (stickies, sections, tables) are delegated to references with no inline minimal example, leaving minor gaps for the most common first action. | 4 / 5 |
Workflow Clarity | The inspect-then-mutate sequence is explicit ('Use get_figjam upfront before writing any use_figma code') and includes a genuine error-recovery loop (call get_figjam if you forgot to return an ID, rather than re-running an inspection script), plus exact error messages guiding fixes. It is not a 5 because the full board-creation workflow (plan content → create nodes → position) is never sequenced in one place, only implied across sections. | 4 / 5 |
Progressive Disclosure | The body is a clear overview with a well-annotated reference list — all 13 referenced files exist in references/ — each with a one-line description of when to read it, and cross-links to the companion figma-use skill are one level deep and clearly signaled. This matches the 'clear overview with well-signaled one-level-deep references' anchor. | 5 / 5 |
Total | 18 / 20 Passed |