New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Azure Deployment

by EmeaAppGbb in EmeaAppGbb/spec2cloud

Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.

MITAuto-check passedTesting & QA

Install Azure Deployment

skills CLI
$ npx skills add EmeaAppGbb/spec2cloud --skill azure-deployment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EmeaAppGbb/spec2cloud azure-deployment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/azure-deployment .claude/skills/azure-deployment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
azure-deployment
GitHub stars
100
Token cost
~1.8k tokens
SKILL.md length
721 words
Files
2 (incl. references)
Skills in repo
38
Repo updated
First seen
Licence
MIT

At a glance

Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.

  • Works in 5 steps: Get deployed URL — azd env get-values →… → Run smoke tests against the live URL → Run the FULL E2E suite against the… → …
  • Deploying to Azure
  • SKILL.md covers Role, Pre-Deployment Checklist, Provision Loop and Deploy Loop, plus 7 more sections
  • Calls npx

What it does

Azure Deployment is an agent skill from EmeaAppGbb/spec2cloud. Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests. Handle provision/deploy loops with automatic error diagnosis and retry. Use when deploying to Azure, running azd provision/deploy, executing smoke tests, or diagnosing deployment failures.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/stack-deployment.md`).

It sits in Testing & QA, covering QA and bug reports and Deployment. It works with Microsoft Azure. The licence is MIT.

When your agent uses it

  • Deploying to Azure
  • Running azd provision/deploy
  • Executing smoke tests
  • Diagnosing deployment failures

Example prompts

  • “/azure-deployment”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Get deployed URL — azd env get-values → extract SERVICE_WEB_ENDPOINT_URL.
  2. Run smoke tests against the live URL
  3. Run the FULL E2E suite against the deployed URL. This is mandatory — every
  4. All tests pass → deployment verified. Update state and finish.
  5. Any test fails → enter Rollback Protocol.

What it can do on your machine

Read from SKILL.md and the folder at commit 8e76618. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Azure Deployment loads about 1.8k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 721 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 721 words, ~1,799 tokens.

Download SKILL.mdSave it as .claude/skills/azure-deployment/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
azure-deployment
description
Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests. Handle provision/deploy loops with automatic error diagnosis and retry. Use when deploying to Azure, running azd provision/deploy, executing smoke tests, or diagnosing deployment failures.

Azure Deployment

Role

You are the Deploy Agent. You provision Azure infrastructure, deploy the application to Azure Container Apps, and verify it works via smoke tests. You operate in a loop: provision → deploy → smoke test → verify. If anything fails, you diagnose the error, apply a fix, and retry. If smoke tests fail after a successful deployment, you roll back and open a GitHub issue.

Pre-Deployment Checklist

Before deploying, verify every precondition. Do not proceed until all pass.

#CheckHow to verify
1Tests pass locallyRun unit, Gherkin, and Playwright tests — all green
2State is ready.spec2cloud/state.json confirms Step 3 complete. Consult specs/contracts/infra/resources.yaml for resource config.
3azure.yaml validParse file; verify ≥1 service with valid project path and host: containerapp
4Infra templates existinfra/ contains main.bicep at minimum
5AZD installed + authazd version succeeds; azd auth login --check-status confirms auth
6AZD environment existsazd env list shows environment; if none, create with azd env new <name> and set AZURE_LOCATION

Provision Loop

Provision Azure infrastructure using AZD and Bicep. Retry on fixable errors.

1. Run `azd provision`
2. If success → proceed to Deploy Loop
3. If failure → analyze the error:
   a. Bicep validation error → fix infra/*.bicep files, retry
   b. Quota exceeded → suggest different region or SKU, update env vars, retry
   c. Permission error → STOP and flag for human (cannot fix IAM)
   d. Naming conflict → adjust resource names in Bicep parameters, retry
   e. Network/transient error → retry (max 3 attempts with backoff)
4. After applying a fix → re-run `azd provision`
5. Loop until provision succeeds or retries exhausted

Log every azd provision invocation and result to audit.log.

Deploy Loop

Deploy the application to the provisioned infrastructure.

1. Run `azd deploy`
2. If success → proceed to Smoke Test Protocol
3. If failure → analyze the error:
   a. Build error → fix Dockerfile or build configuration
   b. Container startup error → pull container logs, fix app config or startup
   c. Health check failure → verify health endpoint exists and returns 200
   d. Registry push failure → check ACR configuration and permissions
4. After applying a fix → re-run `azd deploy`
5. Loop until deploy succeeds or retries exhausted

Log every azd deploy invocation and result to audit.log.

Smoke Test Protocol

After a successful deployment, verify the live application works end-to-end.

  1. Get deployed URL — azd env get-values → extract SERVICE_WEB_ENDPOINT_URL.
  2. Run smoke tests against the live URL:
    • Health check: GET /health → HTTP 200
    • API health: GET /api/health → HTTP 200
    • Frontend loads: GET / → HTTP 200 with expected content
    • Critical path: Playwright @smoke tests against deployed URL
  3. Run the FULL E2E suite against the deployed URL. This is mandatory — every E2E test that passes locally must also pass on the deployed environment:
    bash
    PLAYWRIGHT_BASE_URL=<deployed-url> npx playwright test --config=e2e/playwright.config.ts
    All E2E tests must pass. A deployment is not considered verified until the complete E2E suite runs green against the live URL.
  4. All tests pass → deployment verified. Update state and finish.
  5. Any test fails → enter Rollback Protocol.

Rollback Protocol

If smoke tests fail after deployment:

  1. Rollback: Re-deploy the previous successful container image tag using azd deploy. If no previous deployment exists (first deploy), leave the failed deployment and flag for human review.
  2. Verify rollback: Re-run smoke tests against the rolled-back deployment.
  3. Open GitHub Issue:
    • Title: [spec2cloud] Smoke test failure after deployment
    • Body: Failed smoke test results, deployment logs, container logs
    • Labels: spec2cloud, deployment-failure, needs-fix
  4. Update state: Set phase back to implementation with failure details.
  5. The orchestrator picks up the issue and re-enters the build/test/deploy loop.
Show full SKILL.md (301 more words)Show less

AZD Commands Reference

CommandPurpose
azd initInitialize project (shell setup only)
azd env new <name>Create a new environment
azd env set <key> <value>Set an environment variable
azd provisionProvision Azure resources via Bicep
azd deployBuild and deploy the application
azd env get-valuesRetrieve deployed URLs and outputs
azd downTear down all resources (only on explicit request)
azd monitorOpen the monitoring dashboard

State Updates

  • After successful deployment: Record deployed URL, timestamp, container image tag, and AZD environment name in state.json.
  • After rollback: Record rollback details — image rolled back to, reason, and link to GitHub issue.
  • Audit log: Append every AZD command, its arguments, exit code, and truncated output to .spec2cloud/audit.log.
[ISO-timestamp] increment={id} step=deploy action=azd-provision result=success
[ISO-timestamp] increment={id} step=deploy action=azd-deploy result=success url={url}
[ISO-timestamp] increment={id} step=deploy action=smoke-tests result=pass:{N}/fail:{N}

Security Considerations

  • Never log secrets or connection strings. Redact sensitive values before writing to logs or GitHub issues.
  • Use managed identity for Azure resource access wherever possible. Avoid storing credentials in code or config files.
  • Verify HTTPS is enabled on all deployed endpoints. Do not accept HTTP-only deployments.
  • Check CORS configuration to ensure it matches the frontend URL and does not use a wildcard (*) in production.

Stack-Specific Details

See references/stack-deployment.md for AZD service structure, Container Apps configuration, Dockerfile details, infrastructure templates, environment variables, and smoke test commands.

Mandatory Completion Checklist

The orchestrator MUST verify ALL of the following before marking azure-deployment as complete:

  • Full regression suite passes locally before deployment
  • azd provision completes without errors
  • azd deploy completes without errors
  • Smoke tests pass against the deployed endpoints (not localhost)
  • HTTPS is enabled on all deployed endpoints
  • Application logs show no startup errors (check via azd monitor)
  • State JSON and audit log are updated with deployment URLs and status

BLOCKING: If any item is unchecked, the skill has NOT completed successfully. The orchestrator must loop back and complete the missing items before marking the increment as delivered.

© EmeaAppGbb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .github/skills/azure-deployment of EmeaAppGbb/spec2cloud.

  • SKILL.md
  • references/stack-deployment.md

Open the folder on GitHubat commit 8e76618

Compare with similar skills

Azure Deployment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Azure Deployment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azure Deployment this skillEmeaAppGbb/spec2cloud100—~1.8kAutomated safety check: PassMIT
Backdoor Deploymentmicrosoft/Docker-Provider174—~7kAutomated safety check: PassCustom licence
Deploying Scalable Agentsmicrosoft/ai-agents-for-beginners77k—~1.5kAutomated safety check: PassMIT
Deploying Scalable Agentsmicrosoft/ai-agents-for-beginners77k—~1.6kAutomated safety check: PassMIT
DeerFlow Smoke Testbytedance/deer-flow83k—~2.5kAutomated safety check: NotesMIT
Skyvern Deployment Smoke TestSkyvern-AI/skyvern23k—~1.5kAutomated safety check: PassAGPL-3.0

Similar skills

  • Backdoor Deployment

    microsoft/Docker-Provider

    Official

    Validate a container image change via backdoor deployment. An agent skill from microsoft/Docker-Provider.

    174 GitHub stars~7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Deploying Scalable Agents

    microsoft/ai-agents-for-beginners

    Official

    Take a working agent prototype to a scalable, observable production deployment on Microsoft Foundry.

    77k GitHub stars~1.5k tokensUpdated 19 days ago
    DevOps & CloudAuto-check passed

  • Deploying Scalable Agents

    microsoft/ai-agents-for-beginners

    Official

    Take one working agent prototype go scalable, observable production deployment for Microsoft Foundry.

    77k GitHub stars~1.6k tokensUpdated 19 days ago
    DevOps & CloudAuto-check passed

  • DeerFlow Smoke Test

    bytedance/deer-flow

    Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.

    83k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check: notes

  • Skyvern Deployment Smoke Test

    Skyvern-AI/skyvern

    Smoke-tests a Skyvern deployment by checking the backend API, frontend rendering, browser session provisioning and workflow execution in sequence.

    23k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Deployment E2E Testing

    microsoft/aspire

    Official

    Guide for writing Aspire deployment end-to-end tests. An agent skill from microsoft/aspire.

    6.3k GitHub stars~3.2k tokensUpdated today
    Testing & QAAuto-check passed

More from EmeaAppGbb/spec2cloud

All 38 skills in this repo

  • Contract Generation

    EmeaAppGbb/spec2cloud

    Generate API contracts, shared TypeScript types, and infrastructure resource definitions from Gherkin scenarios and test files.

    100 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed

  • Ddd Modeling

    EmeaAppGbb/spec2cloud

    Create Domain-Driven Design proposals from product specs or brownfield extraction outputs.

    100 GitHub stars~2.4k tokensUpdated 5 mo ago
    Auto-check passed

  • Implementation

    EmeaAppGbb/spec2cloud

    Write application code to make failing tests pass using contract-driven, slice-based architecture.

    100 GitHub stars~2.8k tokensUpdated 5 mo ago
    Auto-check passed

  • Spec Refinement

    EmeaAppGbb/spec2cloud

    Review PRDs and FRDs through product and technical lenses. An agent skill from EmeaAppGbb/spec2cloud.

    100 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed

  • State Management

    EmeaAppGbb/spec2cloud

    Read, write, and maintain .spec2cloud/state.json across phases and increments.

    100 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed

  • Tech Stack Resolution

    EmeaAppGbb/spec2cloud

    Identify, research, and resolve every technology needed by the application.

    100 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Azure Deployment

What does Azure Deployment do?

Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests. Azure Deployment is an agent skill from EmeaAppGbb/spec2cloud. Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.

When should I use Azure Deployment?

Azure Deployment fits situations like: deploying to Azure; running azd provision/deploy; executing smoke tests; diagnosing deployment failures.

How do I install Azure Deployment in Claude Code?

Run `npx skills add EmeaAppGbb/spec2cloud --skill azure-deployment -a claude-code`. Or copy the skill folder (.github/skills/azure-deployment in EmeaAppGbb/spec2cloud) into .claude/skills/azure-deployment in your project. Claude Code loads it when a task matches its description.

How do I install Azure Deployment in Codex?

Run `npx skills add EmeaAppGbb/spec2cloud --skill azure-deployment -a codex`. Or copy the skill folder (.github/skills/azure-deployment in EmeaAppGbb/spec2cloud) into .agents/skills/azure-deployment in your project. Codex loads it when a task matches its description.

Can I use Azure Deployment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EmeaAppGbb/spec2cloud --skill azure-deployment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-deployment, .gemini/skills/azure-deployment, .github/skills/azure-deployment and .opencode/skills/azure-deployment in your project.

What does Azure Deployment need to run?

Going by SKILL.md and its folder, Azure Deployment needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Azure Deployment access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Azure Deployment safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Azure Deployment use?

Azure Deployment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Azure Deployment use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 626 tokens, read only when the agent opens those files.

What are the alternatives to Azure Deployment?

Skills that share tags, products or a category with Azure Deployment: Backdoor Deployment (microsoft/Docker-Provider, 174 stars), Deploying Scalable Agents (microsoft/ai-agents-for-beginners, 77k stars), Deploying Scalable Agents (microsoft/ai-agents-for-beginners, 77k stars) and DeerFlow Smoke Test (bytedance/deer-flow, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azure Deployment?

EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on April 16, 2026.

Source: EmeaAppGbb/spec2cloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.