Content
82%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 skill is highly actionable with executable code and a clear, verified workflow; it is lean and well-structured. The main gap is the absence of an explicit error-recovery loop and the lack of any split-out script reference for the larger code blocks.
Suggestions
Add a feedback loop after Step 4 (e.g. if ghp/ghw api user fails, recheck profile load and PATH) to strengthen workflow_clarity for the system-altering setup.
Consider moving the PowerShell setup block into a scripts/ file referenced once, reducing inline bulk and improving progressive_disclosure.
Generalize the repo-specific binding block (bradygaster/squad) so it reads as a pattern rather than a hard-coded example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence without explaining gh or PowerShell basics; the only mild redundancy is the function block appearing both for the profile and the current session, which is justified by intent. | 4 / 5 |
Actionability | Provides fully executable, copy-paste-ready PowerShell with clearly marked placeholders, concrete verification commands (ghp api user --jq '.login'), and specific shell built-ins — covering the common cases completely. | 5 / 5 |
Workflow Clarity | Steps 1–5 are clearly sequenced and a verification step (Step 4) is present for a profile/PATH-modifying operation, but there is no explicit error-recovery feedback loop if verification fails. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly headed sections with no nested or broken references and no bundle files to navigate; at ~85 lines the inlined PowerShell blocks could arguably live in a script, so it stops just short of 5. | 4 / 5 |
Total | 17 / 20 Passed |