Content
75%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 a well-organized, instruction-only skill: concrete directory conventions, named API annotations, a sequenced workflow, and a build-validated checklist, all reasonably concise. It falls short of top marks mainly on missing explicit error-recovery loops in the workflow, no worked before/after example, and no reference files for detail that is currently inlined.
Suggestions
Add an explicit feedback loop to the workflow (e.g., 'After each split, build; if it fails, fix in the newly created file before moving on') to raise workflow clarity.
Include a short before/after refactor example (a monolithic root view and its extracted subviews/files) to make the guidance copy-paste concrete.
Consider moving the file-splitting conventions (section 2b directory layout and the checklist) into a reference file to keep SKILL.md a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative — bullets like 'Break the app into meaningful scene roots' and a concrete file-ordering list add real guidance without explaining SwiftUI basics Claude already knows. A few bullets restate principles Claude could infer ('Keep files small and named after the primary type they contain') and some sections overlap (checklist vs. workflow), which keeps it just below the every-token-earns-its-place level of 5. | 4 / 5 |
Actionability | As an instruction-only skill, it gives concrete, specific guidance: exact directory conventions ('App/<AppName>App.swift', 'Views/SidebarView.swift', 'Models/*.swift', 'Services/*.swift'), named property wrappers (@SceneStorage, @AppStorage, @StateObject), and a clear file-shape ordering. It stops short of fully copy-paste-ready material (e.g., a before/after refactor example), so it sits at 4 rather than 5. | 4 / 5 |
Workflow Clarity | The Workflow section gives a clear 7-step sequence, and the checklist includes a validation checkpoint ('Build after each major split so compile errors stay local'). What is missing is an explicit feedback loop — what to do when the build fails and when to re-verify — which keeps it at 4 rather than the explicit validate-fix-retry pattern of 5. | 4 / 5 |
Progressive Disclosure | With no bundle files, the single SKILL.md is well-organized into Overview, Guidelines, Workflow, Checklist, Smells, and Notes, with one-level pointers to related skills ('use swiftui-patterns', 'use appkit-interop') rather than nested references. At ~105 lines with several distinct guideline areas, some detail (e.g., file-splitting conventions or a worked example) could live in reference files, so structure is good but not fully split — a 4. | 4 / 5 |
Total | 16 / 20 Passed |