Certification requirements and best practices for Azure Terraform modules seeking AVM compliance.
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 azure-verified-modulesCompatible with
Supported agents
Enforces provider version constraints (azurerm >= 4.0, < 5.0; azapi >= 2.0, < 3.0) and prohibits git-based module references in favor of pinned Terraform registry sources
Mandates lower snake_casing for all identifiers, precise variable types, discrete output attributes via anti-corruption layer pattern, and alphabetically ordered locals
Requires feature toggle variables for ne
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionazure-verified-modulesExecute the skills CLI command in your project's root directory to begin installation:
epx add hashicorp/agent-skills --skill azure-verified-modulesFetches azure-verified-modules 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/azure-verified-modules
Restart Cursor to activate azure-verified-modules. Access via /azure-verified-modulesin 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.
refactor-module
hashicorp/agent-skills · Productivity · same repo
azure-cloud-migrate
microsoft/azure-skills · Cloud · tag: azure
azure-cost-optimization
microsoft/github-copilot-for-azure · Cloud · tag: azure
azure-storage
microsoft/azure-skills · Cloud · tag: azure
azure-compliance
microsoft/azure-skills · Cloud · tag: azure
entra-app-registration
microsoft/GitHub-Copilot-for-Azure · Cloud · tag: azure
azure-verified-modules reduced setup friction for our internal harness; good balance of opinion and flexibility.
azure-verified-modules reduced setup friction for our internal harness; good balance of opinion and flexibility.
azure-verified-modules has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: azure-verified-modules is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added azure-verified-modules from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: azure-verified-modules is focused, and the summary matches what you get after install.
I recommend azure-verified-modules for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend azure-verified-modules for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
azure-verified-modules fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
azure-verified-modules has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 38