Content
88%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 unusually dense, high-discipline skill: every line is a directive, commands are executable, and the workflow is gated by approval and verification checkpoints with error-recovery fallbacks. The only structural criticism is that a skill of this length keeps all detail inline rather than splitting secondary procedures (screenshots, writing rules) into reference files.
Suggestions
Move version-sensitive details like the `gh` (2.99.0+) upload behavior into a short compatibility note or reference file so the main flow stays version-stable.
Consider splitting the Screenshots decision tree and the per-section writing rules into a one-level-deep reference file, keeping SKILL.md as the overview of the gather → confirm → create → describe → cut flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and telegraphic ("Three dots — two compares against the base's current tip and misdescribes the PR") and never re-teaches concepts Claude already knows. It misses a 5 because time-sensitive version information ("`gh` (2.99.0+) uploads it and rewrites the reference") sits in the main flow instead of a versioned or compatibility note, which the guidelines say should penalize conciseness. | 4 / 5 |
Actionability | Guidance is fully executable: a copy-paste context-gathering batch with exact gh JSON fields, a concrete merge-base counting rule for base selection, exact gh pr create/edit flags with --body-file rationale, and placeholders only where user-specific values are required — matching the 'copy-paste ready, covers common cases' anchor. | 5 / 5 |
Workflow Clarity | The sequence (gather context → confirm before acting → create/update → description format → cut before showing) is explicit and gated by validation and feedback loops: check git status after staging and stop on anything unexpected, wait-for-approval and revise-until-given, view each image before attaching, and fallbacks for assignee and upload failures. | 5 / 5 |
Progressive Disclosure | Sections are well organized and navigation is easy, but this is a ~105-line single file with no bundle files or references; the under-50-lines exception for a 5 does not apply, and self-contained detail like the three-way Screenshots procedures and the writing rules could live in a one-level-deep reference file. Anchor 4 ('good structure; most content appropriately placed; minor organization gaps') is the best fit. | 4 / 5 |
Total | 18 / 20 Passed |