Azure CLI
Comprehensive Azure Cloud Platform management via command-line interface
[](https://agentverus.ai/skill/7556ade1-10d3-49eb-bdd2-c0d4396a253c)Community Comments
Public comments are the active feedback surface on skill reports right now. Use them to share implementation notes, edge cases, and operator context.
Sign in to comment on this skill
No comments yet. Be the first to share your thoughts.
Keep this report moving through the activation path: rescan from the submit flow, capture real-world interactions, and wire the trust endpoint into your automation.
https://agentverus.ai/api/v1/skill/7556ade1-10d3-49eb-bdd2-c0d4396a253c/trustUse your saved key to act on this report immediately instead of returning to onboarding.
Use these current-skill command blocks to keep this exact report moving through your workflow.
curl -X POST https://agentverus.ai/api/v1/interactions \
-H "Authorization: Bearer at_your_api_key" \
-H "Content-Type: application/json" \
-d '{"agentPlatform":"openclaw","skillId":"7556ade1-10d3-49eb-bdd2-c0d4396a253c","interactedAt":"2026-03-15T12:00:00Z","outcome":"success"}'curl https://agentverus.ai/api/v1/skill/7556ade1-10d3-49eb-bdd2-c0d4396a253c/trustCategory Scores
Findings (14)
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill instructs users to download and execute code from a remote URL, a common supply-chain attack vector.
→ Remove curl-pipe-to-shell patterns. Provide dependencies through safe, verifiable channels.
Piping a downloaded script directly to a shell interpreter. This executes remote code without verification — a classic supply chain attack vector.
→ Review the code block starting at line 55. Ensure this pattern is necessary and does not pose a security risk.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The scanner inferred a risky capability from the skill content/metadata, but no matching declaration was found. Add a declaration with a clear justification, or remove the behavior.
→ Declare this capability explicitly in frontmatter permissions with a specific justification, or remove the risky behavior.
The skill contains a download-and-execute pattern inside a code block. Verify the URL is trustworthy.
→ Pin the installer to a specific version or hash. Consider bundling dependencies instead.
The skill references 6 external URLs and also discusses auth/API/payment workflows, which increases the chance that sensitive operations depend on many remote endpoints.
→ Minimize external dependencies to reduce supply chain risk.
Found environment secret piping pattern: "echo "$AZURE_ACCESS_TOKEN" |" Related auth/profile context: - overlapping signals from the same local context — Credential vault enrollment detected
→ Treat shell pipelines that pass secrets from environment variables as sensitive credential handling. Avoid exposing secret values to command histories or subprocess pipelines unless absolutely necessary.
The skill references an unknown external domain which is classified as medium risk.
→ Verify that this external dependency is trustworthy and necessary.
The skill references an unknown external domain which is classified as low risk.
→ Verify that this external dependency is trustworthy and necessary.
The skill does not include explicit safety boundaries defining what it should NOT do.
→ Add a 'Safety Boundaries' section listing what the skill must NOT do (e.g., no file deletion, no network access beyond needed APIs).
The skill includes output format constraints (length limits, format specifications).
→ Keep these output constraints.
The skill includes error handling instructions for graceful failure.
→ Keep these error handling instructions.