Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, highly actionable workflow skill with a clear phased process and strong validation checkpoints. It is somewhat long for a single file with no progressive disclosure via reference files, and a few rules are restated across sections.
Suggestions
Move the full issue-body markdown template and the per-mission-type style-requirements table into a reference file (e.g. references/ISSUE_TEMPLATE.md) and link to it from SKILL.md, reducing the main file's length and improving progressive_disclosure.
De-duplicate rules that appear in both a phase and the Rules section (click/textbox, projectCards deprecation, milestone necessity) by stating them once and cross-referencing, to improve conciseness.
Consider extracting the Phase 4 title-convention rules and Phase 6 writing-style checklist into a reference doc so the core workflow stays lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and free of generic-concept padding, but ~310 lines with some deliberate duplication — the 'Never write click or textbox', projectCards deprecation, and milestone-importance rules each appear in both a phase and the Rules section — that could be tightened without loss. | 2 / 3 |
Actionability | Provides copy-paste-ready, fully executable guidance: exact `gh` commands with flags, a fenced markdown body template, precise title format, jq queries, and concrete file paths — matching the 'fully executable code/commands' anchor. | 3 / 3 |
Workflow Clarity | An explicit 8-phase sequence with validation checkpoints ('Do not proceed until both checks pass', stop on duplicate, confirm before posting) and a dedicated verify/cleanup phase with feedback loops, matching the 'clear sequence with explicit validation steps' anchor. | 3 / 3 |
Progressive Disclosure | Well-organized into phases but presented as a single monolithic ~310-line file with no bundle/reference files (references/scripts/assets absent) and content that could be split — the full issue-body template and per-mission-type style table — kept inline, fitting the 'content that should be separate is inline' anchor. | 2 / 3 |
Total | 10 / 12 Passed |