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

Official agent skill

Azldev

by microsoft in microsoft/azurelinux

Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config.

OfficialMITAuto-check passed

Install Azldev

skills CLI
$ npx skills add microsoft/azurelinux --skill azldev -a claude-code

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

GitHub CLI
$ gh skill install microsoft/azurelinux azldev --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/microsoft/azurelinux.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/azldev .claude/skills/azldev && 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
azldev
GitHub stars
5.3k
Token cost
~1.1k tokens
SKILL.md length
511 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config.

  • Build a component
  • SKILL.md covers Orient yourself, Core concepts, Common commands and Where to go next, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Add a component

What it does

Azldev is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config. Explains how to use the azldev CLI to build a distro from TOML config, including the core concepts (components, overlays, distros, rendered specs, locks), running azldev (repo root or -C, plus the -q and -O json flags), the common commands, and where to go for each workflow. Triggers include azldev, comp build, comp render, comp update, build a…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Microsoft Azure and Linux. The repository describes itself as: General purpose Linux OS for Azure. The licence is MIT.

When your agent uses it

  • Build a component
  • Add a component

Example prompts

  • “/azldev”

What it can do on your machine

Read from SKILL.md and the folder at commit 61663c0. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Azldev loads about 1.1k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~141
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 microsoft/azurelinux at commit 61663c0, republished under its MIT licence (© microsoft). 511 words, ~1,087 tokens.

Download SKILL.mdSave it as .claude/skills/azldev/SKILL.md (or your agent's skills folder).
name
azldev
description
Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config. Explains how to use the azldev CLI to build a distro from TOML config, including the core concepts (components, overlays, distros, rendered specs, locks), running azldev (repo root or -C, plus the -q and -O json flags), the common commands, and where to go for each workflow. Triggers include azldev, comp build, comp render, comp update, build a component, add a component, distro config.

Using azldev

azldev builds a Linux distribution from TOML configuration. It imports RPM specs from an upstream distro and customizes them with an overlay system — no spec forking. Components render to specs and sidecar build inputs, then build into RPMs; images assemble RPMs into bootable artifacts.

Orient yourself

  • Run azldev from the repo root (where azldev.toml lives), or pass -C <dir>.
  • Global, agent-friendly flags: -q (quiet) and -O json (machine-readable output). They work on every command.
  • Config is a stitched TOML hierarchy: azldev.toml includes the distro and project config, which include the component files (**/*.comp.toml) into one namespace.

Core concepts

  • Component — a unit of packaging that renders to a spec and sidecar build inputs, then builds into one or more RPMs. Its spec source is upstream (default), a pinned upstream distro/version, or a local spec.
  • Overlay — a semantic patch applied to a spec or source file at render time, so you customize upstream without forking it.
  • Distro — a named build target (*.distro.toml) with upstream URIs, release versions, and build inputs.
  • Rendered spec — the generated .spec after overlays; a build input, never hand-edited.
  • Lock — a per-component file pinning the resolved upstream commit and an input fingerprint.

Common commands

Top-level commands in this build:

  • azldev completion — Generate the autocompletion script for the specified shell
  • azldev component — Manage components
  • azldev config — Manage tool configuration
  • azldev docs — Documentation commands
  • azldev image — Manage Azure Linux images
  • azldev package — Manage binary package configuration
  • azldev project — Manage Azure Linux projects
  • azldev repo — Inspect and manage RPM repositories
  • azldev version — Print the CLI version

Everyday tasks (add -q -O json when scripting):

TaskCommand
List componentsazldev comp list -a
Inspect one componentazldev comp list -p <name>
Add a componentazldev comp add
Build a componentazldev comp build -p <name>
Render specsazldev comp render -p <name> (or -a)
Refresh a lockazldev comp update -p <name>
List / build imagesazldev image list / azldev image build

comp is an alias for component. Always confirm current syntax with azldev <command> --help.

The hidden advanced group (adv) contains specialist integrations such as MCP and mock helpers; it is intentionally omitted from normal help.

Show full SKILL.md (156 more words)Show less

Where to go next

  • Add a new component — read the azldev-add-component skill.
  • Edit or review a component's TOML — read the azldev-comp-toml skill.
  • Add or change overlays — read the azldev-overlays skill.
  • Annotate an overlay's intent (category, upstream status, provenance) — read the azldev-overlay-metadata skill.
  • Build, iterate, and debug a component — read the azldev-build-component skill.
  • Build, boot, and register images — read the azldev-image skill.
  • Refresh a lock and finalize for a PR — read the azldev-update-component skill.
  • Remove a component — read the azldev-remove-component skill.
  • Test built RPMs in a chroot — read the azldev-mock skill.

Golden rules

  • Never edit generated output — rendered specs and the output/work/log dirs are produced by azldev. Change the source config and re-render.
  • Re-run azldev comp update before opening a PR — the lock fingerprint covers the whole component config, and lock / rendered-spec CI checks run on committed state.
  • Every overlay needs a description explaining why the change is needed.

Generated by azldev docs agent; do not hand-edit.

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

Files

Just SKILL.md in .agents/skills/azldev of microsoft/azurelinux.

Open the folder on GitHubat commit 61663c0

Compare with similar skills

Azldev 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.

Azldev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azldev this skillmicrosoft/azurelinux5.3k—~1.1kAutomated safety check: PassMIT
Image Managementdotnet/dotnet-docker4.9k—~1.1kAutomated safety check: PassMIT
Build Imageskubernetes-sigs/cloud-provider-azure294—~1.7kAutomated safety check: PassApache-2.0
Ama Logs Update Charts Release Notesmicrosoft/Docker-Provider174—~2.6kAutomated safety check: PassCustom licence
Releasing Blancbnfy/blanc114—~2.9kAutomated safety check: NotesMIT
WebGPU Provider Testing Without a GPUmicrosoft/onnxruntime22k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Image Management

    dotnet/dotnet-docker

    Official

    Manages .NET Docker images including adding images for new .NET versions, new Linux distros (Alpine, Ubuntu, Azure Linux), and new Windows versions.

    4.9k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Build Images

    kubernetes-sigs/cloud-provider-azure

    Official

    Build cloud-provider-azure container images through the repo Makefile with explicit IMAGETAG and IMAGEREGISTRY inputs, optional make flag overrides, and opt-in bounded Docker or Podman retries.

    294 GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Ama Logs Update Charts Release Notes

    microsoft/Docker-Provider

    Official

    Prepare an ama-logs release PR: bump the image tag (X.Y.Z) across Helm charts, manifests, and Dockerfiles, and add a formatted ReleaseNotes.md entry.

    174 GitHub stars~2.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Releasing Blanc

    bnfy/blanc

    Full runbook for cutting a Blanc desktop release — scripts/release.sh mechanics and its required BLANCRELEASE env vars, macOS notarization via 1Password, the Touch ID provisioning profile and…

    114 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • WebGPU Provider Testing Without a GPU

    microsoft/onnxruntime

    Official

    Shows how to build and run ONNX Runtime WebGPU provider tests on Linux with no GPU, using the Mesa lavapipe software Vulkan adapter, and where that approach falls short.

    22k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Multiline Validation

    microsoft/Docker-Provider

    Official

    Validate multi-line log stitching behavior for an ama-logs image change.

    174 GitHub stars~2.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from microsoft/azurelinux

All 10 skills in this repo

  • Azldev Add Component

    microsoft/azurelinux

    Official

    Read this before adding or importing a component; follow the workflow instead of guessing.

    5.3k GitHub stars~987 tokensUpdated today
    Auto-check passed

  • Azldev Build Component

    microsoft/azurelinux

    Official

    Read this before building a component or diagnosing a build failure; do not guess build flags or the inner loop.

    5.3k GitHub stars~894 tokensUpdated today
    Auto-check passed

  • Azldev Comp Toml

    microsoft/azurelinux

    Official

    Read this before authoring, editing, or reviewing a .comp.toml file; do not work from memory.

    5.3k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Azldev Image

    microsoft/azurelinux

    Official

    Read this before building, booting, or configuring an azldev image.

    5.3k GitHub stars~966 tokensUpdated today
    Auto-check passed

  • Azldev Mock

    microsoft/azurelinux

    Official

    Read this before testing or inspecting a built RPM; do not drive mock by hand from memory.

    5.3k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Azldev Overlay Metadata

    microsoft/azurelinux

    Official

    Read this before adding or reviewing an overlay metadata table; do not guess the category or upstream status from memory.

    5.3k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Questions about Azldev

What does Azldev do?

Read this before running azldev or editing azldev config, and whenever working in a repo that contains an azldev.toml file; do not guess azldev's commands or config. Azldev is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization.toml file; do not guess azldev's commands or config.

When should I use Azldev?

Azldev fits situations like: build a component; add a component.

How do I install Azldev in Claude Code?

Run `npx skills add microsoft/azurelinux --skill azldev -a claude-code`. Or copy the skill folder (.agents/skills/azldev in microsoft/azurelinux) into .claude/skills/azldev in your project. Claude Code loads it when a task matches its description.

How do I install Azldev in Codex?

Run `npx skills add microsoft/azurelinux --skill azldev -a codex`. Or copy the skill folder (.agents/skills/azldev in microsoft/azurelinux) into .agents/skills/azldev in your project. Codex loads it when a task matches its description.

Can I use Azldev 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 microsoft/azurelinux --skill azldev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azldev, .gemini/skills/azldev, .github/skills/azldev and .opencode/skills/azldev in your project.

What does Azldev need to run?

SKILL.md names no scripts, command-line tools or credentials: Azldev is instructions for the agent only.

Does Azldev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Azldev 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 Azldev use?

Azldev 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 Azldev use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Azldev?

Skills that share tags, products or a category with Azldev: Image Management (dotnet/dotnet-docker, 4.9k stars), Build Images (kubernetes-sigs/cloud-provider-azure, 294 stars), Ama Logs Update Charts Release Notes (microsoft/Docker-Provider, 174 stars) and Releasing Blanc (bnfy/blanc, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azldev?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/azurelinux, which has 5,348 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.

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