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

by microsoft in microsoft/azurelinux

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

OfficialMITAuto-check passed

Install Azldev Add Component

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

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

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

At a glance

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

  • Works in 4 steps: Add a bare entry so azldev can resolve… → Create the initial lock so source… → Pull the sources without overlays into a… → …
  • Include add component
  • SKILL.md covers Before you start, Inline vs dedicated file, Customize and Validate
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Azldev Add Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.

Its SKILL.md is about 990 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 add component
  • Create comp.toml

Example prompts

  • “/azldev-add-component”

Workflow steps

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

  1. Add a bare entry so azldev can resolve the component: run azldev comp add
  2. Create the initial lock so source resolution is pinned before inspection
  3. Pull the sources without overlays into a scratch dir under the work dir
  4. Read the spec and plan any overlays.

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 and toml).

    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 Add Component loads about 987 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 435 words of instructions outside code blocks.

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

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). 435 words, ~987 tokens.

Download SKILL.mdSave it as .claude/skills/azldev-add-component/SKILL.md (or your agent's skills folder).
name
azldev-add-component
description
Read this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.

Add a component

Before you start

Confirm the component does not already exist:

sh
azldev comp list -p <name> -q -O json
Inspect the upstream spec first

The reliable way to see what you are importing (direct web fetches of upstream dist-git often fail bot detection):

  1. Add a bare entry so azldev can resolve the component: run azldev comp add <name> (it appends [components.<name>] to the root config file), or hand-add [components.<name>] to an included config file if you want it to live elsewhere. A bare root entry is perfect for initial testing, but real distros will usually segment the configuration into included files. Once the initial pass is done, ensure the component is in the right place and remove the root entry.

  2. Create the initial lock so source resolution is pinned before inspection:

    sh
    azldev comp update -p <name>

  3. Pull the sources without overlays into a scratch dir under the work dir:

    sh
    azldev comp prep-sources -p <name> --skip-overlays --force -o base/build/work/scratch/<name> -q

  4. Read the spec and plan any overlays.

Inline vs dedicated file

  • Inline — a bare upstream import with no changes stays in a shared config file:

    toml
    [components.jq]

  • Dedicated — anything that needs overlays, build config, or a local spec gets its own <name>/<name>.comp.toml. Rule of thumb: more than [components.<name>] earns a dedicated file. An includes = ["**/*.comp.toml"] glob picks it up automatically.

azldev comp add <name> [<name>...] adds bare [components.<name>] entries that inherit the distro defaults; it writes to the root config file and does not scaffold spec or source files. If your distro keeps components in included or dedicated files, move the entry there afterward.

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

Customize

For spec source types and overlays, read the azldev-comp-toml and azldev-overlays skills. Key points when adding a component:

  • Prefer overlays over forking the spec — overlays get upstream updates for free. Forking a spec is a last resort and a long-term maintenance commitment. Get explicit user sign-off first, document every change, and keep the delta minimal.
  • Every overlay needs a description explaining why it is needed.
  • Keep %check enabled. Disable it only as a last resort via build.check.skip = true with a required build.check.skip_reason (see the azldev-build-component skill).

Validate

The initial lock pins the upstream revision you inspected. Refresh it after the component inputs settle, then validate:

sh
azldev comp update -p <name>          # resolve the upstream commit and write the lock
azldev comp render -p <name>          # apply overlays and write the rendered spec
azldev comp diff-sources -p <name>    # see exactly what the overlays change
azldev comp build -p <name>           # build the RPMs

Inspect the rendered spec under specs/. A new component always needs a smoke test — see the azldev-build-component and azldev-mock skills.

After all component inputs are final, run azldev comp update -p <name> again and re-render. Stage the component definition and sources, locks/<name>.lock, and the rendered output before committing. Then re-render, stage specs/<first-char>/<name>/, and amend the commit so %changelog and Release: reflect it. See the azldev-update-component skill for the complete finalization workflow.

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

Open the folder on GitHubat commit f019108

Compare with similar skills

Azldev Add 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 Add Component compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azldev Add Component this skillmicrosoft/azurelinux5.3k—~987Automated safety check: PassMIT
Importasgeirtj/system_prompts_leaks69k—~3.5kAutomated safety check: PassCC0-1.0
Nx Importnrwl/nx29k6 repos~3.5kAutomated safety check: PassMIT
Type Only Importsthedaviddias/Front-End-Checklist74k—~558Automated safety check: PassMIT
Import Memoryasgeirtj/system_prompts_leaks69k—~2.7kAutomated safety check: WarnCC0-1.0
Hermes Importsaffaan-m/ECC275k1 repos~752Automated safety check: PassMIT

Similar skills

  • Import

    asgeirtj/system_prompts_leaks

    Handle explicit /import requests for read-only transcript recovery and a resume checkpoint, or continue work from other coding agents and unnamed artifacts.

    69k GitHub stars~3.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 6 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Type Only Imports

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing import statements in TypeScript files, setting up a new TypeScript project, or investigating unexpected bundle inclusions from type-only dependencies.

    74k GitHub stars~558 tokensUpdated yesterday
    Auto-check passed

  • Import Memory

    asgeirtj/system_prompts_leaks

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    69k GitHub stars~2.7k tokensUpdated today
    Auto-check: warnings

  • Hermes Imports

    affaan-m/ECC

    Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts.

    275k GitHub starsUsed in 1 repo~752 tokens
    Auto-check passed

  • Hermes Imports

    affaan-m/ECC

    将本地 Hermes 操作员工作流转换为经过清理的 ECC 技能和发布包工件。在准备将 Hermes 工作流用于公共 ECC 重用而不泄露私有工作区状态、凭据或仅本地路径时使用。

    275k GitHub stars~324 tokensUpdated 3 days ago
    Auto-check passed

More from microsoft/azurelinux

All 10 skills in this repo

  • 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~808 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 Add Component

What does Azldev Add Component do?

Read this before adding or importing a component; follow the workflow instead of guessing. Azldev Add Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before adding or importing a component; follow the workflow instead of guessing.

When should I use Azldev Add Component?

Azldev Add Component fits situations like: include add component; create comp.toml.

How do I install Azldev Add Component in Claude Code?

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

How do I install Azldev Add Component in Codex?

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

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

What does Azldev Add Component need to run?

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

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

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

About 987 tokens (SKILL.md is roughly 3.9k 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 Add Component?

Skills that share tags, products or a category with Azldev Add Component: Import (asgeirtj/system_prompts_leaks, 69k stars), Nx Import (nrwl/nx, 29k stars), Type Only Imports (thedaviddias/Front-End-Checklist, 74k stars) and Import Memory (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azldev Add 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.