Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a concise, well-organized, single-purpose Terraform reference that assumes Claude's competence and avoids padding. Its main weakness is actionability and workflow clarity: it references commands inline without complete worked examples or explicit validation gates.
Suggestions
Add at least one complete, copy-paste example block, e.g. a minimal module with required_providers, a typed variable, and an output, to lift actionability to fully executable.
Make the risky-operation workflow an explicit numbered sequence with a hard checkpoint: 1) plan, 2) review output, 3) confirm no unexpected destroys, 4) apply — so validation is a gate rather than implied review.
Show a concrete import/state-refactor example (terraform import + terraform state mv) since state operations are error-prone and currently only named, not demonstrated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean bullet-point guidance that assumes Terraform competence and never explains basic concepts (e.g., what Terraform or HCL is); every line is actionable, fitting 'lean and efficient; assumes Claude's competence; every token earns its place'. | 3 / 3 |
Actionability | It cites concrete, runnable commands and constructs ('terraform plan', 'terraform state mv', 'terraform import', 'for_each over count', 'required_providers'), but provides no complete copy-paste code blocks, so it is not fully 'copy-paste ready', matching 'some concrete guidance but incomplete'. | 2 / 3 |
Workflow Clarity | It states a plan-before-apply sequence and a destroy guardrail ('Always run terraform plan before terraform apply. Review the plan output carefully'; 'Never run terraform destroy in production without explicit confirmation and a reviewed plan'), but the validation is a manual review rather than an explicit validate-and-proceed gate, and the steps are scattered across sections rather than a sequenced workflow. | 2 / 3 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, and organized into clear sections (Key Principles, Module Design, State Management, Best Practices, Pitfalls) with no external references needed; per the simple-skills note this can score 3 with well-organized sections. | 3 / 3 |
Total | 10 / 12 Passed |