azure-bicep

Automate Azure infrastructure authoring and governance with Bicep.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill azure-bicep-kyle-deprow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-bicep
Source: https://github.com/kyle-deprow/ai_scaffolding/tree/main/skills/azure-bicep
Command: npx skills add https://github.com/kyle-deprow/ai_scaffolding --skill azure-bicep-kyle-deprow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azure infrastructure teams struggle with inconsistent Bicep templates, leading to drift and security gaps. This skill provides a structured approach to authoring modular, secure, and maintainable Bicep configurations that align with best practices.

Core Features & Use Cases

  • Design modular Bicep templates that promote reuse and reduce monoliths.
  • Enforce parameterization, naming conventions, explicit API versions, and mandatory tagging for predictable deployments.
  • Review IaC for security and compliance, including encryption, private networking, and RBAC least-privilege.
  • Convert or refactor ARM templates to Bicep and establish governance for ARM -> Bicep migrations.

Quick Start

Create a production-ready Bicep module skeleton for a storage account in a chosen region that enforces parameterization, naming conventions, and tagging.

Frequently Asked Questions about azure-bicep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce security and naming conventions in Bicep infrastructure-as-code?

Bicep module design for scalable infrastructure-as-code uses parameterization, explicit API versions, and naming conventions to reduce monoliths and promote template reuse across Azure resources.

How do I convert ARM templates to Bicep for Azure deployments?

To create a production-ready Bicep module for an Azure storage account, define parameterization, naming conventions, and mandatory tagging within a modular template skeleton tailored to your chosen deployment region.

What is the best way to structure Bicep modules for Azure infrastructure?

Reviewing Bicep infrastructure-as-code for compliance checks encryption, private networking, and RBAC least-privilege configurations, applying documented rules to identify security gaps and configuration drift.

Can I use Bicep for Azure infrastructure governance and security hardening?

Bicep infrastructure-as-code addresses security gaps and configuration drift by enforcing explicit API versions, module boundaries, and mandatory diagnostic practices through documented rules and examples.

Why does my Bicep template have configuration drift and security gaps?

Bicep infrastructure-as-code addresses security gaps and configuration drift by enforcing explicit API versions, module boundaries, and mandatory diagnostic practices through documented rules and examples.

Do I need explicit API versions in Bicep for predictable Azure deployments?

Bicep infrastructure-as-code addresses security gaps and configuration drift by enforcing explicit API versions, module boundaries, and mandatory diagnostic practices through documented rules and examples.