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

by microsoft in microsoft/azurelinux

Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state.

OfficialMITAuto-check passed

Install Azldev Remove Component

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

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

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

At a glance

Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state.

  • Works in 5 steps: Remove the definition. Delete the… → Remove publish / package config… → Remove the lock. There is no azldev… → …
  • Include remove component
  • SKILL.md covers Before you start, Steps, Verify and Notes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Azldev Remove Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state. Explains the manual removal workflow for deleting component metadata, cleaning references, and validating any related output-affecting changes. Triggers include remove component, delete package, drop component, prune dependency.

Its SKILL.md is about 910 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 remove component
  • Prune dependency

Example prompts

  • “/azldev-remove-component”

Workflow steps

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

  1. Remove the definition. Delete the component's dedicated
  2. Remove publish / package config references. If your project configures
  3. Remove the lock. There is no azldev command for this
  4. Remove the rendered spec. Let azldev prune orphaned spec directories
  5. Check other references. Grep for the component (and its binary names) in

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 Remove Component loads about 905 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 409 words of instructions outside code blocks.

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

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). 409 words, ~905 tokens.

Download SKILL.mdSave it as .claude/skills/azldev-remove-component/SKILL.md (or your agent's skills folder).
name
azldev-remove-component
description
Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state. Explains the manual removal workflow for deleting component metadata, cleaning references, and validating any related output-affecting changes. Triggers include remove component, delete package, drop component, prune dependency.

Remove a component

There is no azldev command to remove a component — it is a manual edit. A deletion-only change needs no package build, but changes to dependents, package/image configuration, or other built inputs must follow the repository's normal validation requirements. The steps below delete the component's definition, lock, and rendered spec, then clean up references.

Before you start

Confirm the component exists and inspect its resolved configuration:

sh
azldev comp list -p <name> -q -O json

Check for reverse dependencies first: if other components BuildRequires or Requires this one, removing it breaks their builds. Search the tree for the component name. Identify its binary subpackage names from the rendered output under specs/<first-char>/<name>/, then search for those names too. azldev comp query currently supports local spec sources only, not the usual upstream spec source.

Steps

  1. Remove the definition. Delete the component's dedicated <name>/<name>.comp.toml directory, or remove its inline [components.<name>] entry from whichever included TOML defines it.

  2. Remove publish / package config references. If your project configures publish channels or package groups, drop any references to the component or to its binary subpackages. Publishing is component-scoped; per-binary exceptions are binary-RPM-scoped — search for both.

  3. Remove the lock. There is no azldev command for this:

    sh
    rm locks/<name>.lock

  4. Remove the rendered spec. Let azldev prune orphaned spec directories:

    sh
    azldev comp render -a --clean-stale

    --clean-stale (only valid with -a) removes rendered-spec directories that no longer correspond to a configured component. It re-renders everything, so it is slow; for a targeted removal you can instead delete the component's rendered spec under specs/ by hand.

  5. Check other references. Grep for the component (and its binary names) in image definitions and any *.kiwi / package-list files, and remove or replace them — an image that installs a now-removed package will not build.

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

Verify

sh
azldev comp list -p <name> -q -O json   # should report the component is not found

Also confirm the lock and rendered spec directory are gone and that no image or package configuration still references the component.

If the removal required changes to dependents or package/image configuration, build and test the affected outputs according to the repository's normal validation policy.

Notes

  • Dependents with manual release. If removing this component forces a change in a dependent (e.g. dropping a BuildRequires), and that dependent sets release.calculation = "manual", bump its release counter yourself in the same change. Components with automatic release calculation (auto, autorelease, static) are handled by the normal commit/render/amend cycle.
  • Remove exclusive dependencies together. If a package is only needed by the component you are dropping, remove it in the same change to keep the tree consistent.

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

Open the folder on GitHubat commit f019108

Compare with similar skills

Azldev Remove 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 Remove Component compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Azldev Remove Component this skillmicrosoft/azurelinux5.3k—~905Automated safety check: PassMIT
Warp Feature Flag Removalwarpdotdev/warp65k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Dead Code Removercode-yeongyu/oh-my-openagent70k1 repos~1.8kAutomated safety check: PassCustom licence
Deleting ThoughtsNateBJones-Projects/OB14.7k—~995Automated safety check: PassCustom licence
Remove Bg AutomationComposioHQ/awesome-claude-skills77k3 repos~738Automated safety check: PassNone
Remove AI Slopscode-yeongyu/oh-my-openagent70k—~5.3kAutomated safety check: PassCustom licence

Similar skills

  • Warp Feature Flag Removal

    warpdotdev/warp

    Removes a Warp feature flag once it is stable for everyone, deleting the definition, the Cargo entries and every conditional check.

    65k GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • Dead Code Remover

    code-yeongyu/oh-my-openagent

    Finds unused code in a TypeScript project, confirms each candidate has no references through the language server, then hands removals to parallel agents.

    70k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed

  • Deleting Thoughts

    NateBJones-Projects/OB1

    A skill your agent uses when asked to delete, remove, purge, wipe, or "get rid of" an Open Brain thought, or before calling deletethought (the open-brain-delete-thought connector), which…

    4.7k GitHub stars~995 tokensUpdated yesterday
    Auto-check passed

  • Remove Bg Automation

    ComposioHQ/awesome-claude-skills

    Automate Remove Bg tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~738 tokens
    Productivity & AutomationAuto-check passed

  • Remove AI Slops

    code-yeongyu/oh-my-openagent

    Removes AI-generated code smells from branch changes or an explicit file list behind regression tests.

    70k GitHub stars~5.3k tokensUpdated yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

  • Azldev Image

    microsoft/azurelinux

    Official

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

    5.3k GitHub stars~758 tokensUpdated yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Questions about Azldev Remove Component

What does Azldev Remove Component do?

Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state. Azldev Remove Component is an agent skill from microsoft/azurelinux, published by the product's own GitHub organization. Read this before deleting or dropping a component; there is no azldev remove command, so doing it wrong leaves dangling state.

When should I use Azldev Remove Component?

Azldev Remove Component fits situations like: include remove component; prune dependency.

How do I install Azldev Remove Component in Claude Code?

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

How do I install Azldev Remove Component in Codex?

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

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

What does Azldev Remove Component need to run?

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

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

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

About 905 tokens (SKILL.md is roughly 3.6k 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 Remove Component?

Skills that share tags, products or a category with Azldev Remove Component: Warp Feature Flag Removal (warpdotdev/warp, 65k stars), Dead Code Remover (code-yeongyu/oh-my-openagent, 70k stars), Deleting Thoughts (NateBJones-Projects/OB1, 4.7k stars) and Remove Bg Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

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