Content
92%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.
An exceptionally tight, executable body with a validated multi-step workflow — preflight checks, a fallback upload ladder, an idempotent owned region, and a verify-and-report step with error recovery. Its one real defect is that the bundle is incomplete: Steps 2 and 3 point to `rules/upload-ladder.md` and `rules/body-region.md`, which are missing from the skill directory.
Suggestions
Create the missing `rules/upload-ladder.md` file referenced in Step 2 — the 'Full procedure' link for the entire upload mechanism is currently a dead path, so a following agent has no procedure to load when the inline rung table is insufficient.
Create the missing `rules/body-region.md` file referenced in Step 3, covering the region contract (merge-by-filename semantics, marker format) that the body only summarizes.
If the skill is intended to stay a single-file-plus-rationale bundle, inline the essential content of both missing files into Steps 2–3 and remove the dead links instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational — argument tables, a preflight checklist, exact commands — with no explanations of concepts Claude already knows; even its rationale sentences carry non-obvious domain knowledge ("~20× smaller, and its bare URL renders as a player; a GIF renders only as an image embed"). It matches anchor 5 ('Lean and efficient; every token earns its place'); there is nothing that qualifies as the anchor-4 'minor instances of over-explanation'. | 5 / 5 |
Actionability | Guidance is fully executable and copy-paste ready: exact `gh pr edit --help` probe, a named curl endpoint ("POST to https://uploads.github.com/user-attachments/assets"), complete ffmpeg invocations with flags ("-movflags +faststart -vf 'scale=1280:-2,format=yuv420p' -c:v libx264 -crf 28 -an"), frame-extraction commands, and an exact report format. It matches anchor 5 ('Fully executable; copy-paste ready code or commands; specific examples cover the common cases'). | 5 / 5 |
Workflow Clarity | A clear four-step sequence (Preflight → Upload ladder → Write owned region → Verify and report) with explicit validation at every phase: per-check failure handling with named statuses ("skipped (missing)", "skipped (too large)"), a fallback ladder with retry ("Re-encode a video once"), and a mandatory verify step with an error-recovery loop ("Remove any local path you find and list its file as 'not attached'"). This matches anchor 5 ('explicit validation steps; feedback loops for error recovery; checklists'), and the batch-operation cap does not apply since validation is present. | 5 / 5 |
Progressive Disclosure | The body itself is well-structured with clearly signaled one-level references ([`rules/upload-ladder.md`](./rules/upload-ladder.md) "Full procedure", [`rules/body-region.md`](./rules/body-region.md) "Full contract", [`references/rationale.md`](./references/rationale.md) "Rationale"), but scored against the actual bundle, two of the three referenced files do not exist — there is no `rules/` directory, so the links carrying the core upload procedure and region contract are dead. The structure is far better than anchor 2 ('minimal structure; references buried'), but broken references for the most load-bearing details exceed anchor 4's 'minor organization gaps', leaving anchor 3 ('references present but' fundamentally not navigable to the promised detail). | 3 / 5 |
Total | 18 / 20 Passed |