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.
The body is an exemplary lean index: a single, clearly signaled reference file (verified to exist with sections matching the table) plus a topic-to-section navigation table, with no padding or redundant explanation. The only weakness is that all executable content lives one level deep, so the body itself offers no inline commands for even the most common questions.
Suggestions
Inline one or two copy-paste commands for the most frequent questions (e.g., `git switch -c <branch>` / `git restore <file>`) so trivial lookups can be answered without loading the 378-line reference.
Mark which navigation-table topics involve destructive or risky operations (e.g., `git clean`, force-push, branch deletion) so the index itself signals where caution is needed before jumping to the section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~20 lines with zero padding: 'Full reference: [./references/git-workflows.md] — read it when answering any question this skill covers' plus a compact topic-to-section table. It explains nothing Claude already knows and every token earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor. | 5 / 5 |
Actionability | The concrete guidance is the explicit directive to read './references/git-workflows.md' and a navigation table mapping topics to exact sections (§1–§10), which is executable routing. It falls short of anchor 5 ('copy-paste ready code or commands; specific examples cover the common cases') because the body contains no inline commands or examples at all — all command-level detail is delegated to the reference, a deliberate but real gap. | 4 / 5 |
Workflow Clarity | This is a single-purpose routing skill under 50 lines; the single action — 'read it when answering any question this skill covers' — is unambiguous, satisfying the simple-skill exception. No destructive or batch operations appear in the body, so the workflow-clarity cap does not apply. | 5 / 5 |
Progressive Disclosure | The body is a clear overview with one well-signaled, one-level-deep reference ('Full reference: [./references/git-workflows.md]'); the referenced file exists and its §1–§10 sections match the navigation table exactly. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; easy navigation'). | 5 / 5 |
Total | 19 / 20 Passed |