azure-hosted-copilot-sdk
Build and deploy GitHub Copilot SDK applications to Azure with flexible model configuration.
Works with
0
total installs
0
this week
582
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
582
stars
What it does
Three scaffolding paths: create new greenfield projects, add SDK services to existing repos, or deploy existing SDK apps with Azure infrastructure
Supports three model configurations: GitHub's default models, specific GitHub models via discovery, or bring-your-own-model (BYOM) on Azure with DefaultAzureCredential authentication
Includes complete templates with Express/TypeScript API, React/Vi
Installation Guide
How to use azure-hosted-copilot-sdk on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
azure-hosted-copilot-sdk
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches azure-hosted-copilot-sdk from microsoft/azure-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate azure-hosted-copilot-sdk. Access via /azure-hosted-copilot-sdk in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
GitHub Copilot SDK on Azure
Codebase Detection — MANDATORY FIRST CHECK
Before routing to azure-prepare for ANY prompts involving an existing codebase, scan the workspace for Copilot SDK markers. If ANY marker is found, this skill MUST be used instead of azure-prepare:
| Marker | Where to check |
|---|---|
@github/copilot-sdk |
package.json dependencies |
copilot-sdk |
package.json name or dependencies |
CopilotClient |
Source files (.ts, .js) |
createSession + sendAndWait |
Source files (.ts, .js) |
⚠️ Warning: ANY prompt targeting an existing codebase — deploy, modify, add feature, update, enhance — MUST trigger this skill when codebase contains
@github/copilot-sdk, even if the prompt does not mention "copilot". Do NOT fall through to azure-prepare.
Step 1: Route
| User wants | Action |
|---|---|
| Build new (empty project) | Step 2A (scaffold) |
| Add new SDK service to existing repo | Step 2B (scaffold alongside) |
| Deploy existing SDK app to Azure | Step 2C (add infra to existing SDK app) |
| Modify/add features to existing SDK app | Use codebase context + SDK references to implement |
| Add SDK to existing app code | Integrate SDK |
| Use Azure/own model | Step 3 (BYOM config) |
Step 2A: Scaffold New (Greenfield)
azd init --template azure-samples/copilot-sdk-service
Template includes API (Express/TS) + Web UI (React/Vite) + infra (Bicep) + Dockerfiles + token scripts — do NOT recreate. See SDK ref.
Step 2B: Add SDK Service to Existing Repo
User has existing code and wants a new Copilot SDK service alongside it. Scaffold template to a temp dir, copy the API service + infra into the user's repo, adapt azure.yaml to include both existing and new services. See deploy existing ref.
Step 2C: Deploy Existing SDK App
User already has a working Copilot SDK app and needs Azure infra. See deploy existing ref.
Step 3: Model Configuration
Three model paths (layers on top of 2A/2B):
| Path | Config |
|---|---|
| GitHub default | No model param — SDK picks default |
| GitHub specific | model: "<name>" — use listModels() to discover |
| Azure BYOM | model + provider with bearerToken via DefaultAzureCredential |
⚠️ BYOM Auth — MANDATORY: Azure BYOM configurations MUST use
DefaultAzureCredential(local dev) orManagedIdentityCredential(production) to obtain abearerToken. The ONLY supported auth pattern isbearerTokenin the provider config. See auth-best-practices.md for the credential pattern and model config ref for the full BYOM code example.
See model config ref.
Step 4: Deploy
Invoke azure-prepare (skip its Step 0 routing — scaffolding is done) → azure-validate → azure-deploy in order.
Rules
- Read
AGENTS.mdin user's repo before changes - Docker required (
docker info) - BYOM auth: ONLY
bearerTokenviaDefaultAzureCredentialorManagedIdentityCredential— no other auth pattern is supported
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
azure-cost-optimization
1microsoft/azure-skills
azure-cloud-migrate
1microsoft/azure-skills
microsoft-foundry
1microsoft/azure-skills
azure-storage
2microsoft/GitHub-Copilot-for-Azure
microsoft-foundry
1microsoft/GitHub-Copilot-for-Azure
suggest-awesome-github-copilot-skills
4github/awesome-copilot
Reviews
- CCharlotte Menon★★★★★Dec 12, 2024
azure-hosted-copilot-sdk is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- DDiego Yang★★★★★Dec 12, 2024
azure-hosted-copilot-sdk has been reliable in day-to-day use. Documentation quality is above average for community skills.
- GGanesh Mohane★★★★★Dec 4, 2024
Keeps context tight: azure-hosted-copilot-sdk is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSakshi Patil★★★★★Nov 23, 2024
azure-hosted-copilot-sdk has been reliable in day-to-day use. Documentation quality is above average for community skills.
- LLi Farah★★★★★Nov 19, 2024
I recommend azure-hosted-copilot-sdk for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- YYash Thakker★★★★★Nov 3, 2024
I recommend azure-hosted-copilot-sdk for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- CCamila Brown★★★★★Nov 3, 2024
Solid pick for teams standardizing on skills: azure-hosted-copilot-sdk is focused, and the summary matches what you get after install.
- CCamila Thomas★★★★★Nov 3, 2024
Keeps context tight: azure-hosted-copilot-sdk is the kind of skill you can hand to a new teammate without a long onboarding doc.
- DDhruvi Jain★★★★★Oct 22, 2024
Useful defaults in azure-hosted-copilot-sdk — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- LLi Garcia★★★★★Oct 22, 2024
azure-hosted-copilot-sdk has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 39
Discussion
Comments — not star reviews- No comments yet — start the thread.