Bicep Diagrams

This one parses Azure Bicep files and generates cloud architecture diagrams by hitting the Eraser API. It reads your .bicep declarations, maps out resource dependencies and module hierarchies, then converts everything into Eraser DSL before rendering it as a visual diagram. Handles the Bicep-specific stuff like showing VNets as containers for subnets, tracking dependsOn relationships, and displaying module boundaries. Built by Eraser Labs, so it's naturally wired into their diagramming service. Useful when you're staring at infrastructure as code and want to see what you're actually deploying without mentally compiling resource blocks. Requires network access since it calls out to the Eraser rendering endpoint.

skills.sh installs: 544
GitHub stars: 47
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add eraserlabs/eraser-io --skill bicep-diagrams --agent claude-code

Installs into .claude/skills of the current project.

Files

Bicep Diagram Generator

Generates architecture diagrams directly from Azure Bicep files. Bicep is a domain-specific language (DSL) for deploying Azure resources declaratively.

When to Use

Activate this skill when:

User has Bicep files (.bicep) and wants to visualize the infrastructure
User asks to "diagram my Bicep" or "visualize this Bicep infrastructure"
User mentions Bicep or Azure Bicep
User wants to see the architecture of their Bicep-deployed resources

How It Works

This skill generates Bicep-specific diagrams by parsing Bicep code and calling the Eraser API directly:

Parse Bicep Files: Identify resource declarations, modules, parameters, and outputs
Extract Relationships: Map dependencies, resource references, and module hierarchies
Generate Eraser DSL: Create Eraser DSL code from Bicep resources
Call Eraser API: Use /api/render/elements with diagramType: "cloud-architecture-diagram"