Content
96%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 exemplary lean skill body: concrete commands in every common input form, an explicit throttled-refresh strategy, a guarded fast-forward, and guidance to keep edits out of the shared cache. The one defect is bundle integrity — the body's only external reference, `checkout.sh`, has no corresponding file in `scripts/`, so the documented commands cannot run as bundled.
Suggestions
Ship `checkout.sh` in `scripts/` (or correct the invocation path) — the body's entire command surface depends on it, but no bundle file exists.
Add a brief note on failure handling (network error, non-fast-forward divergence, repo moved) so the caller knows whether to fall back to the stale cached checkout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: no explanation of git or caching concepts, and every section (cache location, command, update strategy, workflow, edits, notes) delivers non-obvious operational detail. "The goal is to keep a reusable local checkout that is: stable... up to date... efficient" conveys design intent in three bullets rather than paragraphs. Every token earns its place. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready commands: `bash checkout.sh <repo> --path-only` with three concrete input forms (owner/repo, host/owner/repo, full URL) and `--force-update` for immediate refresh. The script's five behaviors (parse, clone, reuse, fetch when stale at 300s, fast-forward when clean) are enumerated so the operator knows exactly what each call does. | 5 / 5 |
Workflow Clarity | A simple, single-purpose skill with an unambiguous workflow: resolve the path via `checkout.sh --path-only`, use that path for searching/reading/analysis, and re-call the script on later references. The risky operation (fast-forward merge) is explicitly guarded — "if the checkout is clean and has an upstream" — and edits are routed away from the shared cache via a worktree/copy, satisfying the simple-skill exception. | 5 / 5 |
Progressive Disclosure | The single SKILL.md is well organized into clearly labeled sections with one one-level-deep reference (`checkout.sh`), which is appropriate for a skill this size. However, no `scripts/` directory exists in the bundle, so the referenced script is not actually present — the reference dangles. This sits between anchor 5 (clean one-level structure, no issues) and anchor 4 (good structure with a minor gap). | 4 / 5 |
Total | 19 / 20 Passed |