Content
86%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 an exemplary lean skill: executable commands with concrete output fields, an implicit but coherent discover-verify-act workflow with freshness validation before mutations, and clean sectioning with one well-signaled external link. The only improvements are showing the remaining described commands (the sqlite3 query, the maintainer commands) and making the discover→sync→verify sequence explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean, dense, and imperative throughout ("Check freshness and configured database paths with `gitcrawl doctor --json`"); it assumes Claude's competence and every token earns its place with no padding or explanations of known concepts. | 5 / 5 |
Actionability | Copy-paste-ready command blocks with concrete JSON field lists (threads, neighbors, search, clusters, gh pr view/checks/issue view) cover the common cases, but a few invocations are described rather than given, e.g. no full `sqlite3 -readonly` example and "maintainer commands" are referenced without being shown. | 4 / 5 |
Workflow Clarity | A clear ordered flow is present (archive discovery → `doctor --json` freshness check → bounded sync if stale → `gh` live verification before any maintainer decision or public mutation) with an explicit validation checkpoint, so the destructive-operation cap does not apply; it falls short of 5 only because the sequence is implicit in prose rather than an explicit step checklist with error-recovery loops. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no bundle files; sections (overview/commands, Current GitHub State, Archive Boundaries) are well-organized with a single clearly signaled one-level-deep external reference, which merits 5 under the simple-skill exception. | 5 / 5 |
Total | 18 / 20 Passed |