microsoft-foundry
Deploy, evaluate, and manage Foundry agents end-to-end: Docker build, ACR push, hosted/prompt agent create, container start, batch eval, prompt optimization, agent.yaml, dataset curation from traces. USE FOR: deploy agent to Foundry, hosted agent, create agent, invoke agent, evaluate agent, run batch eval, optimize prompt, deploy model, Foundry project, RBAC, role assignment, permissions, quota, capacity, region, troubleshoot agent, deployment failure, create dataset from traces, dataset versioning, eval trending, create AI Services, Cognitive Services, create Foundry resource, provision resource, knowledge index, agent monitoring, customize deployment, onboard, availability. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare).
Install with Tessl CLI
npx tessl i github:microsoft/github-copilot-for-azure --skill microsoft-foundry94
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 a well-crafted skill description that excels across all dimensions. It provides comprehensive specific actions, extensive natural trigger terms in a clear 'USE FOR' section, and explicitly delineates boundaries with other Azure-related skills. The description effectively enables Claude to select this skill precisely when Foundry agent work is needed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Docker build, ACR push, hosted/prompt agent create, container start, batch eval, prompt optimization, agent.yaml, dataset curation from traces' - these are detailed, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (deploy, evaluate, manage Foundry agents with specific actions) AND when (explicit 'USE FOR:' section with comprehensive trigger scenarios, plus 'DO NOT USE FOR:' to clarify boundaries). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'deploy agent', 'create agent', 'evaluate agent', 'run batch eval', 'optimize prompt', 'troubleshoot agent', 'deployment failure', 'create dataset from traces'. Includes both technical terms and common user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly distinguishes itself from related skills with 'DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare)' - clear niche focused on Foundry agents specifically. | 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 that effectively routes users to specialized sub-skills. Its strengths are excellent progressive disclosure, clear workflow sequencing, and token-efficient presentation using tables. The main weakness is limited actionability in the main document itself—it delegates all concrete execution details to sub-skills without providing any quick-start examples.
Suggestions
Add a minimal 'Quick Start' section with one concrete executable example (e.g., a single deploy or invoke command) so users can see immediate value before diving into sub-skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section serves a clear purpose without padding. | 3 / 3 |
Actionability | The skill provides good structural guidance and workflow sequences, but lacks concrete executable code examples. It relies heavily on references to sub-skills rather than providing copy-paste ready commands in the main document. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit ordering (create → deploy → invoke). The 'Agent Development Lifecycle' table maps user intents to ordered workflow steps, and the context resolution section has clear numbered steps with validation logic. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-organized one-level-deep references via the sub-skills table. Each sub-skill is clearly signaled with 'When to Use' guidance, making navigation straightforward. | 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.
- 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.