Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced skill body with concrete API calls, complete templates, and a real validation step, supported by appropriately split one-level references. Its main weakness is repetition of the INSTANCE_SWAP/SLOT guidance and snippet patterns across several sections, which inflates length.
Suggestions
Consolidate the INSTANCE_SWAP vs SLOT guidance (currently repeated in Step 3, the Step 5 mapping table, the descendant-layers table, and Rules #4/#5/#7) into one authoritative section and cross-reference it.
Dedupe the icon executeTemplate snippet pattern, which appears nearly verbatim in the INSTANCE_SWAP, nested-configurable-instances, nested-component-example, and Rules #7 sections.
Consider moving the Inline Quick Reference signature tables fully into references/api.md and keeping only a pointer, since they overlap with the API reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is genuinely non-obvious Figma Code Connect API detail that earns its place, but the INSTANCE_SWAP/SLOT distinction and the icon/executeTemplate snippet pattern are repeated across Step 3, the Step 5 tables, the descendant-layers table, and Rules and Pitfalls #4/#5/#7, so it could be tightened. | 2 / 3 |
Actionability | Provides exact MCP tool calls with named parameters, complete copy-paste template structures, concrete method signatures, and a full end-to-end worked example — fully executable rather than pseudocode. | 3 / 3 |
Workflow Clarity | A clear six-step sequence (parse URL → discover → fetch properties → identify component → create template → validate) with an explicit Step 6 validation checklist, error-response branches in Step 2 that stop the workflow, and a user-confirmation checkpoint in Step 4. | 3 / 3 |
Progressive Disclosure | Core workflow lives inline while advanced nesting and the full API are deferred to real one-level-deep references (references/api.md, references/advanced-patterns.md), clearly signaled in an Additional Reference section and at point of need. | 3 / 3 |
Total | 11 / 12 Passed |