azd-deployment

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

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azd-deployment/SKILL.md

Quality

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 strong on specificity and distinctiveness, clearly identifying a narrow deployment scenario with concrete technical details. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing common user-facing trigger term variations (e.g., 'ACA', 'Docker', 'deploy to Azure'). Adding trigger guidance and broader keyword coverage would make this description excellent.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to deploy frontend and/or backend containers to Azure, mentions Azure Container Apps, or asks about cloud container deployment.'

Include common trigger term variations such as 'ACA', 'Docker', 'deploy to Azure', 'cloud deployment', '.bicep', or 'container orchestration' to improve discoverability.

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 per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes good technical terms like 'Azure Container Apps', 'containerized', 'managed identity', 'remote builds', but misses common user variations like 'ACA', 'deploy to Azure', 'container app', 'Docker', or 'cloud deployment'. Users might not always use the exact phrase 'Azure Container Apps'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche: Azure Container Apps deployment with frontend + backend, managed identity, and remote builds. This is unlikely to conflict with other skills due to the highly specific platform and deployment pattern.	3 / 3
	Total	10 / 12 Passed

Implementation

64%

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 concrete code examples covering the full azd deployment lifecycle. Its main weaknesses are the lack of validation/verification checkpoints in the deployment workflow and some content bloat from boilerplate sections and inline detail that could be offloaded to reference files. The referenced supporting files don't exist in the bundle, undermining the progressive disclosure structure.

Suggestions

Add explicit validation checkpoints to the deployment workflow, e.g., 'Verify deployment: azd show' after azd up, and 'Check build logs: az acr task logs' if deployment fails, with a retry loop.

Remove the boilerplate 'When to Use' and 'Limitations' sections — they add no actionable information and waste tokens.

Create the referenced bundle files (references/bicep-patterns.md, references/troubleshooting.md, references/azure-yaml-schema.md) and move detailed Bicep module examples and the full azure.yaml configuration into them to reduce SKILL.md size.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of tables and code blocks, but includes some unnecessary sections like the boilerplate 'When to Use' and 'Limitations' sections that add no value, and the hooks examples with placeholder echo statements add bulk without substance. The full azure.yaml example could be tighter.	2 / 3
Actionability	Provides fully executable code blocks throughout — real Bicep modules, concrete azure.yaml configurations, specific CLI commands, and copy-paste-ready hook scripts with actual az CLI calls. The parameter injection patterns and RBAC examples are immediately usable.	3 / 3
Workflow Clarity	The Quick Start provides a clear sequence, and the idempotent deployment section explains the flow well. However, there are no explicit validation checkpoints — no 'verify the deployment succeeded' step, no 'check ACR build logs if deploy fails' feedback loop, and the custom domain preservation hook lacks a proper restore step (just echoes saved domains).	2 / 3
Progressive Disclosure	References to references/bicep-patterns.md, references/troubleshooting.md, and references/azure-yaml-schema.md are well-signaled and one-level deep, which is good structure. However, no bundle files are provided, so these references point to non-existent files. The main content also includes substantial inline detail (full azure.yaml, Bicep patterns, service discovery) that could be split into reference files.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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: 76aea27

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