CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azd-deployment

Prepare and verify authorized Azure Container Apps deployments with azd. Use for azure.yaml, Bicep, remote builds, managed identity and post-deploy checks.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured, highly actionable deployment reference with excellent authorization and post-deploy verification discipline. The main weaknesses are verbose caution prose and an entirely inline layout with no bundle files for a document of this length.

Suggestions

Tighten the prose in "Deployment Repeatability" and "Container App Service Discovery" to direct instructions, and deduplicate the "azd show" entry between the environment-management and debugging command lists.

Move the full azure.yaml-with-hooks example and the detailed RBAC hook into a references/ file, keeping only the minimal example and key options inline in SKILL.md.

Consider merging "Local Resources" into "Official command references" since both make the same point about external validation and missing bundle files.

DimensionReasoningScore

Conciseness

The body is mostly efficient azd-specific content, but the hedging prose in "Deployment Repeatability" and "Container App Service Discovery", plus duplication (e.g., "azd show" appears in both the environment-management and debugging command lists), could be tightened without losing information.

3 / 5

Actionability

Mostly executable guidance: copy-paste-ready azure.yaml, main.parameters.json, Bicep outputs, azd commands, and a fail-fast RBAC hook. The nginx block and resourceToken example are deliberately schematic, which is explicitly justified, keeping this just below fully copy-paste-ready.

4 / 5

Workflow Clarity

The lifecycle sequence (authorize/prepare -> init/env -> configure -> deploy -> verify) is coherent, and the six-step Post-Deployment Verification checklist has explicit validation checkpoints, failure handling (stop rollout, report, use reviewed rollback plan), and instructions to record observed vs. assumed state.

5 / 5

Progressive Disclosure

Good section structure with an explicit "Local Resources" note clarifying that nothing is bundled and pointing to official references. All ~290 lines live inline in SKILL.md; the full azure.yaml example and detailed verification checklist could plausibly be split into reference files, which keeps this below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong, third-person description that clearly states what the skill does and when to use it, with concrete azd-specific trigger terms. Its only weaknesses are broad action verbs and a few missing synonyms such as "Azure Developer CLI".

DimensionReasoningScore

Specificity

"Prepare and verify authorized Azure Container Apps deployments with azd" names the domain and actions, and the trigger list covers concrete artifacts (azure.yaml, Bicep, remote builds, managed identity, post-deploy checks), but the action verbs themselves are limited to prepare/verify rather than multiple distinct concrete operations.

4 / 5

Completeness

The what ("Prepare and verify authorized Azure Container Apps deployments with azd") and the when ("Use for azure.yaml, Bicep, remote builds, managed identity and post-deploy checks") are both explicitly stated with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ("azd", "azure.yaml", "Bicep", "managed identity", "post-deploy checks"), but common variations like "Azure Developer CLI", "provision", or "deploy to Azure" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The azd/azure.yaml/Container Apps niche is clear and mostly distinct, but terms like "Bicep" and "managed identity" alone could overlap with general Azure infrastructure skills, leaving minor conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

boisenoise/skills-collections

Path

skills/antigravity-azd-deployment/SKILL.md

Revision

7bf2279

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill