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 Build Component

by microsoft in microsoft/azurelinux

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

OfficialMITAuto-check passed

Install Azldev Build Component

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

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

GitHub CLI
$ gh skill install microsoft/azurelinux azldev-build-component --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-build-component .claude/skills/azldev-build-component && 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-build-component
GitHub stars
5.3k
Token cost
~808 tokens
SKILL.md length
333 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Render error mentioning a non-standard… → Overlay did not apply as expected —… → Inspect the build environment — `azldev… → …
  • Include build component
  • SKILL.md covers Build, The inner loop and Debugging build failures
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Azldev Build Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before building a component or diagnosing a build failure; do not guess build flags or the inner loop. Explains how to build, iterate on, and debug an azldev component, covering comp build flags (local-repo, preserve-buildenv), the render/build/test inner loop, diff-sources, and disabling a failing %check via check.skip. Triggers include build component, build failed, build error, inner loop, preserve buildenv, local repo, disable check.

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

The repository describes itself as: General purpose Linux OS for Azure. The licence is MIT.

When your agent uses it

  • Include build component
  • Preserve buildenv

Example prompts

  • “/azldev-build-component”

Workflow steps

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

  1. Render error mentioning a non-standard Release tag — a release-calculation
  2. Overlay did not apply as expected — azldev comp diff-sources -p shows
  3. Inspect the build environment — `azldev comp build -p --preserve-buildenv
  4. Failing %check — fix the tests first (root cause, upstream patches, targeted

What it can do on your machine

Read from SKILL.md and the folder at commit f019108. 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 (its code samples are bash).

    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 Build Component loads about 808 tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 333 words of instructions outside code blocks.

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

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 f019108, republished under its MIT licence (© microsoft). 333 words, ~808 tokens.

Download SKILL.mdSave it as .claude/skills/azldev-build-component/SKILL.md (or your agent's skills folder).
name
azldev-build-component
description
Read this before building a component or diagnosing a build failure; do not guess build flags or the inner loop. Explains how to build, iterate on, and debug an azldev component, covering comp build flags (local-repo, preserve-buildenv), the render/build/test inner loop, diff-sources, and disabling a failing %check via check.skip. Triggers include build component, build failed, build error, inner loop, preserve buildenv, local repo, disable check.

Build and debug a component

Never install built RPMs on your host — they target the distro, not your dev machine. Test them in a chroot with the azldev-mock skill. Building and testing are separate steps: azldev comp build produces RPMs; it does not test them.

Build

sh
azldev comp build -p <name>                                     # one component
azldev comp build -p <a> -p <b> --local-repo-with-publish <dir> # chain deps via a local repo
azldev comp build -p <name> --local-repo <dir>                  # rebuild against a populated repo

Build foundational packages before their dependents. RPMs land in the project's configured output directory (out by default). -q quiets output but hides build progress — use it only for inner-loop builds you expect to succeed.

The inner loop

investigate → modify → render → build → test → inspect

StepCommand
Investigateread the rendered spec under specs/, or azldev comp diff-sources -p <name>
Modifyedit the component's .comp.toml (see the azldev-overlays and azldev-comp-toml skills)
Verifyazldev comp render -p <name> (fast — skips source tarballs)
Buildazldev comp build -p <name>
Testazldev adv mock shell --add-package <rpm> (see the azldev-mock skill)
Inspectazldev comp build -p <name> --preserve-buildenv always, then a mock shell

Prefer comp render for quick overlay verification; use comp diff-sources to see the exact overlay effect (it fetches sources once, applies overlays to a copy, and diffs the two trees). Builds can be slow — set generous timeouts.

Finalize with azldev comp update -p <name> before opening a PR (see the azldev-update-component skill).

Debugging build failures

  1. Render error mentioning a non-standard Release tag — a release-calculation issue; see the azldev-comp-toml skill.
  2. Overlay did not apply as expected — azldev comp diff-sources -p <name> shows what the overlays actually change.
  3. Inspect the build environment — azldev comp build -p <name> --preserve-buildenv on-failure (values on-failure, always, never), then enter a mock shell.
  4. Failing %check — fix the tests first (root cause, upstream patches, targeted fixes). Only as a last resort, disable with build.check.skip = true and a required build.check.skip_reason explaining what fails, why it cannot be fixed, and whether it is temporary. A transient --no-check build flag exists for one-off local builds.

Per-component build tweaks (build.defines, build.without) live in the .comp.toml — see the azldev-comp-toml skill.

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-build-component of microsoft/azurelinux.

Open the folder on GitHubat commit f019108

Compare with similar skills

Azldev Build Component 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 Build Component compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azldev Build Component this skillmicrosoft/azurelinux5.3k—~808Automated safety check: PassMIT
Diagnose Gatewayopenclaw/openclaw392k—~670Automated safety check: PassMIT
Diagnosegithub/awesome-copilot40k1 repos~1kAutomated safety check: PassMIT
Diagnose Why Work Stoppedpaperclipai/paperclip99k—~2.8kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
Diagnosing Missing RecordingsPostHog/posthog40k—~2kAutomated safety check: PassCustom licence

Similar skills

  • Diagnose Gateway

    openclaw/openclaw

    Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.

    392k GitHub stars~670 tokensUpdated today
    Auto-check passed

  • Diagnose

    github/awesome-copilot

    Official

    Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report…

    40k GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check passed

  • Diagnose Why Work Stopped

    paperclipai/paperclip

    Diagnose stalled, looping, or over-recovered Paperclip issue trees and propose a no-code product-rule plan.

    99k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • Diagnosing Missing Recordings

    PostHog/posthog

    Official

    Diagnoses why a session recording is missing or was not captured.

    40k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Diagnose Android Overheating

    sickn33/agentic-awesome-skills

    A skill your agent uses when diagnosing Android overheating, idle heat, thermal throttling, charging or radio heat, or abnormal battery drain with read-only ADB evidence and approval gates.

    47k GitHub starsUsed in 1 repo~2.9k tokens
    MobileAuto-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 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.6k tokensUpdated today
    Auto-check passed

  • Azldev Image

    microsoft/azurelinux

    Official

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

    5.3k GitHub stars~758 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

  • Azldev Overlays

    microsoft/azurelinux

    Official

    Read this before adding, changing, or diagnosing any overlay; never edit a spec or rendered file from memory.

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

Questions about Azldev Build Component

What does Azldev Build Component do?

Read this before building a component or diagnosing a build failure; do not guess build flags or the inner loop. Azldev Build Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before building a component or diagnosing a build failure; do not guess build flags or the inner loop.

When should I use Azldev Build Component?

Azldev Build Component fits situations like: include build component; preserve buildenv.

How do I install Azldev Build Component in Claude Code?

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

How do I install Azldev Build Component in Codex?

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

Can I use Azldev Build Component 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-build-component -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-build-component, .gemini/skills/azldev-build-component, .github/skills/azldev-build-component and .opencode/skills/azldev-build-component in your project.

What does Azldev Build Component need to run?

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

Does Azldev Build Component 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 Build Component 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 Build Component use?

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

About 808 tokens (SKILL.md is roughly 3.2k 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 Build Component?

Skills that share tags, products or a category with Azldev Build Component: Diagnose Gateway (openclaw/openclaw, 392k stars), Diagnose (github/awesome-copilot, 40k stars), Diagnose Why Work Stopped (paperclipai/paperclip, 99k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azldev Build Component?

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 8, 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.