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/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 trigger guidance and a few more natural user terms would elevate this from good to excellent.
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 user-facing synonyms and abbreviations such as 'ACA', 'Docker', 'Azure deployment', 'container hosting' to improve trigger term coverage.
| 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 distinct profile unlikely to conflict with generic deployment or other cloud provider 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 concrete examples covering the full azd deployment lifecycle. Its main weaknesses are missing validation checkpoints in the deployment workflow (e.g., no verification steps between provision and deploy) and some unnecessary verbosity in sections like 'Why azd up is Idempotent' and the boilerplate Limitations section. The progressive disclosure and reference structure are well done.
Suggestions
Add explicit validation checkpoints to the deployment workflow, e.g., 'Verify provision succeeded: azd show' before proceeding to deploy, and 'Verify deployment: az containerapp show ...' after deploy.
Remove the boilerplate 'When to Use' and 'Limitations' sections—they add no actionable information and waste tokens.
Complete the custom domain preservation hook with an actual restore command instead of just echoing the saved JSON.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of code blocks and tables, but includes some unnecessary verbosity like the full hooks example with placeholder echo statements, the 'When to Use' and 'Limitations' boilerplate sections that add no value, and some explanatory text that could be trimmed (e.g., 'Why azd up is Idempotent' section explains concepts Claude already understands). | 2 / 3 |
Actionability | Provides fully executable code throughout—real Bicep modules, complete azure.yaml configurations, concrete CLI commands, and specific patterns for parameter injection, RBAC assignment, and service discovery. Everything is copy-paste ready with real syntax. | 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 provision succeeded before deploying' step, no 'check container app is running' after deploy, and the custom domain preservation hook lacks a proper restore step (just echoes the saved domains). | 2 / 3 |
Progressive Disclosure | Well-structured with a clear Quick Start, logically organized sections that build in complexity, and explicit one-level-deep references to external files (bicep-patterns.md, troubleshooting.md, azure-yaml-schema.md). Content is appropriately split between overview and reference material. | 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
- sickn33/antigravity-awesome-skills
- Commit
76cbde3
- 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.