Content
92%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.
An exemplary router-style SKILL.md: unambiguous direction selection with an explicit ambiguity checkpoint, dense non-obvious shared context (tool args, URL parsing, SF Symbols, semantic colors, pattern recognition), and verified one-level-deep references. The only trim opportunity is the redundant References table duplicating links already in the direction table.
Suggestions
Drop the trailing 'References' table (or fold its 'When to load' wording into the 'Pick the direction' table) — both tables list the same two files, and removing the duplication tightens the body further.
If keeping both tables, merge them into one table with Direction, Trigger, and Reference columns to eliminate the repeated links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean router content — no concept explanations Claude already knows, and the six shared-context points are dense non-obvious operational knowledge (tool args, URL parsing, SF Symbol handling). Not a 5 only because the bottom "References" table ("references/design-to-code.md... Translating a Figma design / frame into SwiftUI") duplicates the two links already given in the "Pick the direction" table — a minor redundancy that could be trimmed. | 4 / 5 |
Actionability | Fully concrete, executable guidance: exact tool arguments ("Pass `clientLanguages: "swift"` and `clientFrameworks: "swiftui""), a precise URL-parsing recipe ("figma.com/design/:fileKey/:fileName?node-id=:nodeId → use fileKey, replace - with : in nodeId"), a specific API call ("call `figma.util.getSfSymbolCharacter(name)`"), and exact color token mappings ("map to `Color(.systemBackground)`, `Color.secondary`, `Color(.separator)`"). Specific guidance covers the common cases for a router file. | 5 / 5 |
Workflow Clarity | The routing workflow is unambiguous: a decision table for direction, an explicit disambiguation checkpoint ("If the request is ambiguous... ask the user which direction before loading a reference"), and explicit loading rules for companion skills ("Always load figma-use before any use_figma call"). No destructive or batch operations, so no validation checkpoint is required for this single-purpose router. | 5 / 5 |
Progressive Disclosure | Clear overview with well-signaled one-level-deep references: the direction table maps each case to a specific doc with 'When to load' conditions, and both referenced files (references/design-to-code.md and references/code-to-design.md) exist in the bundle as real one-level-deep targets. Content is appropriately split — deep translation detail lives in the references, not inlined here. | 5 / 5 |
Total | 19 / 20 Passed |