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 Mock

by microsoft in microsoft/azurelinux

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

OfficialMITAuto-check passedTesting & QA

Install Azldev Mock

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

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

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

At a glance

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

  • Works in 5 steps: Run a simple command (e.g. echo ready)… → Ask the user to run the azldev adv mock… → Wait for confirmation that they are… → …
  • Include test package
  • SKILL.md covers Non-interactive chroot…, Inspect an RPM without…, Interactive chroot and Key flags, plus 1 more section
  • Calls dnf

What it does

Azldev Mock is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before testing or inspecting a built RPM; do not drive mock by hand from memory. Explains how to test and inspect built packages in a mock chroot with 'azldev adv mock shell', covering non-interactive (heredoc) and interactive chroot workflows, the -p/--add-package flag, and resetting stale chroot state. Triggers include test package, mock shell, inspect rpm, smoke test, chroot, verify build output.

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

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: General purpose Linux OS for Azure. The licence is MIT.

When your agent uses it

  • Include test package
  • Verify build output

Example prompts

  • “azldev adv mock shell”
  • “/azldev-mock”

Workflow steps

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

  1. Run a simple command (e.g. echo ready) in a foreground terminal to establish a shared shell.
  2. Ask the user to run the azldev adv mock shell command in that same terminal.
  3. Wait for confirmation that they are inside the mock shell.
  4. Run diagnostic commands in the same foreground terminal — they execute inside the chroot.
  5. Run exit to leave the chroot.

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

    Shell commands in SKILL.md call:

    • dnf

    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 Mock loads about 1k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 470 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~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 f019108, republished under its MIT licence (© microsoft). 470 words, ~1,006 tokens.

Download SKILL.mdSave it as .claude/skills/azldev-mock/SKILL.md (or your agent's skills folder).
name
azldev-mock
description
Read this before testing or inspecting a built RPM; do not drive mock by hand from memory. Explains how to test and inspect built packages in a mock chroot with 'azldev adv mock shell', covering non-interactive (heredoc) and interactive chroot workflows, the -p/--add-package flag, and resetting stale chroot state. Triggers include test package, mock shell, inspect rpm, smoke test, chroot, verify build output.

Test and inspect packages in a mock chroot

Never install built RPMs on the host. They target the distro you are building, not your dev machine. Use a mock chroot instead.

azldev tests and inspects packages inside mock build roots via mock shell, which lives under the hidden advanced group (azldev adv is an alias for azldev advanced; it does not appear in azldev --help).

Non-interactive chroot (preferred for agents)

Pipe commands in via a heredoc — fully autonomous, no user interaction needed:

sh
azldev adv mock shell --add-package /path/to/package.rpm <<'CMDS'
<command> --version
echo "exit code: $?"
exit
CMDS

Use this for automated checks: running binaries, querying installed packages, inspecting paths.

Inspect an RPM without installing it

When --add-package fails to install, or you just want to look at an RPM's contents, get the file inside the chroot and inspect it there rather than installing on the host. If the RPM is not already reachable inside the build root, copy it in first with mock --copyin <rpm> /tmp/ (using the project's distro mock config), then:

sh
azldev adv mock shell <<'CMDS'
rpm -qip /tmp/<name>*.rpm    # package info
rpm -qlp /tmp/<name>*.rpm    # file list
rpm -qRp /tmp/<name>*.rpm    # dependencies
dnf install /tmp/<name>*.rpm # retry the install to see the error details
exit
CMDS

This gives you the full distro environment for debugging dependency issues, file conflicts, and failed installs, without touching the host.

Interactive chroot

Use when you need to explore interactively or react to output between commands:

sh
azldev adv mock shell --add-package /path/to/package.rpm --enable-network

When driving an interactive shell as an agent:

  1. Run a simple command (e.g. echo ready) in a foreground terminal to establish a shared shell.
  2. Ask the user to run the azldev adv mock shell command in that same terminal.
  3. Wait for confirmation that they are inside the mock shell.
  4. Run diagnostic commands in the same foreground terminal — they execute inside the chroot.
  5. Run exit to leave the chroot.

Prefer the non-interactive heredoc approach; use interactive only when you must react to output between commands.

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

Key flags

FlagPurpose
-p, --add-package <path>Install a package into the chroot before entering. Accepts an RPM file path or a package name. May be repeated.
--enable-networkAllow network access (dependency resolution, downloads).

-p means --add-package, not a component name. Unlike azldev comp build -p <name>, mock shell has no component selector. -p <name> installs a package by name from the configured repos — it does not set up a chroot with that component's build dependencies.

Gotchas

  • Don't mix -p <name> with --add-package /path/to/<name>.rpm for the same package — that installs both the repo build and your local build, which conflict. Use one or the other.
  • The mock chroot is persistent across azldev adv mock shell sessions — installed packages and created files survive. Handy (install once, re-enter later), but stale state can confuse. azldev has no built-in reset; clear it with mock directly (--scrub=chroot, or --scrub=all to also drop the bootstrap), pointing at the project's distro mock config.
  • One mock session per terminal. Running azldev adv mock shell while a terminal is already inside a mock shell fails — run exit first.

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

Open the folder on GitHubat commit f019108

Compare with similar skills

Azldev Mock 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 Mock compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azldev Mock this skillmicrosoft/azurelinux5.3k—~1kAutomated safety check: PassMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Minimal Run And Auditlllllllama/RigorPilot-Skills4972 repos~691Automated safety check: PassMIT
Moav E2EMotherofallVPNs/MoaV448—~1.9kAutomated safety check: NotesMIT
Anchor Reprolynxlangya/techne1051 repos~1.2kAutomated safety check: PassMIT

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed

  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Minimal Run And Audit

    lllllllama/RigorPilot-Skills

    Rigor Run skill for README-first deep learning repo reproduction.

    497 GitHub starsUsed in 2 repos~691 tokens
    Testing & QAAuto-check passed

  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    448 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes

  • Anchor Repro

    lynxlangya/techne

    Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.

    105 GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-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~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 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

Categories

Questions about Azldev Mock

What does Azldev Mock do?

Read this before testing or inspecting a built RPM; do not drive mock by hand from memory. Azldev Mock is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before testing or inspecting a built RPM; do not drive mock by hand from memory.

When should I use Azldev Mock?

Azldev Mock fits situations like: include test package; verify build output.

How do I install Azldev Mock in Claude Code?

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

How do I install Azldev Mock in Codex?

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

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

What does Azldev Mock need to run?

Going by SKILL.md and its folder, Azldev Mock needs the command-line tools its instructions call (dnf).

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

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

About 1k tokens (SKILL.md is roughly 4k 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 Mock?

Skills that share tags, products or a category with Azldev Mock: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Azldev Mock?

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.