Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
52
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/agents-v2-py/SKILL.mdQuality
Discovery
75%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 well-structured with a clear 'Use when' clause and targets a very specific niche (container-based Azure AI Foundry agents), making it distinctive and complete. Its main weakness is that it only describes one high-level action ('build') rather than listing multiple concrete sub-tasks, and the trigger terms are heavily technical without covering common user phrasings.
Suggestions
Add more specific concrete actions beyond 'build', such as 'configure container settings, define environment variables, set up agent endpoints, deploy hosted agents'.
Include additional natural trigger terms users might say, such as 'Docker image agent', 'containerized agent deployment', or 'hosted agent container setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (container-based Foundry Agents) and a key action (build), and mentions a specific SDK class (ImageBasedHostedAgentDefinition), but only describes one action rather than listing multiple concrete capabilities like configuration, deployment, or debugging. | 2 / 3 |
Completeness | Clearly answers both 'what' (build container-based Foundry Agents with Azure AI Projects SDK using ImageBasedHostedAgentDefinition) and 'when' (Use when creating hosted agents with custom container images in Azure AI Foundry), with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'container', 'Foundry Agents', 'Azure AI Projects SDK', 'custom container images', and 'Azure AI Foundry', but these are fairly specialized. Missing common variations users might say like 'Docker', 'deploy agent', 'hosted container', or 'agent deployment'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting container-based hosted agents in Azure AI Foundry with a named SDK class (ImageBasedHostedAgentDefinition). Very unlikely to conflict with other skills due to the precise technology stack and pattern specified. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples for Azure AI hosted agent creation, which is its primary strength. However, it suffers from significant verbosity and redundancy—the same patterns are shown 3-4 times across different sections, and content that Claude already knows (basic best practices, what environment variables are) inflates the token count. The lack of any bundle files means all reference material is crammed into one long document with no progressive disclosure.
Suggestions
Eliminate redundant code examples: merge Authentication, Core Workflow step 2, and Complete Example into a single concise example. The async pattern could be a separate file.
Move the parameter reference table, tools configuration examples, and resource limits table into a separate REFERENCE.md file, keeping only the core creation workflow in SKILL.md.
Add explicit validation checkpoints to the workflow: verify ACR access before creation, check agent.state after creation, and include a retry/error-handling loop.
Remove explanations Claude already knows (e.g., 'Never hardcode secrets', what environment variables are, basic best practices) to reduce token usage by ~30%.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity and redundancy throughout. The Authentication section repeats code shown in the Core Workflow. The Complete Example is essentially a copy of the Core Workflow section. Resource Allocation, Protocol Versions, and Tools Configuration sections repeat patterns already shown. The parameter reference table, while useful, combined with all the repetitive examples makes this far too long. Much of this (what environment variables are, best practices like 'don't hardcode secrets') is knowledge Claude already has. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. Specific imports, method calls, parameter types, and error messages are all provided with clear solutions. The parameter reference table and common errors table are highly actionable. | 3 / 3 |
Workflow Clarity | The Core Workflow section provides a clear sequence (imports → create → list → delete), but there are no validation checkpoints. For an operation involving container deployment and ACR permissions, there should be explicit verification steps (e.g., verify ACR access before creating, check agent state after creation, handle deployment failures). The Common Errors table partially compensates but isn't integrated into the workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no bundle files to offload detail into. The parameter reference table, tools configuration examples, async pattern, complete example, and resource allocation details could all be in separate reference files. Everything is inline in a single long document with no clear navigation hierarchy. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
76aea27
Table of Contents
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.