PaperclipOrg
Claude Agent Skill · by Github

Update Avm Modules In Bicep

Here's a skill that automates the tedious process of keeping Azure Verified Modules current in your Bicep infrastructure files. It scans your Bicep templates, c

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill update-avm-modules-in-bicep
Works with Paperclip

How Update Avm Modules In Bicep fits into a Paperclip company.

Update Avm Modules In Bicep drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md60 lines
Expand
---name: update-avm-modules-in-bicepdescription: 'Update Azure Verified Modules (AVM) to latest versions in Bicep files.'--- # Update Azure Verified Modules in Bicep Files Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions. Limit progress updates to non-breaking changes. Don't output information other than the final output table and summary. ## Process 1. **Scan**: Extract AVM modules and current versions from `${file}`1. **Identify**: List all unique AVM modules used by matching `avm/res/{service}/{resource}` using `#search` tool1. **Check**: Use `#fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`1. **Compare**: Parse semantic versions to identify AVM modules needing update1. **Review**: For breaking changes, use `#fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`1. **Update**: Apply version updates and parameter changes using `#editFiles` tool1. **Validate**: Run `bicep lint` and `bicep build` using `#runCommands` tool to ensure compliance.1. **Output**: Summarize changes in a table format with summary of updates below. ## Tool Usage Always use tools `#search`, `#searchResults`,`#fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks. ## Breaking Change Policy ⚠️ **PAUSE for approval** if updates involve: - Incompatible parameter changes- Security/compliance modifications- Behavioral changes ## Output Format Only display results in table with icons: ```markdown| Module | Current | Latest | Status | Action | Docs ||--------|---------|--------|--------|--------|------|| avm/res/compute/vm | 0.1.0 | 0.2.0 | 🔄 | Updated | [📖](link) || avm/res/storage/account | 0.3.0 | 0.3.0 | ✅ | Current | [📖](link) | ### Summary of Updates Describe updates made, any manual reviews needed or issues encountered.``` ## Icons - 🔄 Updated- ✅ Current- ⚠️ Manual review required- ❌ Failed- 📖 Documentation ## Requirements - Use MCR tags API only for version discovery- Parse JSON tags array and sort by semantic versioning- Maintain Bicep file validity and linting compliance