azd-deployment

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 concrete commands and code, but it is verbose, lacks validation checkpoints in the deployment workflow, and references bundle files that are not actually present.

Suggestions

Add an explicit validation/verification step after `azd up` (e.g., check `azd show` / container app status) with a fix-and-retry loop for the destructive redeploy case.

Create the referenced bundle files (bicep-patterns.md, troubleshooting.md, azure-yaml-schema.md) or remove the broken Reference Files pointers.

Trim the full azure.yaml and hooks examples, moving exhaustive variants into a reference file to reduce inline token load.

Dimension	Reasoning	Score
Conciseness	The ~300-line body is mostly actionable code and config rather than concepts Claude already knows, but the full azure.yaml, hooks examples, and several sections are verbose and could be tightened.	2 / 3
Actionability	Provides copy-paste-ready, executable guidance throughout — concrete azd commands, complete azure.yaml configs, Bicep snippets, and real shell hooks with specific flags and resource IDs.	3 / 3
Workflow Clarity	The Quick Start sequence (auth login -> init -> env new -> up) is present, but this deployment workflow is potentially destructive (custom domains can be lost on redeploy) and lacks explicit validation checkpoints or error-recovery feedback loops, capping it at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned with a Reference Files section, but the referenced files (references/bicep-patterns.md, troubleshooting.md, azure-yaml-schema.md) do not exist, so navigation is broken, and much detail-heavy content remains inline.	2 / 3
	Total	9 / 12 Passed

Description

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 specific and occupies a distinct niche, but it omits any explicit "when to use" trigger guidance, which is required for full completeness and natural trigger-term coverage.

Suggestions

Add a "Use when..." clause naming natural user phrasings, e.g. "Use when deploying a containerized frontend and backend to Azure Container Apps with azd."

Include more common conversational trigger terms (e.g. "deploy to Azure", "azd up", "container app deployment") alongside the product jargon.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure" — covering deploy, remote builds, managed identity, and idempotent infra.	3 / 3
Completeness	Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Includes relevant product terms like "Azure Container Apps" and "deploy" that a user might say, but is dominated by technical jargon and lacks common natural phrasings or a usage trigger.	2 / 3
Distinctiveness Conflict Risk	The Azure Container Apps / azd / containerized frontend+backend niche is specific and clearly distinguishable, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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
Commit: f36337d

Reviewed: 2 days 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.