azure-hosted-copilot-sdk
Build and deploy GitHub Copilot SDK apps to Azure. USE FOR: build copilot app, create copilot app, copilot SDK, @github/copilot-sdk, scaffold copilot project, copilot-powered app, deploy copilot app, host on azure, azure model, BYOM, bring your own model, use my own model, azure openai model, DefaultAzureCredential, self-hosted model, copilot SDK service, chat app with copilot, copilot-sdk-service template, azd init copilot, CopilotClient, createSession, sendAndWait, GitHub Models API. DO NOT USE FOR: using Copilot (not building with it), Copilot Extensions, Azure Functions without Copilot, general web apps without copilot SDK, Foundry agent hosting (use microsoft-foundry skill), agent evaluation (use microsoft-foundry skill).
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill azure-hosted-copilot-sdk100
Does it follow best practices?
Validation for skill structure
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 excels across all dimensions. It provides specific actions, comprehensive trigger terms covering both natural language and technical terminology, explicit use/don't-use guidance, and clear boundaries with other skills. The DO NOT USE FOR section with skill cross-references is particularly effective for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Build and deploy GitHub Copilot SDK apps to Azure', 'scaffold copilot project', 'deploy copilot app', 'host on azure'. Also mentions specific technical components like 'CopilotClient', 'createSession', 'sendAndWait'. | 3 / 3 |
Completeness | Clearly answers both what ('Build and deploy GitHub Copilot SDK apps to Azure') and when with explicit 'USE FOR:' and 'DO NOT USE FOR:' clauses that provide comprehensive trigger guidance and boundary conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'build copilot app', 'create copilot app', 'copilot SDK', 'bring your own model', 'BYOM', 'use my own model', 'chat app with copilot'. Includes both casual phrases and technical terms like '@github/copilot-sdk' and 'DefaultAzureCredential'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit exclusions ('DO NOT USE FOR: Copilot Extensions, Azure Functions without Copilot, Foundry agent hosting') and cross-references to related skills ('use microsoft-foundry skill'). Clear niche focused specifically on Copilot SDK development. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency through routing tables, clear actionable commands, and well-organized progressive disclosure. The workflow is clear with explicit step sequencing and appropriate delegation to reference files for detailed implementation guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for routing decisions, minimal prose, and delegates details to reference files. Every token serves a purpose with no explanation of concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete, executable commands (azd init with specific template), clear routing tables for decision-making, and specific configuration patterns. The scaffold command is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear numbered steps with explicit routing table at the start. Step 4 explicitly sequences deployment through three skills in order. The workflow handles multiple entry points cleanly with clear branching. | 3 / 3 |
Progressive Disclosure | Excellent structure with concise overview and well-signaled one-level-deep references to detailed docs (copilot-sdk.md, deploy-existing.md, azure-model-config.md). Appropriately delegates complexity to reference files. | 3 / 3 |
Total | 12 / 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.
- 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.