Content
63%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 delivers strong repo-specific actionability — exact patterns, commands, and label mappings with genuine validation gates in the workflow. Its weaknesses are repetition of authorization boilerplate, a large inline PR-template schematic that belongs in a reference file, and reliance on an external 'canonical issue-creation workflow contract' that is never defined in the bundle.
Suggestions
Move the PR body schematic and the commit-convention tables into reference files (e.g. references/pr-template.md, references/commit-conventions.md) and keep one-line, clearly signaled pointers in SKILL.md.
Deduplicate the authorization/label-mutation gating language: state the 'canonical issue-creation workflow contract' requirements once and reference that section, instead of repeating the full clause in Critical Rules, the Workflow, and the Automated Checks table.
Remove the verbatim duplication between the Test Plan checkboxes and the Contributor Checklist checkboxes in the PR schematic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly repo-specific and non-padded (exact regexes, command blocks, label mappings), but the authorization boilerplate ('current direct human instruction binding the exact target/action', 'canonical issue-creation workflow contract') is repeated nearly verbatim in Critical Rules, the taxonomy paragraph, Workflow step 4, and the Automated Checks table, and the checklist test items appear twice within the PR schematic. It fits anchor 3 ('mostly efficient but could be tightened') better than 2, since there is no explanation of concepts Claude already knows. | 3 / 5 |
Actionability | Concrete, executable material dominates: exact branch-name and commit-message regexes, runnable commands (`gh issue view`, `go test ./...`, `gh pr checks`), type-to-label tables, and a full PR body schematic. Not 5 because the central action (creating the PR) deliberately has no command ('this skill provides no executable creation command') and the repeatedly-invoked 'canonical issue-creation workflow contract' is never defined in this file, leaving those gates non-executable. | 4 / 5 |
Workflow Clarity | The Workflow section gives a clear 5-step sequence with real validation checkpoints: verify `status:approved` before proceeding, run local checks before drafting, 'Mark checkboxes only after observed readback', and 'Unknown requiredness is not merge-ready'. Not 5 because error-recovery loops are thin (only 'Fix failing tests before pushing' in the table) and the checkpoints for label mutation defer to an undefined external contract. | 4 / 5 |
Progressive Disclosure | The single-file bundle has no reference files, while ~70 lines of PR-template schematic plus the branch-naming and commit-convention tables are exactly the kind of lookup material that belongs in separate one-level-deep references. Section headers are clear, so navigation works, but this matches anchor 3 ('content that should be separate is inline') rather than 4's 'most content is appropriately placed'. | 3 / 5 |
Total | 14 / 20 Passed |