azd-deployment

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

Quality

65%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azd-deployment/SKILL.md

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

Quality

Content

65%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 concrete commands and configs and is reasonably concise, but the deployment workflow lacks validation checkpoints and the progressive-disclosure structure is undermined by broken reference files and inlined bulk content.

Suggestions

Add explicit validation/verification checkpoints to the deployment workflow — e.g. run `azd show` or `az containerapp show` after `azd up` to confirm the app is healthy before running post-provision RBAC hooks.

Create the referenced bundle files (references/bicep-patterns.md, references/troubleshooting.md, references/azure-yaml-schema.md) or remove the broken references, since the Reference Files section currently points to files that do not exist.

Move the inlined bulk content (full azure.yaml schema and Bicep module patterns) into the reference files so SKILL.md stays a lean overview and progressive disclosure improves.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code and config with little padding of concepts Claude doesn't need, but the 'Why azd up is Idempotent' bullets (Bicep is declarative, ACR reuses layers) and the options table that duplicates the full azure.yaml example are minor over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready azd commands, azure.yaml configs, Bicep snippets, and hook scripts cover the common cases, but some hook scripts reference undefined variables ($FRONTEND_NAME, $RG, $OPENAI_RESOURCE_ID) and several Bicep snippets are partial without surrounding context, leaving minor gaps.	4 / 5
Workflow Clarity	The Quick Start gives a clear sequence (auth login → init → env new → up), but this destructive provisioning/deployment workflow has no validation or verification checkpoints, so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	There is reasonable section structure and a clearly signaled Reference Files section, but the referenced files (references/bicep-patterns.md, troubleshooting.md, azure-yaml-schema.md) do not exist, and bulk content that belongs in those files (full azure.yaml schema, Bicep module patterns) is inlined, leaving it at 'some structure but could be better organized'.	3 / 5
	Total	14 / 20 Passed

Description

66%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 distinct, clearly conveying what the skill does for Azure Container Apps, but it omits any 'Use when...' trigger guidance, which caps completeness and slightly weakens distinctiveness and trigger-term coverage.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when deploying containerized apps to Azure Container Apps, authoring azure.yaml, or configuring managed identity and idempotent Bicep infrastructure.'

Include the natural trigger terms 'azd' and 'Azure Developer CLI' in the description so users who say 'azd deploy' or 'azd init' will match it.

Add common synonyms/abbreviations like 'ACA' to broaden trigger-term coverage toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure Container Apps') and several concrete capabilities — 'remote builds', 'managed identity', and 'idempotent infrastructure' — but these read as attributes of one deploy action rather than a comprehensive list of distinct actions, so it sits at 'several specific actions; minor gaps' rather than 5.	4 / 5
Completeness	The 'what' is clear ('Deploy containerized frontend + backend applications to Azure Container Apps...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	'Azure Container Apps' and 'containerized frontend + backend' are natural terms users say, and 'managed identity'/'remote builds' are real trigger phrases, but common synonyms like 'azd', 'Azure Developer CLI', and 'ACA' are absent, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The Azure Container Apps + managed identity + idempotent Bicep niche is distinct and unlikely to fire for unrelated skills, but without an explicit trigger phrase it has minor overlap risk with closely related general Azure deployment skills.	4 / 5
	Total	15 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azd-deployment/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.