azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
75
70%
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-azd-deployment/SKILL.mdQuality
Discovery
67%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 strong on specificity and distinctiveness, clearly identifying a narrow Azure Container Apps deployment use case with concrete technical details. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing common user-facing trigger term variations (e.g., 'ACA', 'Docker', 'Azure deployment').
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to deploy containers to Azure, mentions Azure Container Apps, ACA, or needs to set up containerized web applications on Azure.'
Include common trigger term variations like 'ACA', 'Docker', 'Azure deployment', 'container deployment', or 'cloud deployment to Azure' to improve matching with natural user language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Deploy containerized frontend + backend applications', 'remote builds', 'managed identity', 'idempotent infrastructure'. These are concrete, specific capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (deploy containerized apps to Azure Container Apps with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'Azure Container Apps', 'containerized', 'deploy', 'managed identity', and 'frontend + backend'. However, it misses common user variations like 'ACA', 'container apps', 'Azure deployment', 'Docker', or '.bicep'. Users might say 'deploy to Azure' or 'set up containers on Azure' which aren't well covered. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Azure Container Apps deployment with containerized frontend + backend. The combination of Azure Container Apps, remote builds, managed identity, and idempotent infrastructure creates a highly distinct profile unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent structure and concrete, executable examples covering the full azd deployment workflow. Its main weaknesses are moderate verbosity (some sections could be tightened, particularly the full azure.yaml example with placeholder hooks) and the lack of explicit validation/verification steps in the deployment workflow. The progressive disclosure and reference file structure are well done.
Suggestions
Add explicit validation checkpoints to the deployment workflow, e.g., 'After `azd up`, verify with `azd show` and check service URIs are accessible' with error recovery steps if deployment fails.
Trim the full azure.yaml example—the placeholder echo hooks don't add value; either show real hook commands or remove them and reference the hooks section separately.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some sections that could be tightened—the full azure.yaml configuration with placeholder echo statements adds bulk, and the hooks examples with comments like 'echo Before provisioning...' don't add real value. The 'Key azure.yaml Options' table partially repeats what's shown in the code examples above it. | 2 / 3 |
Actionability | The skill provides fully executable code throughout—real bash commands, complete Bicep snippets, valid YAML configurations, and concrete nginx config. Commands are copy-paste ready with specific flags and options, and the common commands section serves as a practical reference. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequence, and the environment variable flow is well-structured with three levels. However, there are no explicit validation checkpoints in the deployment workflow—no 'verify the deployment succeeded' step, no error recovery guidance after 'azd up' fails, and the idempotent deployment section describes behavior rather than providing a validated workflow with feedback loops. | 2 / 3 |
Progressive Disclosure | The skill has a clear Quick Start overview, well-organized sections with increasing detail, and explicit one-level-deep references to external files (bicep-patterns.md, troubleshooting.md, azure-yaml-schema.md). Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- boisenoise/skills-collections
- Commit
f1697b6
- 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.