Skip to content
TrustedSkillsbeta
Back to all skills

Bicep Diagrams

Listed
eraserlabs·vlatest·cloud·MIT

Generates Bicep infrastructure-as-code diagrams for visual understanding and collaboration, streamlining Azure deployments.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add eraserlabs/eraser-io --skill bicep-diagrams -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

eraserlabs

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: app.eraser.io.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    app.eraser.ioundeclared

    What it found

    • skills/bicep-diagrams/SKILL.md:90contacts app.eraser.io
      curl -X POST https://app.eraser.io/api/render/elements \
  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned eraserlabs/eraser-io at 30d6f3679f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 249 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill generates diagrams from Bicep code. It allows users to visualize their infrastructure as code, making complex deployments easier to understand and debug. The generated diagrams represent the resources defined in the Bicep file and their dependencies.

When to use it

  • Understanding Complex Deployments: Use this when you need a visual representation of your Azure infrastructure deployed via Bicep.
  • Debugging Deployment Issues: Quickly identify dependencies and potential bottlenecks during deployment troubleshooting.
  • Documentation & Knowledge Sharing: Create diagrams to document existing deployments or share architectural overviews with team members.
  • Onboarding New Team Members: Help new engineers understand the structure of your infrastructure by providing visual aids.

Key capabilities

  • Diagram generation from Bicep code
  • Visualization of resource dependencies
  • Support for Azure infrastructure as code

Example prompts

  • "Generate a diagram for this Bicep file: [paste Bicep code here]"
  • "Show me the dependencies in my deployment defined by this Bicep file."
  • "Create a visual representation of the resources deployed using this Bicep script."

Tips & gotchas

  • The quality and clarity of the diagram depend on the complexity of the Bicep code. Very large or deeply nested deployments may result in less readable diagrams.