HavenSkills

Claude Cloud Skills

Prepare, validate and troubleshoot Azure application deployments.

Skills
6 skills

How to choose

Begin with project preparation for a new service. Use diagnostics when a deployed service already has an error to reproduce.

Filter

All skills in this category

azure-prepare

Assess an application and prepare its project configuration for Azure deployment.

by microsoft
npx skills add microsoft/azure-skills --skill azure-prepare
Author
microsoft
Repo
GitHub

azure-validate

Check Azure project configuration and deployment prerequisites.

by microsoft
npx skills add microsoft/azure-skills --skill azure-validate
Author
microsoft
Repo
GitHub

azure-deploy

Deploy a prepared application to the intended Azure environment.

by microsoft
npx skills add microsoft/azure-skills --skill azure-deploy
Author
microsoft
Repo
GitHub

azure-diagnostics

Investigate Azure runtime issues using resource state, logs and platform diagnostics.

by microsoft
npx skills add microsoft/azure-skills --skill azure-diagnostics
Author
microsoft
Repo
GitHub

azure-storage

Choose and configure Azure storage for application data and files.

by microsoft
npx skills add microsoft/azure-skills --skill azure-storage
Author
microsoft
Repo
GitHub

microsoft-foundry

Work with Microsoft Foundry projects, models and AI application resources.

by microsoft
npx skills add microsoft/azure-skills --skill microsoft-foundry
Author
microsoft
Repo
GitHub

What cloud skills are for

A cloud skill turns “deploy this” from a conversation into an operation. The model already knows what a Dockerfile looks like; what it does not know is your subscription, your region, your resource names, and the order in which your platform accepts changes. A cloud skill supplies exactly that — the account-specific steps and a check after each one.

The honest promise: it saves you from re-explaining your setup on every run, and it stops the agent from inventing flags that your CLI version no longer has.

The five-step Azure path, and why the order matters

All six skills on this page come from microsoft/azure-skills, and they are a sequence rather than alternatives:

  1. azure-prepare — reads the application and writes the project's deployment configuration: resource names, region, app settings. This is where the deployment target is decided. Skip it and the agent guesses.
  2. azure-validate — checks that configuration against the prerequisites before anything is created. Cheap failure goes here.
  3. azure-deploy — creates and updates the resources. Expensive failure goes here, which is why validate exists.
  4. azure-diagnostics — reads resource state and logs when something answers 403 or 404 after a successful deploy. That pairing — deploy succeeded, first request failed — is almost always identity and role assignment, not a code bug.
  5. azure-storage and microsoft-foundry — the two sideways skills. Storage decides where application data and files live; Foundry is for Microsoft's AI project resources.

If you install only azure-deploy, expect it to guess the target. That is the single most common way an Azure run goes wrong.

Where these skills break in practice

  • Permission errors read as success. The command exits 0, the build never reached the app, and the agent reports a URL that 404s. The check must be an HTTP request against the URL, not the exit code.
  • Wrong environment. Staging credentials in a production run is the expensive version; the cheap version is deploying to a region that has no database yet.
  • Silent partial deploys. Static assets upload, the API fails, and the site half-works for hours. List what should exist afterwards and verify each piece.
  • Secrets in the transcript. Tokens pasted into commands end up in logs. Pass them as environment variables or a credential file.
  • Version drift. The skill's CLI instructions are older than your toolchain. If a flag looks unfamiliar, check it against --help before running.

The check that catches most of it

  1. Open the resource group in the portal and confirm the region and subscription match the environment you meant.
  2. Hit the deployed URL yourself: 200 with the right content, not just a 200.
  3. Deploy the same commit twice. The second run should be a no-op; duplicated resources mean the flow is not idempotent.
  4. Grep the transcript for anything that looks like a key or a password.

Which page to read next

Database skills matter the moment a deploy touches migrations — a deploy that succeeds but leaves the schema one version behind is worse than a failed one. Agent workflow explains the SKILL.md format these skills are written in.

How to evaluate the result

Review the target subscription and environment, then validate configuration and service health.

How to check the result

Confirm the resource group and region in the portal match the intended environment, then load the health endpoint and read the start-up log. A deploy that returns 403 or 404 on the first request usually means identity and role assignment, not a code bug.

Frequently asked questions

How do I install one of these cloud skills?

Use the command beside the skill, select a supported agent, then reload the agent and confirm it can see the skill in your project.

Can I install only azure-deploy?

You can install azure-deploy on its own. Before deploying, run azure-prepare to set the resource names, region and app settings, then use azure-validate to verify the target.

Do these skills work for AWS or Google Cloud?

No. The skills in microsoft/azure-skills describe Azure resources and Azure deployment flows. For AWS or GCP you need that platform's own skills.

How do I try a deployment without risking production?

Work in a separate resource group or subscription, run validate before deploy, and keep the previous deployment available so you can switch back without rebuilding configuration from memory.

Why does my deployed app return an authorisation error?

Check that the calling identity has the required Azure role. Use azure-diagnostics to inspect resource state and logs before you change configuration.

Will Claude know my platform's current CLI?

Only as current as the skill's last update. Treat unfamiliar flags as a signal to verify before running the command.