CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-hosted-copilot-sdk

Build, deploy, and modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github/copilot-sdk or CopilotClient in package.json. PREFER OVER azure-prepare when copilot-sdk markers detected. WHEN: copilot SDK, @github/copilot-sdk, copilot-powered app, build copilot app, prepare copilot app, add feature to copilot app, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: deploying already-prepared copilot-sdk apps (use azure-deploy), general web apps without copilot SDK (use azure-prepare), Copilot Extensions, Foundry agents (use microsoft-foundry).

66

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured orchestration overview that routes to five real one-level-deep references, but it leans on some redundant routing warnings and defers the key executable code to those references, leaving in-body actionability and explicit validation checkpoints incomplete.

Suggestions

Consolidate the three repeated routing warnings in the Codebase Detection section into a single statement to reduce token overhead and improve conciseness.

Add one concrete, copy-paste BYOM code snippet (DefaultAzureCredential + bearerToken provider config) inline so the body is executable without opening the reference.

Insert an explicit validation checkpoint in Step 4 (e.g., confirm `docker info` succeeds and azure-validate passes before azure-deploy) to add an error-recovery feedback loop for the risky deploy operation.

DimensionReasoningScore

Conciseness

Mostly efficient with tables and short steps, but the Codebase Detection section restates the routing rule three times ("MANDATORY FIRST CHECK", the CRITICAL block, the "ANY build... MUST route" warning), which could be tightened.

2 / 3

Actionability

Provides the executable `azd init --template azure-samples/copilot-sdk-service` command and specific config params, but the full BYOM code example and implementation details are deferred to references, leaving the body itself incomplete for direct execution.

2 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1 Route through Step 4 Deploy with azure-validate in the chain) and the detection procedure is a numbered checklist, but in-body validation checkpoints and error-recovery feedback loops for the risky scaffold/deploy operations are largely delegated out rather than stated.

2 / 3

Progressive Disclosure

Clear orchestration overview with well-signaled, one-level-deep references (copilot-sdk.md, deploy-existing.md, existing-project-integration.md, auth-best-practices.md, azure-model-config.md) — all real files, each linked inline with context, content appropriately split into detail files.

3 / 3

Total

9

/

12

Passed

Description

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.

The description is specific, trigger-rich, and explicitly disambiguated from sibling skills, covering both what it does and when to use it. It is dense but every clause earns its place and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Build, deploy, and modify GitHub Copilot SDK apps on Azure" — naming specific operations rather than vague language; uses third person so no voice penalty applies.

3 / 3

Completeness

Explicitly answers what ("Build, deploy, and modify...") and when via the "WHEN:" clause, "MANDATORY when codebase contains..." triggers, and a "DO NOT USE FOR" exclusion list.

3 / 3

Trigger Term Quality

Good coverage of natural user terms including "build copilot app", "prepare copilot app", "modify copilot app", "BYOM", "bring your own model", plus code markers CopilotClient/createSession/sendAndWait that a developer would name.

3 / 3

Distinctiveness Conflict Risk

Clear niche (Copilot SDK on Azure) with explicit disambiguation against azure-deploy, azure-prepare, and microsoft-foundry via the "DO NOT USE FOR" clause, making wrong-skill triggering unlikely.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/azure-skills
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.