azure-quotas
Verdict safe, but 1 finding (1 medium), mainly data exfiltration. Most recent scan 2026-10-22.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: \"check quotas\", \"service limits\", \"current usage\", \"request quota increase\", \"quota exceeded\", \"validate capacity\", \"regional availability\", \"provisioning limits\", \"vCPU limit\", \"how many vCPUs available in my subscription\".
- Package
- 5 files, 30 KB
- SKILL.md
- 1398 words, 12+ sections
- Code
- PowerShell (1), Shell (1)
- License
- MIT
SKILL.md covers: Azure Quotas - Service Limits & Capacity Management · Overview · When to Use This Skill · Quick Reference · Quota Types · Understanding Resource Name Mapping · Example Mappings · Discovery Workflow · Scripts · Core Workflows · Workflow 1: Check Quota for a Specific Resource · Workflow 2: Compare Quotas Across Regions
Findings
MEDIUM Bash: tainted data flows to dangerous sink Data Exfiltrationbehavioral
Variable $QUOTAS_JSON (line 61) flows to `python3` at line 67.
scripts/check-quota.sh:67
printf '%s\0%s' "$QUOTAS_JSON" "$USAGES_JSON" | python3 -c 'What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 12 KB |
references/advanced-commands.md | doc | 1.8 KB |
references/commands.md | doc | 10 KB |
scripts/check-quota.ps1 | script | 3.3 KB |
scripts/check-quota.sh | script | 3.1 KB |
External hosts referenced
learn.microsoft.com portal.azure.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Environment variables referenced
REGION SUBSCRIPTION_ID RESOURCE_PROVIDER REGIONS
Package contents recorded 2026-10-22 at commit f49ac319a7d3. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Scan history
| Date | Verdict | Findings | Change | Analyzers | Raw |
|---|---|---|---|---|---|
| SAFE | 1 | = | static bytecode pipeline correlation behavioral trigger | JSON | |
| SAFE | 1 | first scan | static bytecode pipeline correlation behavioral trigger | JSON |
Sources
- Repository: https://github.com/microsoft/azure-skills
- Raw scan result: microsoft-azure-skills-skills-azure-quotas-scan.json
- Badge for your README:
 - Request a re-scan