terraform

I took a look at your terraform skill and wanted to share some thoughts.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 74/100, solidly in C territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Ease of Use (22/25)—the metadata and trigger patterns are really well done. The weakest spot is Progressive Disclosure Architecture (18/30)—everything's loaded at once, which burns tokens unnecessarily.

What's Working Well

• Metadata is chef's kiss. Your description clearly explains the READ-ONLY constraint, and your trigger patterns cover terraform commands, file types, and cloud provider prefixes (aws_, azurerm_, google_). That's thorough.
• Command safety is solid. The forbidden/allowed command lists are comprehensive and make the constraint crystal clear to users. This is exactly what a skill should do for sensitive domains.
• HCL patterns are practical. Your module structure, variable definitions, and lifecycle rules are real examples developers actually need.

The Big One: Token Efficiency (High Priority)

Right now, all 360 lines load every time someone uses your skill. That's wasteful. You need a references directory with on-demand-loaded files.

Here's the fix:

• Create references/aws-patterns.md (provider configs, common resources)
• Create references/lifecycle-rules.md (the detailed lifecycle examples)
• Create references/module-structure.md (complete module templates)

Keep only the essentials in SKILL.md—the critical safety restrictions and quick-start. The patterns section becomes a pointer: "See module structure reference for complete templates."

Impact: This single change gets you +8 points, pushing you to 82/100 (B territory).

Other Things Worth Fixing

1. Duplicate command lists — You list allowed/forbidden commands twice (in critical_restriction and user_instructions). Keep the detailed version in one place, reference it in the other. Saves clutter and maintenance headaches. (+1 point)

2. Add a table of contents — At 360 lines, readers need quick navigation. Add a TOC right after the frontmatter linking to major sections. (+2 points)

3. Workflow isn't numbered — Your quick start shows what to do but not the steps. Try: "1. Create provider config → 2. Set up backend → 3. Define modules → 4. Run terraform init." Makes it scannable. (+2 points)

4. No input/output examples — Show what terraform produces. Like: "When you write this module config, terraform plan shows these resources." Helps users understand scope. (+1 point)

Quick Wins

• Move patterns to references/ directory (+8 points)
• Deduplicate command lists (+1 point)
• Add TOC (+2 points)
• Numbered workflow steps (+2 points)

That's +13 points with focused effort—gets you to 87/100 (solid B).

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.