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.
The skill body is a well-organized overview with excellent progressive disclosure and largely actionable, opinionated macOS-specific guidance backed by a real reference bundle. Its main weaknesses are notable duplication of the scaffolding and visual-style rules across sections, and the absence of any inline code examples or error-recovery loops in the workflow.
Suggestions
Merge the scaffold/file-structure guidance from 'New App Scaffolding', 'New App File Structure', and 'Pre-Edit Checklist' into one section — the checklist currently restates the same three bullets, costing tokens without new information.
De-duplicate the sidebar row and background-color rules, which appear in both 'General Rules To Follow' and 'Anti-Patterns'; state each once and reference it.
Add an inline minimal code snippet for the highest-frequency patterns (e.g. a WindowGroup + MenuBarExtra scene) and a build-failure recovery step in the workflow to close the actionability and workflow-clarity gaps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The scaffold and file-structure guidance is repeated across "New App Scaffolding", "New App File Structure", and the "Pre-Edit Checklist" (which restates the same bullets), and the sidebar/background-color rules appear in both General Rules and Anti-Patterns. The content is largely non-obvious opinionated guidance rather than padded concept explanation, so it sits above anchor 2 but clearly could be tightened. | 3 / 5 |
Actionability | Concrete guidance abounds: a state-ownership table mapping scenarios to specific wrappers, exact API calls like `NSApp.setActivationPolicy(.regular)`, a concrete command (`git rev-parse --is-inside-work-tree`), and an explicit file/folder layout. It falls short of anchor 5 because the body contains no copy-paste code examples — those are deferred to the reference files. | 4 / 5 |
Workflow Clarity | "Workflow For A New macOS Scene Or View" is a clear 7-step sequence ending in explicit validation ("Validate the flow with a build and a quick usability pass"), matching anchor 4's 'most checkpoints present'. It is not anchor 5 because there is no error-recovery loop (build fails → fix → re-validate), only a terminal validation step. | 4 / 5 |
Progressive Disclosure | The body stays at overview level with a "Cross-Cutting References" section that clearly annotates all six reference files (all verified present, each containing code examples), one level deep, plus an explicit entry point (`components-index.md`). This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |