azd-deployment

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

Quality

60%

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/azd-deployment/SKILL.md

Quality

Content

53%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.

A code-rich, largely actionable body with strong azure.yaml and Bicep examples, but it is dragged down by dangling references to nonexistent bundle files, inlined detail that belongs in those files, absent validation checkpoints for a risky deploy workflow, and a few filler sections. Fixing the reference files and adding post-deploy verification would lift the two weakest dimensions substantially.

Suggestions

Create the referenced files (references/bicep-patterns.md, references/troubleshooting.md, references/azure-yaml-schema.md) or remove the Reference Files section — currently all three point to nonexistent files.

Move the full azure.yaml configuration and Bicep pattern details into the reference files, keeping only a minimal example inline in SKILL.md.

Add validation checkpoints to the deployment workflow (e.g. verify with 'azd show' / check container app status after 'azd up', and what to do on failure) to lift workflow clarity above the cap.

Trim filler sections ('When to Use', 'Why azd up is Idempotent' prose) that restate what Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-forward content, but it includes unnecessary explanation Claude already knows ('Bicep is declarative - Resources reconcile to desired state') and filler sections like 'When to Use' ('This skill is applicable to execute the workflow or actions described in the overview').	3 / 5
Actionability	Quick Start commands, complete azure.yaml configurations, and copy-paste azd/az commands make most guidance executable; minor gaps include the custom-domains hook that only echoes the saved file instead of restoring it, and fragmentary snippets like 'customDomains: empty(customDomainsParam) ? null : customDomainsParam' and the nginx location block.	4 / 5
Workflow Clarity	The Quick Start sequence (auth login, init, env new, up) is coherent, but there are no validation checkpoints or error-recovery loops for a risky production-infrastructure deployment, capping workflow clarity at 3 per the rubric guidelines.	3 / 5
Progressive Disclosure	The body cites references/bicep-patterns.md, references/troubleshooting.md, and references/azure-yaml-schema.md, but no references/ directory or bundle files exist, so all three references are dangling; meanwhile ~300 lines of azure.yaml schema detail and Bicep patterns are inlined in SKILL.md.	2 / 5
	Total	12 / 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.

A specific, well-scoped description that clearly states what the skill does and names concrete Azure technologies. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness, and it lacks common synonyms like 'azd' or 'ACA'.

Suggestions

Append an explicit trigger clause, e.g. 'Use when deploying containerized apps to Azure with azd, Azure Container Apps, or when the user mentions ACA or azd up.'

Add natural synonym triggers users would say: 'azd', 'Azure Developer CLI', 'ACA', 'azd up'.

Optionally mention one more capability (e.g. environment management or RBAC setup) to round out coverage for a top specificity score.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ('Azure Container Apps') and several specific capabilities ('remote builds, managed identity, and idempotent infrastructure'), but coverage is deploy-only and the trailing items are features rather than distinct actions, so it falls just short of comprehensive.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural phrases like 'deploy containerized frontend + backend applications', 'Azure Container Apps', and 'managed identity' are present, but common user variations such as 'azd', 'Azure Developer CLI', or 'ACA' are missing.	4 / 5
Distinctiveness Conflict Risk	'Azure Container Apps' carves out a clear niche with distinct technical triggers; only minor overlap risk with other Azure deployment or container-orchestration 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: sickn33/agentic-awesome-skills
Path: skills/azd-deployment/SKILL.md
Commit: 7b534bc

Reviewed: 5 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.