Content
68%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.
A well-organized, lean body with concrete commands and a complete executable example. The main gap is workflow clarity: the instructions read as a parallel checklist rather than a sequenced validate-then-deploy workflow with error-recovery checkpoints.
Suggestions
Restructure the Instructions into a sequenced workflow with explicit validation checkpoints, e.g.: 1. Author with YAML and parameters, 2. Run 'cfn-lint' and fix findings, 3. 'aws cloudformation validate-template --template-body file://template.yaml', 4. Deploy via change sets, 5. Check drift with 'aws cloudformation detect-stack-drift'.
Spell out the full troubleshooting command, e.g. 'aws cloudformation continue-update-rollback --stack-name my-stack --resources-to-skip LogicalResourceId', to make the recovery path copy-paste ready.
Add an example matching a headline capability (nested stacks or cross-stack exports), or move extended examples into a references/ file to keep SKILL.md as a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive with no padding or explanations of concepts Claude already knows; each instruction is a terse one-liner and the example demonstrates multiple practices. It is not 5 because a few directives restate basic CFN knowledge (e.g., 'Use YAML over JSON for readability') and the example template runs ~30 lines. | 4 / 5 |
Actionability | It provides concrete commands ('aws cloudformation validate-template', 'cfn-lint', 'cfn-nag') and a copy-paste-ready executable YAML example. It is not 5 because the troubleshooting command is not fully spelled out and headline capabilities like nested stacks have no example. | 4 / 5 |
Workflow Clarity | The six numbered instructions are parallel authoring practices rather than a sequenced workflow, and the validation checkpoint (item 5) is implicit rather than embedded in a clear sequence with a fix-and-retry loop. Not 2 because steps and a concrete validation directive do exist; not 4 because there is no clear ordered sequence with most checkpoints present. | 3 / 5 |
Progressive Disclosure | The single-file skill is well organized with clear sections (Use when / Do not use / Instructions / Examples / Best Practices / Troubleshooting) and no unnecessary external references. It is not 5 because the ~72-line body exceeds the simple-skill threshold and extended example content could be split into reference files. | 4 / 5 |
Total | 15 / 20 Passed |