Content
71%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.
A well-organized, lean body with executable Swift patterns and a sensible workflow, undermined by one material defect: it positions `references/components-index.md` and `references/app-scaffolding-wiring.md` as core entry points, but the bundle contains no reference files at all, so the main component guidance the skill promises cannot be loaded. Meta sections about maintaining references add tokens without user-facing value.
Suggestions
Ship the referenced files (at minimum `references/components-index.md` and `references/app-scaffolding-wiring.md`) or remove/inline those references — currently the skill's central component guidance is unreachable.
Trim the maintainer-facing sections ("Component references" expectations and "Adding a new component reference") or move them into a CONTRIBUTING-style reference file; they spend tokens on skill authorship rather than skill use.
Strengthen the workflow's validation step into a feedback loop: what to check when the build fails and when to re-run it after updating usage callsites.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes competence — it never explains what SwiftUI is, gives a concrete `rg "TabView\("` command, and keeps rules as terse bullets. It sits at 4 rather than 5 because of meta-content that earns few tokens ("Component references" describes what reference files should contain, and "Adding a new component reference" is maintainer guidance rather than usage guidance) and some bullet redundancy with the code examples. | 4 / 5 |
Actionability | Guidance is mostly executable: two complete Swift snippets (item-driven sheet, sheet-owns-its-actions with `dismiss()` and `@Environment`), a concrete search command, and named file paths. Not a 5 because several directives stay high-level ("Sketch the view hierarchy", "Follow the project's formatter and style guide", "explicit loading/error states" without an example) and the core component guidance is deferred to files that do not exist. | 4 / 5 |
Workflow Clarity | "Workflow for a new SwiftUI view" is a clear 6-step sequence ending in a validation checkpoint ("Validate with a build and update usage callsites if needed"), and the Quick start tracks are sequenced. Below 5 because validation is a single mention with no error-recovery loop (what to do when the build or accessibility check fails), and step ordering is present but checkpoints are implicit elsewhere. | 4 / 5 |
Progressive Disclosure | In-body structure is good — clear sections, clearly signaled one-level references ("Use `references/components-index.md` as the entry point", "Start with `references/app-scaffolding-wiring.md`") — but no `references/`, `scripts/`, or `assets/` directories exist in the bundle, so both entry-point references are dangling. The promised component detail is unreachable, leaving the disclosure chain broken; this fits the 'structure present but organization compromised' middle anchor rather than the good-structure anchor at 4. | 3 / 5 |
Total | 15 / 20 Passed |