bicep-diagrams

Parse Azure Bicep code and render architecture diagrams via the Eraser API.

32|7|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/eraserlabs/eraser-io --skill bicep-diagrams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bicep-diagrams
Source: https://github.com/eraserlabs/eraser-io/tree/main/skills/bicep-diagrams
Command: npx skills add https://github.com/eraserlabs/eraser-io --skill bicep-diagrams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and cloud engineers turn Azure Bicep definitions into clear, shareable diagrams, making it easier to reason about infrastructure.

Core Features & Use Cases

  • Parse Bicep resources, modules, parameters, and dependencies to build a coherent diagram.
  • Show resource relationships and module boundaries to reflect deployment structure.
  • Generate an Eraser diagram via the Eraser API for visualizing cloud architectures.

Quick Start

Use the bicep-diagrams skill with your main.bicep file (and any modules). The AI will parse the Bicep definitions and render a cloud-architecture diagram.

Frequently Asked Questions about bicep-diagrams

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

FAQPage Schema
How do I visualize Azure Bicep infrastructure as code?

To visualize Azure Bicep infrastructure, you can parse your Bicep deployments and modules to generate architecture diagrams. This process reads Bicep constructs, maps dependencies, and renders visual representations of resources and module boundaries.

Can I generate a diagram from Bicep module dependencies?

Yes, you can generate a diagram from Bicep module dependencies by parsing your Bicep code. It maps dependsOn relationships and module boundaries to convert resources into a visual cloud architecture diagram.

What is the best way to diagram Azure Bicep resources and parameters?

The best way to diagram Azure Bicep resources and parameters is to parse the Bicep definitions and convert them into a diagramming DSL. This approach builds a coherent visual representation of resource relationships and deployment structure.

Do I need a specific diagramming tool to render Bicep architecture diagrams?

You do not need a separate diagramming tool because the parsing process converts Bicep constructs directly into a diagramming DSL and renders the cloud architecture via the Eraser API without external diagram software.

Does visualizing Bicep deployments work with complex module boundaries?

Visualizing Bicep deployments works with complex module boundaries by parsing the Bicep code to reflect deployment structure accurately. It maps resource dependencies and module boundaries to build a coherent architecture diagram.