Content
43%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 body is a token-efficient index that would be a reasonable overview if its references resolved, but it contains no actionable or sequenced guidance of its own and every referenced file is missing, so the skill as bundled delivers almost nothing beyond its description.
Suggestions
Fix the reference paths so they point to files that actually exist (create reference/issue-to-pr.md, reference/committing.md, and reference/prek.md, or correct the directory name to references/).
Add a minimal quick-start sequence inline (e.g. pick up the issue → create a branch → commit → run `prek run --all-files` → fix failures → open the PR) so the skill works even before the references are opened.
Include at least one concrete command or example per section (such as the actual prek invocation and commit-message format) to lift actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is extremely lean with no concept over-explanation; the only trimmable token is the intro sentence "This skill covers the end-to-end PR flow, including commits and prek usage", which repeats the description, placing it between the efficient and every-token-earns-its-place anchors. | 4 / 5 |
Actionability | The body offers only a "When to use" bullet list and three links — no commands, steps, or examples — and the referenced files (reference/issue-to-pr.md, reference/committing.md, reference/prek.md) do not exist in the bundle, so no executable guidance is reachable. It sits above the entirely-vague anchor because the bullets and labeled references are real, if thin, pointers. | 2 / 5 |
Workflow Clarity | The domain is inherently multi-step (issue → branch → commit → check → PR, plus fixing hook failures) but the body sequences nothing — no numbered steps and no validation checkpoint for prek failures. The "When to use" bullets imply a rough order, which fits between the steps-missing and rough-sequence anchors. | 2 / 5 |
Progressive Disclosure | The pattern is correct — a lean overview with clearly signaled, one-level-deep references — but all three links point into a reference/ directory that is absent from the bundle, breaking the navigation chain and making it more than the "minor organization gaps" of the next anchor up. | 3 / 5 |
Total | 11 / 20 Passed |