Skip to content
TrustedSkillsbeta
Back to all skills

Azure Resource Discovery

Checked
mindmorass·vlatest·cloud

Quickly identifies Azure resources (VMs, databases, etc.) within a subscription based on specified criteria.

Repository

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 mindmorass/reflex --skill azure-resource-discovery -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

mindmorass

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 mindmorass/reflex at b87139cce6.

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

Commit
b87139cce6
Manifest
plugins/reflex/skills/azure-resource-discovery/SKILL.md
Scanned
1 file, 734 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 allows AI agents to discover and list Azure resources. It leverages the Azure Resource Graph API to query for resources based on various criteria, providing a detailed inventory of your cloud infrastructure. The agent can then present this information in a structured format for analysis or further action.

When to use it

  • Inventory Management: Quickly identify all virtual machines running in a specific region.
  • Cost Optimization: Determine the number and type of storage accounts being used to assess potential cost savings.
  • Security Audits: List all resources with public IP addresses for security review.
  • Compliance Checks: Identify resources tagged with specific compliance labels.

Key capabilities

  • Azure Resource Graph API integration
  • Resource listing based on various filters (region, resource type, tags)
  • Structured output of discovered resources

Example prompts

  • "List all virtual machines in the West US region."
  • "Show me all storage accounts tagged with 'environment:production'."
  • "Find all resources with public IP addresses."

Tips & gotchas

  • Requires appropriate Azure permissions to access the Resource Graph API. Ensure the agent has a service principal or managed identity configured with sufficient roles (e.g., Reader).