[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AWPVYB6TQXPZW9WMY8CF1":3,"skill-same:01M69AWPVYB6TQXPZW9WMY8CF1":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M69AWPVYB6TQXPZW9WMY8CF1","azldev",null,"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.","microsoft\u002Fazurelinux","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AVY9Y3D59ZBRVNKRJ851E",5364,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"repo","running","where to go","for","overlays","render","comp","how to","triggers","toml","do","use","cli","editing","common","file","core","config","component","components","workflow","go","2026-11-10 10:12:30",false,"---\nname: azldev\ndescription: \"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.\"\n---\n\n# Using azldev\n\nazldev builds a Linux distribution from TOML configuration. It imports RPM specs\nfrom an upstream distro and customizes them with an overlay system — no spec\nforking. Components render to specs and sidecar build inputs, then build into RPMs;\nimages assemble RPMs into bootable artifacts.\n\n## Orient yourself\n\n- Run azldev from the repo root (where `azldev.toml` lives), or pass `-C \u003Cdir>`.\n- Global, agent-friendly flags: **`-q`** (quiet) and **`-O json`** (machine-readable\n  output). They work on every command.\n- Config is a stitched TOML hierarchy: `azldev.toml` includes the distro and project\n  config, which include the component files (`**\u002F*.comp.toml`) into one namespace.\n\n## Core concepts\n\n- **Component** — a unit of packaging that renders to a spec and sidecar build inputs,\n  then builds into one or more RPMs. Its spec source is upstream (default), a pinned\n  upstream distro\u002Fversion, or a local spec.\n- **Overlay** — a semantic patch applied to a spec or source file at render time, so\n  you customize upstream without forking it.\n- **Distro** — a named build target (`*.distro.toml`) with upstream URIs, release\n  versions, and build inputs.\n- **Rendered spec** — the generated `.spec` after overlays; a build input, never\n  hand-edited.\n- **Lock** — a per-component file pinning the resolved upstream commit and an input\n  fingerprint.\n\n## Common commands\n\nTop-level commands in this build:\n\n- `azldev completion` — Generate the autocompletion script for the specified shell\n- `azldev component` — Manage components\n- `azldev config` — Manage tool configuration\n- `azldev docs` — Documentation commands\n- `azldev image` — Manage Azure Linux images\n- `azldev package` — Manage binary package configuration\n- `azldev project` — Manage Azure Linux projects\n- `azldev repo` — Inspect and manage RPM repositories\n- `azldev version` — Print the CLI version\n\nEveryday tasks (add `-q -O json` when scripting):\n\n| Task | Command |\n| --- | --- |\n| List components | `azldev comp list -a` |\n| Inspect one component | `azldev comp list -p \u003Cname>` |\n| Add a component | `azldev comp add` |\n| Build a component | `azldev comp build -p \u003Cname>` |\n| Render specs | `azldev comp render -p \u003Cname>` (or `-a`) |\n| Refresh a lock | `azldev comp update -p \u003Cname>` |\n| List \u002F build images | `azldev image list` \u002F `azldev image build` |\n\n`comp` is an alias for `component`. Always confirm current syntax with\n`azldev \u003Ccommand> --help`.\n\nThe hidden `advanced` group (`adv`) contains specialist integrations such as MCP and\nmock helpers; it is intentionally omitted from normal help.\n\n## Where to go next\n\n- Add a new component — read the `azldev-add-component` skill.\n- Edit or review a component's TOML — read the `azldev-comp-toml` skill.\n- Add or change overlays — read the `azldev-overlays` skill.\n- Annotate an overlay's intent (category, upstream status, provenance) — read the `azldev-overlay-metadata` skill.\n- Build, iterate, and debug a component — read the `azldev-build-component` skill.\n- Build, boot, and register images — read the `azldev-image` skill.\n- Refresh a lock and finalize for a PR — read the `azldev-update-component` skill.\n- Remove a component — read the `azldev-remove-component` skill.\n- Test built RPMs in a chroot — read the `azldev-mock` skill.\n\n## Golden rules\n\n- **Never edit generated output** — rendered specs and the output\u002Fwork\u002Flog dirs are\n  produced by azldev. Change the source config and re-render.\n- **Re-run `azldev comp update` before opening a PR** — the lock fingerprint covers\n  the whole component config, and lock \u002F rendered-spec CI checks run on committed state.\n- **Every overlay needs a `description`** explaining why the change is needed.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n","# Using azldev\n\nazldev builds a Linux distribution from TOML configuration. It imports RPM specs\nfrom an upstream distro and customizes them with an overlay system — no spec\nforking. Components render to specs and sidecar build inputs, then build into RPMs;\nimages assemble RPMs into bootable artifacts.\n\n## Orient yourself\n\n- Run azldev from the repo root (where `azldev.toml` lives), or pass `-C \u003Cdir>`.\n- Global, agent-friendly flags: **`-q`** (quiet) and **`-O json`** (machine-readable\n  output). They work on every command.\n- Config is a stitched TOML hierarchy: `azldev.toml` includes the distro and project\n  config, which include the component files (`**\u002F*.comp.toml`) into one namespace.\n\n## Core concepts\n\n- **Component** — a unit of packaging that renders to a spec and sidecar build inputs,\n  then builds into one or more RPMs. Its spec source is upstream (default), a pinned\n  upstream distro\u002Fversion, or a local spec.\n- **Overlay** — a semantic patch applied to a spec or source file at render time, so\n  you customize upstream without forking it.\n- **Distro** — a named build target (`*.distro.toml`) with upstream URIs, release\n  versions, and build inputs.\n- **Rendered spec** — the generated `.spec` after overlays; a build input, never\n  hand-edited.\n- **Lock** — a per-component file pinning the resolved upstream commit and an input\n  fingerprint.\n\n## Common commands\n\nTop-level commands in this build:\n\n- `azldev completion` — Generate the autocompletion script for the specified shell\n- `azldev component` — Manage components\n- `azldev config` — Manage tool configuration\n- `azldev docs` — Documentation commands\n- `azldev image` — Manage Azure Linux images\n- `azldev package` — Manage binary package configuration\n- `azldev project` — Manage Azure Linux projects\n- `azldev repo` — Inspect and manage RPM repositories\n- `azldev version` — Print the CLI version\n\nEveryday tasks (add `-q -O json` when scripting):\n\n| Task | Command |\n| --- | --- |\n| List components | `azldev comp list -a` |\n| Inspect one component | `azldev comp list -p \u003Cname>` |\n| Add a component | `azldev comp add` |\n| Build a component | `azldev comp build -p \u003Cname>` |\n| Render specs | `azldev comp render -p \u003Cname>` (or `-a`) |\n| Refresh a lock | `azldev comp update -p \u003Cname>` |\n| List \u002F build images | `azldev image list` \u002F `azldev image build` |\n\n`comp` is an alias for `component`. Always confirm current syntax with\n`azldev \u003Ccommand> --help`.\n\nThe hidden `advanced` group (`adv`) contains specialist integrations such as MCP and\nmock helpers; it is intentionally omitted from normal help.\n\n## Where to go next\n\n- Add a new component — read the `azldev-add-component` skill.\n- Edit or review a component's TOML — read the `azldev-comp-toml` skill.\n- Add or change overlays — read the `azldev-overlays` skill.\n- Annotate an overlay's intent (category, upstream status, provenance) — read the `azldev-overlay-metadata` skill.\n- Build, iterate, and debug a component — read the `azldev-build-component` skill.\n- Build, boot, and register images — read the `azldev-image` skill.\n- Refresh a lock and finalize for a PR — read the `azldev-update-component` skill.\n- Remove a component — read the `azldev-remove-component` skill.\n- Test built RPMs in a chroot — read the `azldev-mock` skill.\n\n## Golden rules\n\n- **Never edit generated output** — rendered specs and the output\u002Fwork\u002Flog dirs are\n  produced by azldev. Change the source config and re-render.\n- **Re-run `azldev comp update` before opening a PR** — the lock fingerprint covers\n  the whole component config, and lock \u002F rendered-spec CI checks run on committed state.\n- **Every overlay needs a `description`** explaining why the change is needed.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n",{"name":5,"description":7},"4.0","431ad36a7a827e8ec414e96ae75517ec1ded115d",".agents\u002Fskills\u002Fazldev",714,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 02:36:52",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Fazurelinux --skill azldev",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Fazurelinux --skill azldev",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Fazurelinux --skill azldev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev\u002FSKILL.md",true,[],[70,98,120,144,165,189],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":41},"01M69AX4PP9MJPS4TE3XDW93NJ","skill-metrics","[Skill] metrics, azure-monitor, aks - Query Azure Monitor metrics for Koji AKS node CPU, memory, disk usage, and pod readiness.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-metrics\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,22],"skill metrics","metrics","memory","azure","monitor","azure-monitor","aks","disk","node","query","azure monitor","false","readiness","CPU","disk usage","usage",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":41},"01M69AX2WT9YWZTVMMQ6QWHG3Y","skill-mass-triage","[Skill] Batch-triage build failures from a JSON results file — diagnose with parallel sub-agents, bucketize by root cause, and produce a consolidated summary. Use when asked to triage a Koji results file. Triggers: batch triage, mass triage, triage results file, bucketize failures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-mass-triage\u002FSKILL.md",[104],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[106,107,108,109,110,34,111,112,113,30,114,115,27,116,117,118,119],"triage","skill mass triage","diagnose","produce","batch","json","parallel","results","build","summary","with","root","root cause","when",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":41},"01M69AX11X7RJS8A0GBJV2X0WD","skill-kql-queries","[Skill] kql, queries, log analytics, container logs - KQL query templates for Koji container logs, pod errors, restarts, Kubernetes events, build job activity, and node resource usage via Log Analytics.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-kql-queries\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[131,132,133,134,135,136,137,90,138,139,114,91,93,140,141,142,143,97,22],"skill kql queries","kql","queries","kubernetes","analytics","logs","templates","container","log","events","via","activity","errors",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":41},"01M69AWYRJY05J3N3K9PZ0X38H","skill-koji-triage","[Skill] Examine Koji builds, fetch task info and logs from the Koji Web UI, identify failures, and provide root cause analysis. Use when triaging Koji build failures, investigating failed tasks, downloading build logs, or searching for broken packages. Triggers: koji failure, koji build failed, koji task, koji log, koji triage, build failure analysis.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-koji-triage\u002FSKILL.md",[150],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[106,152,153,154,155,156,157,136,158,159,160,30,139,161,162,27,163,164,22,118,119],"skill koji triage","web","root cause analysis","tasks","packages","ui","analysis","broken","fetch","task","info","failure analysis","web ui",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":41},"01M69AWWNGM4S4DDN6MSXMJ1XY","skill-fedora-mirror-injections","[Skill] Diagnose Azure Linux Stage 1 (bootstrap-mirror) BuildRequires resolution failures and backfill missing RPMs into the prod Fedora updates mirror via the azl-infra injections file. Use when triaging stage-1 \u002F azl4-bootstrap-mirror build failures, finding dependency gaps in the Fedora mirror, deciding whether a failure is a real mirror gap vs a transient timeout or a spec bug, adding entries to azl4-stage1-injections.yaml, or opening a PR with mirror injections. Triggers: bootstrap-mirror, stage 1 build failure, fedora mirror gap, missing BuildRequires, nothing provides crate, no match for argument, injections file, azl4-stage1-injections, mirror injection.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-fedora-mirror-injections\u002FSKILL.md",[171],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[173,174,175,176,177,108,85,178,179,180,30,181,182,183,184,27,185,186,187,22,188,119],"skill fedora mirror injections","fedora","mirror","spec","linux","pr","bootstrap","injection","dependency","bug","infra","entries","missing","argument","updates","backfill",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":41},"01M69AWTVNFMTX4KQVR6EK62C0","skill-deployment-context","[Skill] deployment context, aks, azure, koji - Resolve Koji AKS deployment context -- resource group, cluster name, subscription, Log Analytics workspace, and monitoring resource names from deployment_summary.yaml when available, or discover them dynamically from Azure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fskill-deployment-context\u002FSKILL.md",[195],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[197,198,199,135,85,200,201,88,202,139,115,203,93,204,205,119],"skill deployment context","deployment","context","yaml","monitoring","workspace","discover","name","cluster"]