Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
80
Quality
70%
Does it follow best practices?
Impact
100%
2.56xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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.
This description effectively communicates a clear niche for Azure AI Foundry container-based agents with explicit 'Use when' guidance. However, it could benefit from listing more concrete actions beyond 'build' and including additional natural trigger terms that users might employ when seeking this functionality.
Suggestions
Add more concrete actions such as 'configure', 'deploy', or 'manage' to better describe the full capability set
Include additional trigger terms users might naturally say, such as 'Docker', 'containerized', 'hosted agent deployment', or 'container image'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (container-based Foundry Agents) and mentions specific SDK class (ImageBasedHostedAgentDefinition), but doesn't list multiple concrete actions beyond 'build' - lacks details like deploy, configure, or manage. | 2 / 3 |
Completeness | Clearly answers both what ('Build container-based Foundry Agents with Azure AI Projects SDK') and when ('Use when creating hosted agents with custom container images in Azure AI Foundry') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'container', 'Foundry Agents', 'Azure AI Projects SDK', 'custom container images', but missing common variations users might say like 'Docker', 'containerized agents', or 'AI Foundry deployment'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting ImageBasedHostedAgentDefinition and container-based agents in Azure AI Foundry - unlikely to conflict with other Azure or agent-related skills due to the precise technical scope. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for creating Azure AI hosted agents with complete, executable code examples and comprehensive parameter documentation. However, it could be more concise by reducing redundancy between sections, and would benefit from explicit validation steps after agent creation to verify successful deployment. The content organization is good but the length suggests some material could be moved to reference files.
Suggestions
Add validation steps after agent creation (e.g., check agent.state, poll until ready, verify container is running) to improve workflow clarity
Move the detailed parameter tables and resource limits to a separate REFERENCE.md file to improve progressive disclosure
Remove the 'Complete Example' section as it largely duplicates the Core Workflow section, or consolidate them into one
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some redundancy (e.g., the complete example largely duplicates earlier sections, and some explanations like 'Best Practice: Never hardcode secrets' state obvious security principles Claude already knows). | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Python code with complete imports, proper async patterns, and specific parameter tables. All code examples are concrete and runnable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (1-4 in Core Workflow) but lacks validation checkpoints for the agent creation process. No feedback loops for handling deployment failures or verifying the agent is running correctly after creation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~250 lines) with detailed API reference tables that could be split into a separate REFERENCE.md. External links are provided but internal file references for advanced topics are missing. | 2 / 3 |
Total | 9 / 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 | |
5c5ae21
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.