azd-deployment

Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-azd-deployment/SKILL.md

The canonical home for this skill is azd-deployment in sickn33/antigravity-awesome-skills

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with abundant executable examples and a clear quick-start, but it over-explains some known concepts and, because it covers destructive/batch deployment operations without explicit validation checkpoints, workflow clarity is capped at 3. Referenced bundle files are missing and significant detail is inlined, limiting progressive disclosure.

Suggestions

Add explicit validation checkpoints to the deployment workflow (e.g. after `azd provision`, verify resources; after `azd deploy`, curl the service URI), with a fix-and-retry feedback loop for failed deploys.

Create the referenced files (references/bicep-patterns.md, references/troubleshooting.md, references/azure-yaml-schema.md) or remove the dangling references, and move the full azure.yaml and long hook scripts into them to keep SKILL.md as an overview.

Trim explanations of concepts Claude already knows (e.g. why Bicep is declarative, ACR layer reuse) and keep only the azd-specific guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight tables and code blocks, but the body explains some concepts Claude already knows (e.g. 'Bicep is declarative - Resources reconcile to desired state', 'ACR reuses layers') and the custom-domain hook example is long; it could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste ready bash, yaml, json, bicep, and nginx snippets covering the common cases (init, env, deploy, hooks, RBAC, parameters, service discovery).	5 / 5
Workflow Clarity	Quick Start gives a sequence (auth login -> init -> env new -> up) and there are 'Critical Reminders', but a full provision/deploy/RBAC workflow involving destructive batch operations lacks explicit validation checkpoints or error-recovery feedback loops, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	The body references references/bicep-patterns.md, references/troubleshooting.md, and references/azure-yaml-schema.md, but those referenced files do not exist in the bundle, and large amounts of configuration detail (full azure.yaml, hook scripts, Bicep modules) are inlined rather than split out; structure is present but references are not clearly backed and bulk content is inline.	3 / 5
	Total	14 / 20 Passed

Description

56%Weight 40%Scale 1-5

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 specific and narrowly scoped to Azure Container Apps deployment, with clear concrete capabilities. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3 and weakens trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when deploying containerized apps to Azure Container Apps, or when the user mentions azd, Azure Container Apps, or container deployment to Azure.'

Include natural user-facing synonyms and the tool name 'azd' in the description so it surfaces on natural-language requests.

Avoid first-rate over-claims: 'idempotent infrastructure' is a feature; lead with the action ('Deploy ... to Azure Container Apps') which it already does well.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('remote builds', 'managed identity', 'idempotent infrastructure') for the containerized frontend+backend to Azure Container Apps domain, though these are somewhat high-level feature labels rather than enumerated operational steps.	4 / 5
Completeness	Clearly states what the skill does, but contains no 'Use when...' clause or explicit trigger guidance; per rubric guidelines, a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes domain terms like 'Azure Container Apps', 'remote builds', 'managed identity' but lacks the natural trigger phrasing a user would say (e.g. 'deploy to Azure', 'container app'), offering only technical jargon without common synonyms.	3 / 5
Distinctiveness Conflict Risk	The Azure Container Apps + azd niche is specific and distinct from most other skills, with only minor overlap risk against generic Azure deployment or Terraform skills.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-azd-deployment/SKILL.md
Commit: 19c310e

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.