Content
72%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 concise, well-sectioned body with genuinely executable dispatch commands and honest limitation notes. Its weaknesses are the missing verification/observation steps in the install-configure-dispatch workflow and a broken reference to templates/mac-run.yml, which forces the reader to trust prose descriptions of the workflow instead of reading it.
Suggestions
Add post-dispatch verification commands, e.g. `gh run watch` / `gh run list --workflow mac-run.yml` and `gh run download` for the `mac-run` artifact, to close the validation-loop gap.
Ensure templates/mac-run.yml ships in the bundle (it is referenced by both the body and scripts/install.sh but is absent), or inline the key workflow snippet so the payload is inspectable.
Provide a concrete example XCODE_DESTINATION value (a specific simulator identifier) alongside the 'Replace the example' guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: terse tables for env values and dispatch steps, copy-paste `gh` commands, and honest scope/failure notes ("does not archive, export or deploy an app") with zero padding or explanation of concepts Claude already knows. It matches the 'every token earns its place' anchor; the only near-noise is the small kendex instruction comment block, which is structural rather than over-explanation. | 5 / 5 |
Actionability | Guidance is mostly executable: exact `gh workflow run mac-run.yml -f step=...` commands for all three operations, a table of env values to edit, and a named installer script (scripts/install.sh, which exists). It falls short of the 5 anchor because the body's central reference, templates/mac-run.yml, is not present in the bundle, and configuration advice is prose ('Replace the example with a simulator supported by the selected Xcode') without a concrete example destination. | 4 / 5 |
Workflow Clarity | The sequence (install → configure env → commit to default branch → dispatch → retrieve artifact) is present and coherent via section ordering, but verification checkpoints are missing or implicit: no commands to confirm dispatch (e.g. `gh run watch/list`) or download the `mac-run` artifact, and no pre-dispatch check that XCODE_SCHEME/XCODE_DESTINATION are valid. This matches the 'sequence present but checkpoints missing' anchor; it is above the 2 anchor because steps are well defined, but below 4, which requires most checkpoints present. | 3 / 5 |
Progressive Disclosure | Sections are well organized and references are clearly signaled (a markdown link to templates/mac-run.yml, and the installer declared in frontmatter pointing to the real scripts/install.sh). However, scoring against the actual bundle structure, the referenced templates/mac-run.yml does not exist in the bundle, so navigation to the skill's core payload is broken — the workflow's behavior must be inferred from prose. This places it between 'references present but not clearly signaled' (3) and 'minor organization gaps' (4), landing at 3 due to the unresolvable reference. | 3 / 5 |
Total | 15 / 20 Passed |