Content
78%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 lean, well-structured instruction-only skill with a clear workflow and guardrails, but its guidance stays at the checklist level: it names what to verify (hardened runtime, nested signatures, entitlements) without a single concrete command to verify it with. Adding the minimal validation commands it already points to would lift actionability substantially.
Suggestions
Include the concrete validation commands the workflow references, e.g. `codesign --verify --deep --strict <app>`, `spctl -a -v <app>`, `stapler validate <app>`, and `xcrun notarytool history`.
Add an explicit validate→fix→retry checkpoint in the workflow (e.g. after inspecting signing prerequisites, re-verify before declaring readiness).
Show how to inspect bundle structure and entitlements concretely (e.g. `codesign -d --entitlements -` or checking Frameworks/ and Helpers/ layout) instead of the bare instruction "Validate app bundle structure".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 43-line body is lean across four tight sections with no explanation of concepts Claude already knows and no padding; the Quick Start line "Use this skill when the work is about shipping the app rather than merely running it locally" earns its place by scoping the skill. Every token pulls weight, matching the "lean and efficient; assumes Claude's competence" anchor. | 5 / 5 |
Actionability | The checklist items are concrete ("Hardened runtime", "Signing identity", "Nested code signatures", "Required entitlements") but no executable command appears anywhere — no `codesign --verify --deep`, `spctl -a -v`, `stapler validate`, or `xcrun notarytool` — even though the workflow says "Point to the minimum follow-up validation commands". The instruction-only exemption from the code requirement doesn't fully apply because the how-to-execute detail is missing, fitting "some concrete guidance but incomplete; missing key details" rather than the mostly-executable anchor above. | 3 / 5 |
Workflow Clarity | The four-step sequence (confirm goal → inspect artifact → inspect signing/runtime prerequisites → explain readiness) is clearly ordered and domain-appropriate, with validation present but implicit ("Validate app bundle structure" and the output expectation of "the next validation or repair step"). This matches "clear sequence with most checkpoints present; minor validation gaps"; it lacks the explicit validate→fix→retry loop of the top anchor, though no destructive/batch cap applies. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ exist), and nothing inlined belongs in a separate file; well-organized sections with clear headers are sufficient for a skill of this size per the simple-skill guidance. | 5 / 5 |
Total | 17 / 20 Passed |