Content
61%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 well-structured and highly actionable, giving exact tool slugs and parameter specs, but it suffers from redundant sections and lacks validation checkpoints in its batch/destructive workflows. No bundle files exist, so progressive disclosure relies entirely on in-file sectioning.
Suggestions
Collapse the duplicate "Known Pitfalls" section into the per-workflow Pitfalls (or vice versa) and trim the "Common Patterns" block that restates node traversal already shown in Core Workflows.
Add explicit validation steps inside the rendering and comment workflows (e.g., after FIGMA_RENDER_IMAGES_OF_FILE_NODES, check for null node_id entries before calling FIGMA_DOWNLOAD_FIGMA_IMAGES).
Move the Quick Reference tool catalog into a separate references file (e.g., TOOL_REFERENCE.md) and link to it, keeping SKILL.md a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows, but it carries real redundancy: "Known Pitfalls" repeats the per-workflow pitfalls, and "Common Patterns" plus the Quick Reference table restate tool slugs and traversal steps already covered above. | 3 / 5 |
Actionability | Gives concrete tool slugs and exact parameter specs (e.g., "ids: Comma-separated node IDs (NOT an array)", scale 0.01-4.0, format options), which is mostly executable guidance; the gap is that it offers no literal code blocks and defers schemas to a runtime RUBE_SEARCH_TOOLS call. | 4 / 5 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with [Prerequisite]/[Required]/[Optional] markers, but batch/destructive operations (image rendering, adding comments) lack in-workflow validation checkpoints, so per the feedback-loop cap workflow clarity cannot exceed 3. | 3 / 5 |
Progressive Disclosure | Well-organized into Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference with no nested references, but at over 180 lines everything is inlined with no separate reference file for the bulky tool catalog, which is a minor organization gap short of 5. | 4 / 5 |
Total | 14 / 20 Passed |