Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with a clearly sequenced, well-validated workflow for a genuinely complex destructive operation. Its main weaknesses are verbosity from repeated emphasis callouts and duplicated flows, plus a monolithic structure that for a skill this size would benefit from referenced detail files.
Suggestions
Consolidate the repeated MANDATORY/STRICT SEQUENCING/Critical callouts into a single sequencing rule stated once near the top, and reference it instead of re-declaring it at each step.
Extract the aws-mcp fallback path (and/or the detailed local-git push flow) into a referenced file (e.g. FALLBACK.md) and keep SKILL.md as a concise overview pointing to it, reducing the monolithic length.
Shorten the multi-line quoted user prompts to the essential approval question, since Claude can phrase the surrounding context itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most operational detail (exact tool signatures, bash, polling intervals) earns its place, but the ~400-line body repeats sequencing emphasis via multiple MANDATORY/STRICT SEQUENCING/Critical callouts, embeds lengthy quoted user prompts, and duplicates the core auto-fix flow in the fallback section — it could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash snippets, exact tool-call signatures with parameters, copy-paste JSON examples, concrete polling intervals (30s/15s), and enumerated terminal statuses — copy-paste ready. | 3 / 3 |
Workflow Clarity | Numbered, strictly sequenced steps with explicit validation checkpoints (base-branch verify, sensitive-file grep, branch verification before push, approval gates) and feedback loops (quick failure → list_associations; throttling retry) on destructive operations. | 3 / 3 |
Progressive Disclosure | No bundle files exist and everything lives in one large monolithic SKILL.md; the sizable local-git flow and aws-mcp fallback path are inline content that, for a skill this large, could be split into referenced files. Sections are well-organized, so it is above a wall-of-text, but no progressive disclosure is used. | 2 / 3 |
Total | 10 / 12 Passed |