Content
92%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 content is an exemplary lean, instruction-only skill: specific commands, flag semantics Claude would not know, explicit verification steps, and clean sectioning. The only minor gap is the absence of a complete gh issue create/--body-file command example for the most common use case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense with operational detail — title prefix templates, the --body-file pattern, flag semantics for attachments — with zero padding or explanation of concepts Claude already knows. Every token earns its place. | 5 / 5 |
Actionability | Concrete, copy-paste-ready commands are given for verification (gh issue view --json title,body) and attachment (gh issue edit --attach '...#alt text'), plus explicit --body-file guidance. It is not a 5 because no complete command example is shown for the most common cases, gh issue create and gh issue comment. | 4 / 5 |
Workflow Clarity | The workflow includes an explicit validation checkpoint after create/edit (verify title and body, confirm real newlines vs literal \n) and an error-recovery loop for partial attachment failures ("inspect the issue before retrying to avoid duplicates"), matching the top anchor. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines with no need for external references, and its four well-organized sections (Titles, Markdown bodies and comments, Attachments, Relationships) plus a clearly signaled one-level pointer to the issue-management skill match the simple-skill exception for a top score. | 5 / 5 |
Total | 19 / 20 Passed |