azure-hosted-copilot-sdk
Build, deploy, modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github/copilot-sdk or CopilotClient — use this skill instead of azure-prepare. PREFER OVER azure-prepare when codebase contains copilot-sdk markers. WHEN: copilot SDK, @github/copilot-sdk, copilot-powered app, deploy copilot app, add feature, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: general web apps without copilot SDK (use azure-prepare), Copilot Extensions, Foundry agents (use microsoft-foundry).
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that covers all critical dimensions. It provides specific actions, comprehensive trigger terms including package names and CLI commands, explicit when/when-not guidance, and proactive conflict resolution with related skills. The description is concise yet thorough, making it highly effective for skill selection among many candidates.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Build, deploy, modify GitHub Copilot SDK apps on Azure.' Also specifies what it does NOT cover, adding further specificity. | 3 / 3 |
Completeness | Clearly answers 'what' (build, deploy, modify GitHub Copilot SDK apps on Azure) and 'when' with an explicit WHEN clause listing trigger terms. Also includes 'DO NOT USE FOR' guidance with alternative skill recommendations, which strengthens routing clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including package names (@github/copilot-sdk, CopilotClient), user actions (deploy copilot app, add feature, modify copilot app), acronyms (BYOM), and CLI commands (azd init copilot). These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit conflict resolution: states 'MANDATORY when codebase contains @github/copilot-sdk', 'PREFER OVER azure-prepare', and 'DO NOT USE FOR' clauses that explicitly redirect to azure-prepare and microsoft-foundry for non-matching cases. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestration skill with clear routing logic, concrete detection procedures, and good progressive disclosure to reference files. The main weakness is some verbosity in the detection section, where multiple warnings repeat the same routing mandate. Overall it provides strong actionable guidance for a complex multi-path workflow.
Suggestions
Consolidate the three separate ⚠️ warnings in the detection section into a single concise warning — they all convey the same message about routing priority.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The detection procedure section is somewhat verbose with repeated warnings and a table of prompt patterns that Claude could infer. The routing table and steps are lean, but the mandatory first check section has redundant emphasis (multiple ⚠️ warnings saying the same thing). | 2 / 3 |
Actionability | Provides concrete commands (`azd init --template azure-samples/copilot-sdk-service`, `docker info`), specific detection markers with exact locations to check, clear routing tables mapping user intent to actions, and specific auth patterns (DefaultAzureCredential, bearerToken). Guidance is specific and executable. | 3 / 3 |
Workflow Clarity | Clear sequenced workflow: detection → route → scaffold/deploy → model config → deploy. Step 4 explicitly sequences sub-skills (azure-prepare → azure-validate → azure-deploy). The detection procedure has numbered steps with clear conditionals. Validation is handled via the azure-validate sub-skill invocation. | 3 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references: SDK ref, deploy existing ref, auth-best-practices.md, model config ref, and existing-project-integration.md are all clearly signaled with descriptive link text. The main skill stays as a concise overview with routing logic while deferring details appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
742d20b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.