Content
67%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-structured, highly actionable macOS SwiftUI patterns skill with real one-level reference files and concrete code. Its main weaknesses are redundancy — the sidebar-density and background rules are each stated three times — and inline pattern sections that overlap with the bundle's reference files, which inflates token cost without adding guidance.
Suggestions
Consolidate the sidebar-density guidance: state the rule once (in General Rules or the Recommended Sidebar Row Pattern) and let Anti-Patterns reference it rather than restate it at length.
Merge the Split-View Background Pattern's prose into the split-inspectors.md reference, keeping only a one-line pointer plus the minimal code example in SKILL.md.
Replace the generic "Validate the flow with a build" step with an explicit command (e.g. the referenced script/build_and_run.sh) and a fix-and-retry instruction to make the workflow checkpoint executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, non-obvious desktop guidance (e.g. "Treat Window(...) as a better fit for auxiliary/on-demand singleton windows"), but several rules are restated two to three times across sections: the sidebar row density rule appears in General Rules ("at most one leading icon, one strong title line"), again in the Recommended Sidebar Row Pattern ("one icon maximum and one or two text lines maximum"), and a third time in Anti-Patterns ("three or more text lines"). The opaque-background rule is similarly repeated in General Rules, the Split-View Background Pattern, and Anti-Patterns. This repetition could be consolidated without losing clarity. | 3 / 5 |
Actionability | Guidance is mostly executable: two complete compile-ready Swift examples (sidebar row and split-view background, each with a positive and negative variant), concrete commands ("git rev-parse --is-inside-work-tree"), and specific thresholds ("Cap visible menu item text at 30 characters", "roughly under 50 lines"). Minor gap: it delegates to the appkit-interop and build-run-debug skills and their reference files, which are not part of this bundle and cannot be verified here, leaving a small unexecutable seam. | 4 / 5 |
Workflow Clarity | The Quick Start tracks, Pre-Edit Checklist, and the 7-step "Workflow For A New macOS Scene Or View" give a clear sequence with most checkpoints present, including a validation step ("Validate the flow with a build and a quick usability pass"). It falls short of a 5 because validation is a one-line mention rather than an explicit validate-fix-retry loop with commands, and the destructive-operation guard ("Do not initialize a nested repo inside an existing parent checkout") has no accompanying verification step. | 4 / 5 |
Progressive Disclosure | Structure is good: the Cross-Cutting References section signals all six reference files (all of which exist in references/ and are one level deep) with one-line descriptions, and components-index.md is designated as the entry point. It is not a 5 because the two large Recommended Pattern sections (sidebar row, split-view background) inline substantial pattern content that overlaps with split-inspectors.md territory and duplicates guidance already stated in General Rules, so the SKILL.md is longer than a pure overview needs to be. | 4 / 5 |
Total | 15 / 20 Passed |