deploy-model
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- deploy-model
- license
- MIT
- metadata
- { "author": "Microsoft", "version": "1.0.0" }
- description
- Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
02 资源文件 2
- 参考文档skill-report.json221.7 KB
- 参考文档TEST_PROMPTS.md3.3 KB
03 SKILL.md 正文
Deploy Model
Scope — read this first. This skill creates model deployments out-of-band via Azure CLI / MCP / portal. For azd-managed Foundry projects (those scaffolded from
azd-ai-starter-basicor viaazd ai agent init), declare deployments inazure.yaml services.ai-project.deployments[]instead —azd ai agent initwrites the entry from the sample manifest andazd provisioncreates the deployment through Bicep. See foundry-agent/create/create-hosted.md for the Golden Path. Use this skill only for: (a) Foundry projects not managed by an azd project, (b) ad-hoc deployments outside the azd lifecycle.
Unified entry point for all Azure OpenAI model deployment workflows. Analyzes user intent and routes to the appropriate deployment mode.
Quick Reference
| Mode | When to Use | Sub-Skill |
|---|---|---|
| Preset | Quick deployment, no customization needed | preset/SKILL.md |
| Customize | Full control: version, SKU, capacity, RAI policy | customize/SKILL.md |
| Capacity Discovery | Find where you can deploy with specific capacity | capacity/SKILL.md |
Intent Detection
Analyze the user's prompt and route to the correct mode:
User Prompt
│
├─ Simple deployment (no modifiers)
│ "deploy gpt-4o", "set up a model"
│ └─> PRESET mode
│
├─ Customization keywords present
│ "custom settings", "choose version", "select SKU",
│ "set capacity to X", "configure content filter",
│ "PTU deployment", "with specific quota"
│ └─> CUSTOMIZE mode
│
├─ Capacity/availability query
│ "find where I can deploy", "check capacity",
│ "which region has X capacity", "best region for 10K TPM",
│ "where is this model available"
│ └─> CAPACITY DISCOVERY mode
│
└─ Ambiguous (has capacity target + deploy intent)
"deploy gpt-4o with 10K capacity to best region"
└─> CAPACITY DISCOVERY first → then PRESET or CUSTOMIZE
Routing Rules
| Signal in Prompt | Route To | Reason |
|---|---|---|
| Just model name, no options | Preset | User wants quick deployment |
| "custom", "configure", "choose", "select" | Customize | User wants control |
| "find", "check", "where", "which region", "available" | Capacity | User wants discovery |
| Specific capacity number + "best region" | Capacity → Preset | Discover then deploy quickly |
| Specific capacity number + "custom" keywords | Capacity → Customize | Discover then deploy with options |
| "PTU", "provisioned throughput" | Customize | PTU requires SKU selection |
| "optimal region", "best region" (no capacity target) | Preset | Region optimization is preset's specialty |
Multi-Mode Chaining
Some prompts require two modes in sequence:
Pattern: Capacity → Deploy When a user specifies a capacity requirement AND wants deployment:
- Run Capacity Discovery to find regions/projects with sufficient quota
- Present findings to user
- Ask: "Would you like to deploy with quick defaults or customize settings?"
- Route to Preset or Customize based on answer
💡 Tip: If unsure which mode the user wants, default to Preset (quick deployment). Users who want customization will typically use explicit keywords like "custom", "configure", or "with specific settings".
Project Selection (All Modes)
Before any deployment, resolve which project to deploy to. This applies to all modes (preset, customize, and after capacity discovery).
Resolution Order
- Check
PROJECT_RESOURCE_IDenv var — if set, use it as the default - Check user prompt — if user named a specific project or region, use that
- If neither — query the user's projects and suggest the current one
Confirmation Step (Required)
Always confirm the target before deploying. Show the user what will be used and give them a chance to change it:
Deploying to:
Project: <project-name>
Region: <region>
Resource: <resource-group>
Is this correct? Or choose a different project:
1. ✅ Yes, deploy here (default)
2. 📋 Show me other projects in this region
3. 🌍 Choose a different region
If user picks option 2, show top 5 projects in that region:
Projects in <region>:
1. project-alpha (rg-alpha)
2. project-beta (rg-beta)
3. project-gamma (rg-gamma)
...
⚠️ Never deploy without showing the user which project will be used. This prevents accidental deployments to the wrong resource.
Pre-Deployment Validation (All Modes)
Before presenting any deployment options (SKU, capacity), always validate both of these:
-
Model supports the SKU — query the model catalog to confirm the selected model+version supports the target SKU:
az cognitiveservices model list --location <region> --subscription <sub-id> -o jsonFilter for the model, extract
.model.skus[].nameto get supported SKUs. -
Subscription has available quota — check that the user's subscription has unallocated quota for the SKU+model combination:
az cognitiveservices usage list --location <region> --subscription <sub-id> -o jsonMatch by usage name pattern
OpenAI.<SKU>.<model-name>(e.g.,OpenAI.GlobalStandard.gpt-4o). Computeavailable = limit - currentValue.
⚠️ Warning: Only present options that pass both checks. Do NOT show hardcoded SKU lists — always query dynamically. SKUs with 0 available quota should be shown as ❌ informational items, not selectable options.
💡 Quota management: For quota increase requests, usage monitoring, and troubleshooting quota errors, defer to the quota skill instead of duplicating that guidance inline.
Prerequisites
All deployment modes require:
- Azure CLI installed and authenticated (
az login) - Active Azure subscription with deployment permissions
- Azure AI Foundry project resource ID (or agent will help discover it via
PROJECT_RESOURCE_IDenv var)
Sub-Skills
- preset/SKILL.md — Quick deployment to optimal region with sensible defaults
- customize/SKILL.md — Interactive guided flow with full configuration control
- capacity/SKILL.md — Discover available capacity across regions and projects
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.