Generate and maintain Terraform code following HashiCorp's official style conventions.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add hashicorp/agent-skills --skill terraform-style-guideCompatible with
Supported agents
Enforces two-space indentation, lowercase underscore naming, and standard file organization across terraform.tf , providers.tf , main.tf , variables.tf , outputs.tf , and locals.tf
Requires type and description on all variables and outputs, with validation rules and sensitive flag support for credentials
Prioritizes for_each over count for dynamic resources, applies security hardening (encryption,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionterraform-style-guideExecute the skills CLI command in your project's root directory to begin installation:
epx add hashicorp/agent-skills --skill terraform-style-guideFetches terraform-style-guide from hashicorp/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/terraform-style-guide
Restart Cursor to activate terraform-style-guide. Access via /terraform-style-guidein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
terraform-skill
sickn33/antigravity-awesome-skills · Cloud · tag: terraform
novel-writer-workflow-guide
wordflowlab/novel-writer-skills · Frontend · tag: guide
oiloil-ui-ux-guide
oil-oil/oiloil-ui-ux-guide · Frontend · tag: guide
writing-style
different-ai/agent-bank · Productivity · tag: style
adev-writing-guide
angular/angular · Frontend · tag: guide
implementing-infrastructure-as-code-security-scanning
mukul975/Anthropic-Cybersecurity-Skills · implementing-infrastructure-as-code-security-scanning · tag: terraform
terraform-style-guide has been reliable in day-to-day use. Documentation quality is above average for community skills.
terraform-style-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: terraform-style-guide is focused, and the summary matches what you get after install.
Registry listing for terraform-style-guide matched our evaluation — installs cleanly and behaves as described in the markdown.
terraform-style-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added terraform-style-guide from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: terraform-style-guide is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend terraform-style-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
terraform-style-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
terraform-style-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 26