Content
85%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 exceptionally actionable and well-sequenced workflow skill: executable commands, explicit validation gates before any destructive action, protection rules, fallbacks, and thorough edge-case handling. Its weaknesses are structural: it is monolithic with no progressive disclosure, references a templates/issue-comment.md file that is missing from the bundle, and contains minor duplicated notes that could be trimmed.
Suggestions
Create the referenced templates/issue-comment.md file (or remove the Phase 3 reference to it) — as written, the skill points to a bundle file that does not exist.
Move the bulky, rarely-needed-per-run material — the output triage-table templates, the full Jaccard algorithm spec, and the /pr-triage comparison table — into a references/ file linked one level deep, keeping SKILL.md as a leaner overview of the 3 phases.
De-duplicate the repeated guidance (the 'comments field is count-only' note appears in both Phase 1 and Notes; the English-only comment rule appears in both Language and Phase 3) to reclaim tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational — exact gh commands, decision tables, and a self-contained Jaccard algorithm with no explanations of concepts Claude already knows. Not 5 due to minor duplication and padding: the Notes repeat the Phase 1 "comments field returns count, not content" note verbatim, Phase 3 re-states the English-language rule from the Language section, and the closing /pr-triage comparison table largely restates the decision rule; not 3 because these are trims, not conceptual over-explanation. | 4 / 5 |
Actionability | Quotes: "gh issue list --state open --limit 100 --json number,title,author,...", "Patterns: `fixes #N`, `closes #N`, `resolves #N`...", the 4-step Jaccard algorithm with stop-word list and thresholds, exact output table templates, AskUserQuestion option blocks, and copy-paste execution heredocs ("gh issue comment {num} --body-file - <<'TRIAGE_EOF'"). Fully executable guidance with edge cases and fallbacks covering the common cases. | 5 / 5 |
Workflow Clarity | The 3 phases are clearly sequenced with preconditions ("git rev-parse --is-inside-work-tree; gh auth status"), and the destructive/batch operations have explicit validation: "Display ALL drafted actions" before an AskUserQuestion gate, "Never execute any action without explicit user validation in chat", plus protection rules, fallbacks (collaborators 403 → merged-PR authors; parallel → sequential), and an edge-case table with recovery behavior. The batch-operation cap at 3 does not apply because validation checkpoints are present. | 5 / 5 |
Progressive Disclosure | The skill is a single ~450-line monolithic SKILL.md with no bundle files, yet Phase 3 references "the template `templates/issue-comment.md`" — a file that does not exist in the bundle (dangling reference). Internal headers and tables give it clear structure, so anchor 2's "minimal structure" does not fit, but content that could live one level deep (output table templates, the Jaccard algorithm spec, the /pr-triage comparison) is fully inlined and the one reference made is broken, so it does not reach anchor 4's "most content appropriately placed; references mostly clear". | 3 / 5 |
Total | 17 / 20 Passed |