Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A high-quality, token-efficient skill body that leads with critical gotchas, navigates to six real reference files, and gives concrete commands and troubleshooting fixes. The only notable gap is the absence of explicit validation checkpoints/feedback loops in the multi-step workflows, which is especially relevant for AMI rollouts and fleet operations.
Suggestions
Add explicit validate-then-proceed checkpoints to the AMI-rollout and autoscaling-fleet workflows (e.g., verify the new launch-template version passes a smoke test on one instance before kicking off instance refresh).
For instance refresh, document the rollback/validation loop: pin a numeric LT version, start refresh with a small instance-generation batch, confirm healthy before continuing, and how to roll back if the first batches fail.
Add a quick verification step to the SSM 'Connect to a private instance' workflow (e.g., confirm the instance appears as a managed node via describe-instance-information before opening a Session Manager session).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and action-dense throughout — every line carries operational signal (e.g., 'Set HttpPutResponseHopLimit=2 for bridge/awsvpc container workloads', 'Stop/start to migrate to new hardware (reboot won't)') with no padding or explanation of concepts Claude already knows like what EC2 or an AMI is. | 3 / 3 |
Actionability | Concrete, executable guidance throughout — specific CLI flags ('--health-check-type ELB', 'complete-lifecycle-action CONTINUE'), exact values ('HttpPutResponseHopLimit=2', 'price-capacity-optimized'), named policies ('AmazonSSMManagedInstanceCore'), and a symptom/cause/fix troubleshooting table that is copy-paste ready. | 3 / 3 |
Workflow Clarity | Workflows like 'Roll out a new AMI' and 'Stand up an autoscaling web fleet' list steps but omit explicit validation checkpoints and feedback loops; per the rubric, risky fleet/AMI operations without validate-then-proceed gating cap workflow clarity at 2. | 2 / 3 |
Progressive Disclosure | Clear overview with two navigation tables and well-signaled one-level-deep references to six real bundle files (instance-selection.md, provisioning.md, auto-scaling.md, systems-manager.md, ami-management.md, troubleshooting.md), each linked contextually and verified to exist in ./references/. | 3 / 3 |
Total | 11 / 12 Passed |