capacity
Skill7 starsChanged 21 days agoMITView on GitHub
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/frontier-ai-governance-rvasword for word, first seen Oct 25, 2026
- microsoft/frontier-agentic-cobuild-rvasword for word, first seen Oct 13, 2026
- microsoft/GitHub-Copilot-for-Azureword for word, first seen Oct 13, 2026
- microsoft/skillsword for word, first seen Oct 13, 2026
- microsoft/azure-skillsword for word, first seen Oct 13, 2026
- microsoft/agent-skillsword for word, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 7
- microsoft/agent-skills★ 3.2k100% same
- microsoft/skills★ 3.2k100% same
- microsoft/azure-skills★ 1.6k100% same
- microsoft/GitHub-Copilot-for-Azure★ 262100% same
- jorgeasaurus/agent-skills★ 14100% same
- microsoft/frontier-agentic-cobuild-rvas★ 7100% same
- microsoft/frontier-ai-governance-rvas★ 1100% same
Edited · 0
None found.
Wrote their own version · 2
- skyf0xx/gambit★ 29same name
- Joshua-Palamuttam/workbench-template★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- azure-aigatewaySkill
- azure-aiSkill
- diagram-designSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- finetuningSkill
- customizeSkill
- presetSkill
- deploy-modelSkill
- microsoft-foundrySkill
- rvap-brandSkill
- writing-for-agentsSkill
- agentic-workflowsSkill
- content-accuracy-auditSkill
- foundry-hosted-agentsSkill
- foundry-iq-knowledge-basesSkill
- foundry-modelsSkill
- foundry-observabilitySkill
- foundry-projects-resourcesSkill
- foundry-toolboxesSkill
- foundry-workflowsSkill
- impeccableSkill
- ai-agent-creatorSkill
- cloud-architecture-diagramSkill
- idea-forgeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 68
Run the full discovery script with model name, version, and minimum capacity target:
- Distinctive: line 81
After discovery identifies candidate regions, validate that the user's subscription actually has available quota in each region.
- Distinctive: line 108
Add a "Quota Available" column to the ranked output from Phase 3:
- Distinctive: line 120
After the script outputs the ranked table (now annotated with quota info), present it to the user and ask:
- Distinctive: line 129
Before handing off to preset or customize, always confirm the target project with the user.
- Distinctive: line 131
If the discovery table shows a sample project for the chosen region, suggest it as the default.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Capacity Discovery
Finds available Azure OpenAI model capacity across all accessible regions and projects. Recommends the best deployment location based on capacity requirements.
Quick Reference
| Property | Description |
| Purpose | Find where you can deploy a model with sufficient capacity |
| Scope | All regions and projects the user has access to |
| Output | Ranked table of regions/projects with available capacity |
| Action | Read-only analysis — does NOT deploy. Hands off to preset or customize |
| Authentication | Azure CLI (az login) |
When to Use This Skill
- ✅ User asks "where can I deploy gpt-4o?"
- ✅ User specifies a capacity target: "find a region with 10K TPM for gpt-4o"
- ✅ User wants to compare availability: "which regions have gpt-4o available?"
- ✅ User got a quota error and needs to find an alternative location
- ✅ User asks "best region and project for deploying model X"
After discovery → hand off to preset or customize for actual deployment.
Scripts
Pre-built scripts handle the complex REST API calls and data processing. Use these instead of constructing commands manually.
| Script | Purpose | Usage |
scripts/discover_and_rank.ps1 | Full discovery: capacity + projects + ranking | Primary script for capacity discovery |
scripts/discover_and_rank.sh | Same as above (bash) | Primary script for capacity discovery |
scripts/query_capacity.ps1 | Raw capacity query (no project matching) | Quick capacity check or version listing |
scripts/query_capacity.sh | Same as above (bash) | Quick capacity check or version listing |
Workflow
Phase 1: Validate Prerequisites
az account show --query "{Subscription:name, SubscriptionId:id}" --output tablePhase 2: Identify Model and Version
Extract model name from user prompt. If version is unknown, query available versions:
.\scripts\query_capacity.ps1 -ModelName <model-name>./scripts/query_capacity.sh <model-name>This lists available versions. Use the latest version unless user specifies otherwise.
Phase 3: Run Discovery
Run the full discovery script with model name, version, and minimum capacity target:
.\scripts\discover_and_rank.ps1 -ModelName <model-name> -ModelVersion <version> -MinCapacity <target>./scripts/discover_and_rank.sh <model-name> <version> <min-capacity>💡 The script automatically queries capacity across ALL regions, cross-references with the user's existing projects, and outputs a ranked table sorted by: meets target → project count → available capacity.
Phase 3.5: Validate Subscription Quota
After discovery identifies candidate regions, validate that the user's subscription actually has available quota in each region. Model capacity (from Phase 3) shows what the platform can support, but subscription quota limits what this specific user can deploy.
# For each candidate region from discovery results:
$usageData = az cognitiveservices usage list --location <region> --subscription $SUBSCRIPTION_ID -o json 2>$null | ConvertFrom-Json
# Check quota for each SKU the model supports
# Quota names follow pattern: OpenAI.<SKU>.<model-name>
$usageEntry = $usageData | Where-Object { $_.name.value -eq "OpenAI.<SKU>.<model-name>" }
if ($usageEntry) {
$quotaAvailable = $usageEntry.limit - $usageEntry.currentValue
} else {
$quotaAvailable = 0 # No quota allocated
}# For each candidate region from discovery results:
usage_json=$(az cognitiveservices usage list --location <region> --subscription "$SUBSCRIPTION_ID" -o json 2>/dev/null)
# Extract quota for specific SKU+model
quota_available=$(echo "$usage_json" | jq -r --arg name "OpenAI.<SKU>.<model-name>" \
'.[] | select(.name.value == $name) | .limit - .currentValue')Annotate discovery results:
Add a "Quota Available" column to the ranked output from Phase 3:
| Region | Available Capacity | Meets Target | Projects | Quota Available |
| eastus2 | 120K TPM | ✅ | 3 | ✅ 80K |
| westus3 | 90K TPM | ✅ | 1 | ❌ 0 (at limit) |
| swedencentral | 100K TPM | ✅ | 0 | ✅ 100K |
Regions/SKUs where quotaAvailable = 0 should be marked with ❌ in the results. If no region has available quota, hand off to the quota skill for increase requests and troubleshooting.
Phase 4: Present Results and Hand Off
After the script outputs the ranked table (now annotated with quota info), present it to the user and ask:
- 🚀 Quick deploy to top recommendation with defaults → route to preset
- ⚙️ Custom deploy with version/SKU/capacity/RAI selection → route to customize
- 📊 Check another model or capacity target → re-run Phase 2
- ❌ Cancel
Phase 5: Confirm Project Before Deploying
Before handing off to preset or customize, always confirm the target project with the user. See the Project Selection rules in the parent router.
If the discovery table shows a sample project for the chosen region, suggest it as the default. Otherwise, query projects in that region and let the user pick.
Error Handling
| Error | Cause | Resolution |
| "No capacity found" | Model not available or all at quota | Hand off to quota skill for increase requests and troubleshooting |
| Script auth error | az login expired | Re-run az login |
| Empty version list | Model not in region catalog | Try a different region: ./scripts/query_capacity.sh <model> "" eastus |
| "No projects found" | No AI Services resources | Guide to project/create skill or Azure Portal |
Related Skills
- preset — Quick deployment after capacity discovery
- customize — Custom deployment after capacity discovery
- quota — For quota viewing, increase requests, and troubleshooting quota errors, defer to this skill instead of duplicating guidance
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

