Content
36%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 a well-grouped but padded catalog of 11 GitHub coordination modes, dominated by marketing-style attribute labels rather than executable procedures, and it opens with a redundant embedded YAML metadata block. It names real gh CLI subcommands and gives example invocations, so it is partially actionable, but contains no sequenced workflows or validation for the destructive batch operations it advertises. With no bundle files, everything — including detail that belongs in per-mode references — is inlined in one file.
Suggestions
Replace buzzword attributes ('Intelligent', 'Smart', 'Advanced', 'Proactive') with concrete procedures or actual command sequences for each mode.
Add validation checkpoints before destructive or batch operations — e.g., run 'gh pr checks' and confirm CI status before 'gh pr merge', or verify issue/PR creation output when creating in batch.
Keep SKILL.md as a concise overview with links to per-mode reference files (e.g., references/pr-manager.md, references/release-manager.md), and remove the duplicated YAML metadata block from the top of the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body opens with a redundant second YAML metadata block (name, description, capabilities, hooks) that duplicates the section headings, and the 11 mode sections are padded with buzzword attributes like 'Conflict Resolution: Intelligent', 'Label Management: Smart', and 'Batch Optimized: Yes' that carry no instruction. This is 'several unnecessary... padded sections' (anchor 2) rather than anchor 3's incidental over-explanation, though it never explains basics Claude already knows (anchor 1). | 2 / 5 |
Actionability | Each mode lists real gh subcommands ('gh pr create, gh pr view, gh pr review, gh pr merge') and the usage examples include concrete task strings, but the batch-operations example is pseudocode (Bash("gh issue create --title 'Feature A' --body '...'") with placeholder bodies) and no complete, copy-paste executable workflow exists. This matches anchor 3 ('pseudocode instead of executable code'), not 4, since the gaps are more than minor. | 3 / 5 |
Workflow Clarity | The content is a mode catalog with no process steps, sequencing, or validation checkpoints, while covering destructive and batch operations (batch PR creation, 'gh pr merge', 'All GitHub modes support batch operations') with zero verification guidance — the batch-operation cap applies. It sits at anchor 2 ('steps poorly defined; validation absent') rather than 1 only because the usage invocations imply a rough pick-a-mode-then-invoke sequence. | 2 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent) and nothing is split out: the full 145-line mode catalog is inlined in SKILL.md with no references signaling where details live. Section headers are consistent and well-grouped (more than anchor 2's minimal structure), but per-mode detail that belongs in separate reference files is inline, matching anchor 3. | 3 / 5 |
Total | 10 / 20 Passed |