Content
77%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-engineered operational skill: tight, command-dense, with an explicit preflight checklist, fallback ladder, and a verify-and-report feedback loop. Its main defect is bundle integrity — the two rules/ files carrying the full upload and body-region procedures are referenced but missing, which also leaves key paths not fully executable from the shipped skill.
Suggestions
Add the missing ./rules/upload-ladder.md and ./rules/body-region.md files to the bundle (or inline their essential procedures), since three of the four referenced paths in the body do not resolve.
Spell out one complete rung-1 invocation in the body (e.g., gh pr edit <n> --body-file <f> --attach <file>) so the primary upload path is copy-paste ready even without the ladder file.
Tighten the check-4 table cell by moving the light/dark-pair and contact-sheet edge cases into a short list or the upload-ladder reference, reducing the dense nested parenthetical.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational — preflight table, exact ffmpeg commands, rung table, region template, report format — with no explanation of concepts Claude already knows. It is not a 5 because a few rationale asides could be trimmed ('It is ~20× smaller...', 'An absent region is honest; a placeholder claims work that never happened') and the check-4 cell packs light/dark-pair and contact-sheet edge cases into one long nested parenthetical that could be tightened. | 4 / 5 |
Actionability | Commands are concrete and mostly copy-paste ready (three full ffmpeg invocations, the rung-1 gh flags, the curl endpoint, the region template with exact delimiters). It is not a 5 because full rung-1/rung-2 command syntax and the --to urls output procedure are delegated to rules/upload-ladder.md and rules/body-region.md, which are absent from the bundle, so the primary paths are not fully executable from what is shipped. | 4 / 5 |
Workflow Clarity | A clear four-step sequence (preflight → upload ladder → write region → verify/report) with a per-file failure checklist, explicit on-failure actions at every stage, a dry-run mode, and a post-write verification loop (re-read region, confirm one URL per file and no local path, remove and downgrade failures). It is not a 4 because validation checkpoints are explicit and complete, including the mandatory look-at-every-file check for a batch (1–50 file) operation. | 5 / 5 |
Progressive Disclosure | The design is right — lean overview delegating detail to well-labeled one-level-deep files ('Full procedure:', 'Full contract:', 'Rationale:') — but scored against the actual bundle, three of the four referenced paths (rules/upload-ladder.md, rules/body-region.md, and its § --to urls anchor) do not exist; only references/rationale.md resolves. It is not a 4 because majority-dangling references are more than minor organization gaps, leaving the delegated detail unavailable anywhere. | 3 / 5 |
Total | 16 / 20 Passed |