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, standard agent setup, capability host. 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/azure-skills --skill microsoft-foundry93
Quality
92%
Does it follow best practices?
Impact
93%
2.58xAverage score across 3 eval scenarios
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 a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms in a dedicated 'USE FOR' section, and explicitly delineates boundaries with other skills via 'DO NOT USE FOR'. The description effectively enables Claude to select this skill appropriately from a large skill library.
| 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 and conversational variations. | 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 routing skill that efficiently directs Claude to appropriate sub-skills for Microsoft Foundry operations. Its strengths are excellent organization, clear workflow sequencing, and appropriate use of progressive disclosure. The main weakness is that the skill itself contains no executable code examples, relying entirely on sub-skills for concrete implementation details.
Suggestions
Consider adding one minimal executable example (e.g., a quick-start command or code snippet) to demonstrate the most common operation inline, rather than requiring navigation to a sub-skill for any actionable content.
| 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 with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides good structural guidance with clear routing to sub-skills and workflow tables, but lacks concrete executable code examples. The actionable content is delegated to sub-skills rather than demonstrated inline. | 2 / 3 |
Workflow Clarity | Clear lifecycle workflows are provided (create → deploy → invoke), with an explicit validation section that includes a feedback loop (run → check → diagnose → fix → retry). The intent-to-workflow mapping table makes sequencing unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-organized sub-skill table with one-level-deep references. Each sub-skill has a clear 'When to Use' description and direct link, 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.