azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
57
66%
Does it follow best practices?
Impact
—
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 technically specific and clearly identifies a distinct niche around Azure Container Apps deployment. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding common user trigger terms and variations would also improve discoverability.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to deploy applications to Azure Container Apps, mentions ACA, or needs containerized Azure deployments.'
Include common keyword variations users might say, such as 'ACA', 'Docker', 'Azure deployment', 'container apps', or 'Bicep/ARM templates'.
| 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 per the rubric caps completeness at 2. | 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'/'ARM templates' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Azure Container Apps deployment with containerized frontend+backend apps. The combination of Azure Container Apps, remote builds, managed identity, and idempotent infrastructure makes this highly distinctive and unlikely to conflict with generic deployment or Azure skills. | 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 is a solid, actionable skill with concrete executable examples covering the full azd deployment lifecycle. Its main weaknesses are the lack of explicit validation/verification checkpoints in the deployment workflow and some content bloat from placeholder hook examples and boilerplate sections. The referenced files don't exist in the bundle, undermining the progressive disclosure structure.
Suggestions
Add explicit validation checkpoints after key steps (e.g., 'Verify deployment: azd show' after 'azd up', check container app status with az containerapp show)
Move the full azure.yaml configuration example and the hooks examples into a referenced file like references/azure-yaml-schema.md to reduce the main file length
Remove the boilerplate 'When to Use' and 'Limitations' sections—they add no actionable information and waste tokens
Provide the referenced bundle files (references/bicep-patterns.md, references/troubleshooting.md, references/azure-yaml-schema.md) or remove the references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like the boilerplate 'When to Use' and 'Limitations' sections that add no value, and the full azure.yaml example with placeholder echo statements is somewhat padded. The hooks examples with 'echo' placeholders could be tighter. | 2 / 3 |
Actionability | Provides fully executable code throughout: real bash commands, complete Bicep snippets, valid YAML configurations, concrete nginx config, and specific az CLI commands with actual role names and flags. Everything is copy-paste ready. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequence, and the environment variable flow is well-explained with a three-level hierarchy. However, there are no explicit validation checkpoints—no 'verify the deployment succeeded' step, no error recovery guidance after 'azd up' fails, and the idempotent deployment section lacks a verify-then-proceed pattern. | 2 / 3 |
Progressive Disclosure | References to references/bicep-patterns.md, references/troubleshooting.md, and references/azure-yaml-schema.md are well-signaled and one-level deep, which is good structure. However, no bundle files are provided, so these references point to non-existent files. The main content is also quite long (~200+ lines) with some sections like the full azure.yaml example that could be moved to reference files. | 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 | |
- Repository
- boisenoise/skills-collections
- Commit
8ac11ab
- 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.