Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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.
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 could benefit from additional natural trigger terms users might use when seeking this skill.
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', 'containerized agent', 'deploy agent', or 'agent hosting'.
| 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
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with complete, executable code examples and useful reference tables, but suffers from significant verbosity and redundancy—the same patterns are repeated 3-4 times across sections. The workflow lacks validation checkpoints (e.g., checking agent state after creation, verifying the container is running) which is important for cloud resource provisioning. The content would benefit greatly from deduplication and splitting reference material into separate files.
Suggestions
Eliminate redundancy by keeping one canonical code example (the complete example) and removing duplicate authentication and definition snippets from earlier sections, or reduce earlier sections to minimal fragments that reference the complete example.
Add a validation step after agent creation (e.g., polling agent.state until it reaches 'Running' or handling failure states) to create a proper feedback loop for this cloud provisioning workflow.
Move the parameter reference table, tools configuration details, and async pattern into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the core workflow and links.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant redundancy throughout: the authentication section repeats in the core workflow and complete example, the ImageBasedHostedAgentDefinition parameters are shown in code then repeated in a table, resource allocation is explained twice, tools configuration shows three near-identical examples, and the complete example is essentially a copy of the core workflow. The 'When to Use' and 'Limitations' sections are generic boilerplate adding no value. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready Python code with specific imports, concrete parameter values, and complete examples for both sync and async patterns. The parameter tables, error table, and tool configuration examples give precise, actionable guidance. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced (imports → create → list → delete), but there are no validation checkpoints—no verification that the agent actually started successfully, no feedback loop for checking agent state after creation, and no guidance on handling the common errors inline within the workflow steps. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but it's monolithic—over 200 lines of inline content that could benefit from splitting detailed reference material (parameter tables, tool configs, async patterns) into separate files. Reference links are provided but only to external docs, not to any companion skill files. | 2 / 3 |
Total | 8 / 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 | |
431bfad
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.