Content
65%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 concrete executable commands and a clear sequenced workflow, but it is held back by redundancy between sections, implicit rather than explicit validation checkpoints in the workflow, and an orphaned helper script that the body never surfaces.
Suggestions
Wire scripts/drift-check.sh into the Instructions (e.g., "Run scripts/drift-check.sh <iac-dir> to perform init + plan -detailed-exitcode") so the existing bundle asset is actually reachable, and replace the boilerplate references/assets READMEs with skill-specific material or remove them.
Make validation explicit in the workflow: after step 3, add a checkpoint such as "Check the plan exit code: 0 = no drift, 2 = drift detected, 1 = error — resolve errors before interpreting drift," and gate the destructive step 7 (terraform apply) behind an explicit confirmation/validation step.
Tighten redundancy: collapse the Overview into the body without restating the description, and remove the Output items that duplicate Instruction step 7; fix the empty Pulumi resource link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is action-dense and avoids explaining concepts Claude already knows, but the Overview duplicates the frontmatter description and the Output section restates remediation commands already covered in Instruction step 7; the empty Pulumi resource link adds dead weight. It is mostly efficient but could be tightened, fitting the 2 anchor rather than the lean/every-token-earns-its-place 3 anchor. | 2 / 3 |
Actionability | Concrete executable commands with specific flags and exit codes appear throughout — "terraform plan -detailed-exitcode" (exit code 2 = drift), "aws cloudformation detect-stack-drift", "terraform force-unlock <ID>" — and the Error Handling table gives copy-paste-ready solutions, matching the fully-executable anchor. | 3 / 3 |
Workflow Clarity | A clear 9-step numbered sequence exists, but validation checkpoints are implicit rather than explicit (the exit-code-2 signal is mentioned in passing, not as a branch point), and the destructive remediation step ("terraform apply to enforce desired state") lacks an explicit validation gate before enforcement. This fits the sequence-present-but-checkpoints-missing anchor at 2, not the explicit-validation/feedback-loop anchor at 3. | 2 / 3 |
Progressive Disclosure | The body is well-sectioned, but bundle integration is poor: scripts/drift-check.sh directly implements steps 2–3 yet is never referenced from the body, and the references/ and assets/ directories contain only generic boilerplate README templates rather than skill-specific material. This matches the some-structure-but-references-not-clearly-signaled anchor at 2. | 2 / 3 |
Total | 9 / 12 Passed |