azure-cli

The skill claims to be an Azure CLI management skill and includes many legitimate az commands and helper scripts. However, the registry metadata lists no required binaries while the scripts clearly invoke the 'az' CLI (and 'jq' in a couple places). A management skill that runs az commands would reasonably be expected to declare the az binary (and any other runtime tools) as requirements. The SKILL.md/repository fields also point to the official Azure CLI repo while the package owner is an unrelated ID — potential misrepresentation of origin.

SKILL.md and included scripts provide concrete commands and helper scripts that can create, modify, and delete Azure resources (az group delete, az vm delete, resource cleanup with delete flag). That behavior is consistent with a cloud management skill, but it means the agent (or user) must have authenticated Azure credentials and should understand the destructive effects of some commands. The instructions do not attempt to read unrelated local files or exfiltrate data to external endpoints.

There is no install spec (instruction-only), which minimizes supply-chain risk. The skill bundle includes scripts and docs but does not fetch or execute remote code during install. This is appropriate for documentation/scripts only.

requires.env and primary credential are empty despite SKILL.md showing examples that use service principal environment variables ($AZURE_CLIENT_ID, $AZURE_CLIENT_SECRET, $AZURE_TENANT_ID) and the scripts requiring authenticated az access. The skill also uses 'jq' but does not declare it. Not declaring required credentials/binaries is an omission that makes assessing privileges harder and is disproportionate to the stated purpose.

always is false and model invocation is allowed (the platform default). The skill does not request persistent system-wide changes at install time. It contains scripts that an agent could run while authorized, but that is expected for a management skill.