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 skill: opinionated operating rules, three concrete workflows with checklist validation gates, a precise topic-to-skill/file routing table, and a hard-rule correctness checklist. Only minor stylistic trimming is needed in the Operating Rules section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is directive and teaches nothing Claude already knows, but a few stylistic passages ('apps should feel current-generation — fluid, design-forward, alive. Sweat the tiny details.') could be trimmed. | 4 / 5 |
Actionability | Fully concrete for an instruction-only skill: exact skill names (e.g. 'guide-swiftui-performance-audit', 'swiftui-specialist'), a Topic Router table naming specific reference files, and copy-paste-ready hard rules ('.animation(_:value:) always includes the value: parameter'). | 5 / 5 |
Workflow Clarity | Three task workflows (Review, Improve, Build) are clearly sequenced, each with an explicit validation checkpoint ('Run the correctness checklist first' / 'before finishing'), backed by a dedicated hard-rule checklist. Not a destructive/batch skill, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | With no bundle files to split, the body is exactly what a router SKILL.md should be: well-organized sections, a one-level-deep Topic Router table pointing to named skills and files, and a clearly signaled Related Skills index. | 5 / 5 |
Total | 19 / 20 Passed |