Content
57%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill establishes useful repository boundaries and a basic workflow for terraform changes, with a good safety gate at step 1. However, it lacks concrete terraform commands (plan, apply, validate, fmt), specific examples, and explicit feedback loops for infrastructure operations. The content is reasonably concise but could be more actionable.
Suggestions
Add specific terraform commands to each workflow step (e.g., `terraform plan`, `terraform apply`, `terraform fmt`, `terraform validate`) instead of vague instructions like 'apply your changes'.
Show an example invocation of `@scripts/check.sh` with expected output so Claude knows what success and failure look like.
Add an explicit validate-fix-retry loop for steps 2-3: e.g., 'Run terraform plan → review output → if errors, fix and re-run plan → only apply when plan is clean'.
Remove the generic opening sentence ('When working with terraform code...guidelines to help you achieve this') — it adds no value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient. The opening sentence ('it's important to maintain a consistent style and structure. Here are some guidelines to help you achieve this.') is unnecessary filler that Claude doesn't need, but the rest is lean and informative. | 4 / 5 |
Actionability | Provides some concrete guidance (repository boundaries, the check script reference, branch workflow), but lacks executable examples. Steps like 'apply your changes' and 'verify that everything STILL works' are vague — no terraform commands (plan, apply, fmt, validate) are specified. The check script reference is helpful but no example invocation or expected output is shown. | 3 / 5 |
Workflow Clarity | A numbered sequence exists with a useful gate at step 1 ('if step 1 fails, DO NOT continue'), which is a good validation checkpoint. However, 'apply your changes' and 'verify that everything STILL works' are underspecified. There's no explicit validation-fix-retry loop for steps 2-3 beyond 'feel free to fix issues if you can.' For infrastructure changes (destructive/batch operations), the missing explicit feedback loop caps this at 3. | 3 / 5 |
Progressive Disclosure | References the check script via @scripts/check.sh, which is good, but no bundle files are provided to verify this. The skill is relatively short and doesn't need heavy splitting, but it could benefit from linking to a more detailed terraform conventions file or examples. The structure has sections but could be better organized (e.g., separating 'verification' into its own clearly navigable section). | 3 / 5 |
Total | 13 / 20 Passed |