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 exemplary instruction-only skill body: lean, fully sequenced with verification and a pre-conclusion audit, and concretely actionable via an explicit diff command, per-file attack-surface categories, and a specified findings format. The only improvement space is defining the severity scale and tightening a few verification hints.
Suggestions
Define the severity levels (what distinguishes Critical from High from Medium) so ratings are consistent across runs.
Make 'Search for existing tests covering the scenario' concrete, e.g., suggest grep for test names matching the changed function or module.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient throughout: no explanations of concepts Claude already knows, every phase and checklist item earns its place, and even edge guidance ("If you find nothing significant, say so - don't invent issues") is terse and load-bearing. Matches anchor 5. | 5 / 5 |
Actionability | Provides one copy-paste-ready command (`git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD`), a concrete 11-item security checklist, and a fully specified findings format. Minor gaps keep it below anchor 5: the Critical/High/Medium/Low severity levels are never defined and "Search for existing tests" gives no concrete command. | 4 / 5 |
Workflow Clarity | Five clearly sequenced phases with explicit validation checkpoints and feedback loops: Phase 4 verifies each potential issue ("Check if it's already handled elsewhere", "Search for existing tests"), and Phase 5 is a pre-conclusion audit requiring every checklist item to be accounted for and unverified areas to be listed. The skill is read-only ("Do not make changes"), so the destructive-operation cap does not apply. | 5 / 5 |
Progressive Disclosure | A single-file, ~70-line skill with well-organized sections and no bundle files; nothing here belongs in a separate reference file since the checklist and output format must load on every invocation. Consistent with the simple-skill exception, well-organized sections alone merit the top score. | 5 / 5 |
Total | 19 / 20 Passed |