[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AWHQZTXHGTXD0PQK0TGER":3,"skill-same:01M69AWHQZTXHGTXD0PQK0TGER":70},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M69AWHQZTXHGTXD0PQK0TGER","azldev-overlays",null,"Read this before adding, changing, or diagnosing any overlay; never edit a spec or rendered file from memory. Explains how to modify a component's RPM spec or loose source files with azldev overlays (semantic patches applied at render time) instead of forking the spec, covering overlay types, the render-and-inspect loop, common failures, pitfalls, and metadata. Triggers include overlay, overlay failed, no match, spec-add-tag, spec-remove-tag, patch-add, fix spec, backport, disable test, prune subpackage, edit spec.","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-overlays\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"overlays","azldev overlays","azldev","never","overlay","edit spec","inspect","rpm","render","types","how to","time","files","patch","spec","remove","fix","common","loop","backport","component","test","memory","2026-11-10 10:12:30",false,"---\nname: azldev-overlays\ndescription: \"Read this before adding, changing, or diagnosing any overlay; never edit a spec or rendered file from memory. Explains how to modify a component's RPM spec or loose source files with azldev overlays (semantic patches applied at render time) instead of forking the spec, covering overlay types, the render-and-inspect loop, common failures, pitfalls, and metadata. Triggers include overlay, overlay failed, no match, spec-add-tag, spec-remove-tag, patch-add, fix spec, backport, disable test, prune subpackage, edit spec.\"\n---\n\n# Working with overlays\n\nOverlays are **semantic patches** applied to a component's RPM spec and loose\nsource files at render time. They let you make targeted changes to an upstream\nspec without forking it. Prefer an overlay over hand-editing a rendered spec:\noverlays are re-applied on every render, so a manual edit to a rendered spec is\noverwritten.\n\n## The inner loop\n\nOverlays live in the component's TOML config — inline `[[components.\u003Cname>.overlays]]`\nentries, or per-file overlay documents referenced by the component's `overlay-files`\nglob. They apply **in order** and are **non-atomic**: if one fails part-way, the\noverlays before it stay applied.\n\n1. Add or edit the overlay in the component config.\n2. Re-render and inspect the result:\n\n   ```sh\n   azldev comp render -p \u003Cname>\n   ```\n\n   Read the rendered spec (under `specs\u002F`) to confirm the change\n   landed where you intended, and iterate until it is correct.\n3. Finalize the lock and changelog with the normal end-of-work refresh (see the\n   `azldev-update-component` skill): update the lock, commit, then re-render and amend.\n\nConfig errors reference the offending overlay by its `description`, so give every\noverlay a short, specific `description`.\n\n## Diagnose common failures\n\nStart with `azldev comp diff-sources -p \u003Cname>` to see the exact overlay effect.\nUse separate pre\u002Fpost `prep-sources` directories only when you need persistent trees\nfor deeper inspection.\n\n| Symptom | Likely cause and fix |\n| --- | --- |\n| `spec-add-tag`: tag already exists | Upstream already has the tag. Use `spec-set-tag`, or `spec-update-tag` when its prior existence is an invariant. |\n| `spec-search-replace`: no match | Inspect the current upstream line, check TOML regex quoting, and narrow the expression to the actual section\u002Fpackage. |\n| Section or file not found | Inspect the upstream spec\u002Fsource names; upstream may have renamed or removed the target. |\n| Overlay applies but output\u002Fbuild is wrong | Inspect `diff-sources` for an over-broad match, malformed replacement, or a dependency\u002Ffile change the overlay omitted. |\n\n## Choosing an overlay type\n\nMatch the change to the narrowest overlay type. Required fields are enforced when\nthe config loads, so a missing field fails fast rather than at apply time.\n\n### Spec overlays (structured `.spec` edits)\n\n| Type | Use for | Required |\n| --- | --- | --- |\n| `spec-add-tag` | add a tag; fails if it already exists | `tag`, `value` |\n| `spec-insert-tag` | add a tag next to its family (e.g. after the last `Source*`) | `tag`, `value` |\n| `spec-set-tag` | set a tag, replacing it if present or adding it if not | `tag`, `value` |\n| `spec-update-tag` | change an existing tag; fails if it is missing | `tag`, `value` |\n| `spec-remove-tag` | delete tag instances; without `value`, deletes every instance | `tag` |\n| `spec-prepend-lines` | insert lines at the top of a section (or the whole file) | `lines` |\n| `spec-append-lines` | insert lines at the end of a section (or the whole file) | `lines` |\n| `spec-search-replace` | regex replace within a section (or the whole spec) | `regex` |\n| `spec-remove-section` | delete a whole section | `section` |\n| `spec-remove-subpackage` | delete every section of a sub-package | `package` |\n| `patch-add` | add a `.patch` file and register it in the spec | `source` |\n| `patch-remove` | remove a patch and its spec references | `file` |\n\n### File overlays (loose non-spec files; never `.spec`)\n\n| Type | Use for | Required |\n| --- | --- | --- |\n| `file-prepend-lines` | prepend lines to a file | `file`, `lines` |\n| `file-search-replace` | regex replace in a file | `file`, `regex` |\n| `file-add` | copy in a new file; fails if it already exists | `file`, `source` |\n| `file-remove` | delete a file | `file` |\n| `file-rename` | rename a file in place | `file`, `replacement` |\n\n## Rules that trip people up\n\n- **`spec-remove-tag` without `value` removes every instance** of the named tag.\n  To remove one dependency, set both `tag` and the exact `value` to match:\n\n  ```toml\n  [[components.mypackage.overlays]]\n  description = \"Remove an unavailable build dependency\"\n  type = \"spec-remove-tag\"\n  tag = \"BuildRequires\"\n  value = \"unwanted-package\"\n  ```\n- **`section` is optional only** for `spec-prepend-lines`, `spec-append-lines`, and\n  `spec-search-replace` (omit it to target the whole spec). It is **required** for\n  `spec-remove-section`.\n- **`package` needs `section`** on the whole-file-capable overlays — a sub-package is\n  a sub-qualifier of a section. `spec-remove-subpackage` is the exception: it takes\n  `package` and rejects `section`.\n- **`replacement` is literal** — `$1`-style capture-group references are not expanded;\n  omit it to delete matched text.\n- **Quote `regex` as a TOML literal string** — write `regex = '\\.so$'`, not\n  `regex = \"\\.so$\"`. A basic (double-quoted) TOML string interprets backslash escapes, so\n  `\\s`, `\\.`, `\\d` and friends are mangled before the regex engine ever sees them; single\n  quotes keep the pattern verbatim.\n- **Anchor regex overlays to whole lines, and prefer macro toggles.** When\n  `spec-search-replace` is unavoidable, anchor the full line (for example,\n  `regex = '^%setup -q$'`) instead of matching a fragment, and combine several\n  near-identical patterns into one rather than stacking brittle overlays. If the\n  upstream spec already exposes a conditional such as `%if 0%{?rhel}` \u002F\n  `%if 0%{?fedora}` or a definable macro, set that macro instead of rewriting the\n  line with regex; the explicit toggle survives upstream changes more reliably.\n- **`spec-search-replace` matches one line at a time** — the pattern is applied to each\n  spec line independently, so it can never span a newline and `(?s)`\u002FDOTALL does nothing.\n  For a multi-line change use a structured spec overlay (`spec-remove-section`,\n  `spec-prepend-lines`\u002F`spec-append-lines`, etc.). `file-search-replace` is different: it\n  matches against the whole file, so multi-line patterns (and `(?s)`) work there.\n- **`file` is a glob** (`**` supported) for the multi-file file overlays; for `file-add`\n  and `file-rename` it is a single name, and `file-rename`'s `replacement` is a\n  filename only (not a path).\n- **`source` paths are relative** to the config that declares the overlay — the overlay\n  file when loaded via `overlay-files`, otherwise the component config.\n- **`file-add` lands beside the spec**, in the dist-git sources root — not inside the\n  extracted upstream tree. Adding a file there does not make the build use it; wire it in\n  with a `SourceN` tag plus `%prep`\u002F`%install` steps, or use `patch-add` to change tracked\n  sources.\n- **Don't rename the `Name:` tag** with `spec-update-tag`\u002F`spec-set-tag`. `%{name}` feeds\n  `Source*` URLs, `%setup -n`, and `%files` paths, so renaming it silently breaks those\n  references. Keep the spec `Name` aligned with the component instead.\n- To add a real `.patch` file (rather than an inline edit), use `patch-add`; it copies\n  the `source` into the component sources and registers a `PatchN` tag or `%patchlist`\n  entry.\n\n## Document intent with `metadata`\n\nGive non-trivial overlays a `metadata` table. It is documentation only — excluded from\nthe component fingerprint, so editing it never invalidates the build cache — but it\nrecords *why* the overlay exists and *when* it can be dropped. Every metadata block\nrequires `category`; pick the narrowest of:\n\n`upstream-backport`, `azl-pruning`, `azl-compatibility`, `azl-temp-workaround`,\n`azl-branding-policy`, `azl-disable-flaky-tests`, `azl-disable-unsupported-tests`,\n`azl-security-compliance`, `azl-release-management`, `azl-platform-adaptation`.\n\nIt also requires `upstream-status`: `upstreamed`, `upstreamable`,\n`needs-upstream-hook`, `inapplicable`, or `unknown`. Add `commits` and `bugs` as\n`{ url = \"https:\u002F\u002F...\" }` entries where they apply. `commits` is required for\n`upstream-backport`, whose status must be `upstreamed` or `upstreamable`. When several\noverlays share one provenance, put them in a per-file overlay document (`overlay-files`)\nwith a single file-level `[metadata]`.\n\nFor how to choose the right `category` and `upstream-status`, disambiguation tips, and\nthe TOML forms, read the `azldev-overlay-metadata` skill.\n\n## Full reference\n\nThe tables above are the working subset. For the exhaustive field rules, metadata\nconstraints, and the per-file overlay format, generate the machine-readable schema\nwith `azldev config generate-schema` (see the `ComponentOverlay` definition), or read\nazldev's overlays configuration reference.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n","# Working with overlays\n\nOverlays are **semantic patches** applied to a component's RPM spec and loose\nsource files at render time. They let you make targeted changes to an upstream\nspec without forking it. Prefer an overlay over hand-editing a rendered spec:\noverlays are re-applied on every render, so a manual edit to a rendered spec is\noverwritten.\n\n## The inner loop\n\nOverlays live in the component's TOML config — inline `[[components.\u003Cname>.overlays]]`\nentries, or per-file overlay documents referenced by the component's `overlay-files`\nglob. They apply **in order** and are **non-atomic**: if one fails part-way, the\noverlays before it stay applied.\n\n1. Add or edit the overlay in the component config.\n2. Re-render and inspect the result:\n\n   ```sh\n   azldev comp render -p \u003Cname>\n   ```\n\n   Read the rendered spec (under `specs\u002F`) to confirm the change\n   landed where you intended, and iterate until it is correct.\n3. Finalize the lock and changelog with the normal end-of-work refresh (see the\n   `azldev-update-component` skill): update the lock, commit, then re-render and amend.\n\nConfig errors reference the offending overlay by its `description`, so give every\noverlay a short, specific `description`.\n\n## Diagnose common failures\n\nStart with `azldev comp diff-sources -p \u003Cname>` to see the exact overlay effect.\nUse separate pre\u002Fpost `prep-sources` directories only when you need persistent trees\nfor deeper inspection.\n\n| Symptom | Likely cause and fix |\n| --- | --- |\n| `spec-add-tag`: tag already exists | Upstream already has the tag. Use `spec-set-tag`, or `spec-update-tag` when its prior existence is an invariant. |\n| `spec-search-replace`: no match | Inspect the current upstream line, check TOML regex quoting, and narrow the expression to the actual section\u002Fpackage. |\n| Section or file not found | Inspect the upstream spec\u002Fsource names; upstream may have renamed or removed the target. |\n| Overlay applies but output\u002Fbuild is wrong | Inspect `diff-sources` for an over-broad match, malformed replacement, or a dependency\u002Ffile change the overlay omitted. |\n\n## Choosing an overlay type\n\nMatch the change to the narrowest overlay type. Required fields are enforced when\nthe config loads, so a missing field fails fast rather than at apply time.\n\n### Spec overlays (structured `.spec` edits)\n\n| Type | Use for | Required |\n| --- | --- | --- |\n| `spec-add-tag` | add a tag; fails if it already exists | `tag`, `value` |\n| `spec-insert-tag` | add a tag next to its family (e.g. after the last `Source*`) | `tag`, `value` |\n| `spec-set-tag` | set a tag, replacing it if present or adding it if not | `tag`, `value` |\n| `spec-update-tag` | change an existing tag; fails if it is missing | `tag`, `value` |\n| `spec-remove-tag` | delete tag instances; without `value`, deletes every instance | `tag` |\n| `spec-prepend-lines` | insert lines at the top of a section (or the whole file) | `lines` |\n| `spec-append-lines` | insert lines at the end of a section (or the whole file) | `lines` |\n| `spec-search-replace` | regex replace within a section (or the whole spec) | `regex` |\n| `spec-remove-section` | delete a whole section | `section` |\n| `spec-remove-subpackage` | delete every section of a sub-package | `package` |\n| `patch-add` | add a `.patch` file and register it in the spec | `source` |\n| `patch-remove` | remove a patch and its spec references | `file` |\n\n### File overlays (loose non-spec files; never `.spec`)\n\n| Type | Use for | Required |\n| --- | --- | --- |\n| `file-prepend-lines` | prepend lines to a file | `file`, `lines` |\n| `file-search-replace` | regex replace in a file | `file`, `regex` |\n| `file-add` | copy in a new file; fails if it already exists | `file`, `source` |\n| `file-remove` | delete a file | `file` |\n| `file-rename` | rename a file in place | `file`, `replacement` |\n\n## Rules that trip people up\n\n- **`spec-remove-tag` without `value` removes every instance** of the named tag.\n  To remove one dependency, set both `tag` and the exact `value` to match:\n\n  ```toml\n  [[components.mypackage.overlays]]\n  description = \"Remove an unavailable build dependency\"\n  type = \"spec-remove-tag\"\n  tag = \"BuildRequires\"\n  value = \"unwanted-package\"\n  ```\n- **`section` is optional only** for `spec-prepend-lines`, `spec-append-lines`, and\n  `spec-search-replace` (omit it to target the whole spec). It is **required** for\n  `spec-remove-section`.\n- **`package` needs `section`** on the whole-file-capable overlays — a sub-package is\n  a sub-qualifier of a section. `spec-remove-subpackage` is the exception: it takes\n  `package` and rejects `section`.\n- **`replacement` is literal** — `$1`-style capture-group references are not expanded;\n  omit it to delete matched text.\n- **Quote `regex` as a TOML literal string** — write `regex = '\\.so$'`, not\n  `regex = \"\\.so$\"`. A basic (double-quoted) TOML string interprets backslash escapes, so\n  `\\s`, `\\.`, `\\d` and friends are mangled before the regex engine ever sees them; single\n  quotes keep the pattern verbatim.\n- **Anchor regex overlays to whole lines, and prefer macro toggles.** When\n  `spec-search-replace` is unavoidable, anchor the full line (for example,\n  `regex = '^%setup -q$'`) instead of matching a fragment, and combine several\n  near-identical patterns into one rather than stacking brittle overlays. If the\n  upstream spec already exposes a conditional such as `%if 0%{?rhel}` \u002F\n  `%if 0%{?fedora}` or a definable macro, set that macro instead of rewriting the\n  line with regex; the explicit toggle survives upstream changes more reliably.\n- **`spec-search-replace` matches one line at a time** — the pattern is applied to each\n  spec line independently, so it can never span a newline and `(?s)`\u002FDOTALL does nothing.\n  For a multi-line change use a structured spec overlay (`spec-remove-section`,\n  `spec-prepend-lines`\u002F`spec-append-lines`, etc.). `file-search-replace` is different: it\n  matches against the whole file, so multi-line patterns (and `(?s)`) work there.\n- **`file` is a glob** (`**` supported) for the multi-file file overlays; for `file-add`\n  and `file-rename` it is a single name, and `file-rename`'s `replacement` is a\n  filename only (not a path).\n- **`source` paths are relative** to the config that declares the overlay — the overlay\n  file when loaded via `overlay-files`, otherwise the component config.\n- **`file-add` lands beside the spec**, in the dist-git sources root — not inside the\n  extracted upstream tree. Adding a file there does not make the build use it; wire it in\n  with a `SourceN` tag plus `%prep`\u002F`%install` steps, or use `patch-add` to change tracked\n  sources.\n- **Don't rename the `Name:` tag** with `spec-update-tag`\u002F`spec-set-tag`. `%{name}` feeds\n  `Source*` URLs, `%setup -n`, and `%files` paths, so renaming it silently breaks those\n  references. Keep the spec `Name` aligned with the component instead.\n- To add a real `.patch` file (rather than an inline edit), use `patch-add`; it copies\n  the `source` into the component sources and registers a `PatchN` tag or `%patchlist`\n  entry.\n\n## Document intent with `metadata`\n\nGive non-trivial overlays a `metadata` table. It is documentation only — excluded from\nthe component fingerprint, so editing it never invalidates the build cache — but it\nrecords *why* the overlay exists and *when* it can be dropped. Every metadata block\nrequires `category`; pick the narrowest of:\n\n`upstream-backport`, `azl-pruning`, `azl-compatibility`, `azl-temp-workaround`,\n`azl-branding-policy`, `azl-disable-flaky-tests`, `azl-disable-unsupported-tests`,\n`azl-security-compliance`, `azl-release-management`, `azl-platform-adaptation`.\n\nIt also requires `upstream-status`: `upstreamed`, `upstreamable`,\n`needs-upstream-hook`, `inapplicable`, or `unknown`. Add `commits` and `bugs` as\n`{ url = \"https:\u002F\u002F...\" }` entries where they apply. `commits` is required for\n`upstream-backport`, whose status must be `upstreamed` or `upstreamable`. When several\noverlays share one provenance, put them in a per-file overlay document (`overlay-files`)\nwith a single file-level `[metadata]`.\n\nFor how to choose the right `category` and `upstream-status`, disambiguation tips, and\nthe TOML forms, read the `azldev-overlay-metadata` skill.\n\n## Full reference\n\nThe tables above are the working subset. For the exhaustive field rules, metadata\nconstraints, and the per-file overlay format, generate the machine-readable schema\nwith `azldev config generate-schema` (see the `ComponentOverlay` definition), or read\nazldev's overlays configuration reference.\n\nGenerated by `azldev docs agent`; do not hand-edit.\n",{"name":5,"description":7},"4.0","431ad36a7a827e8ec414e96ae75517ec1ded115d",".agents\u002Fskills\u002Fazldev-overlays",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Fazurelinux --skill azldev-overlays",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Fazurelinux --skill azldev-overlays",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Fazurelinux --skill azldev-overlays","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev-overlays\u002FSKILL.md",true,[],[71,99,124,148,169,192],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":42},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[83,84,41,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"skill metrics","metrics","azure","monitor","azure-monitor","aks","disk","node","query","azure monitor","false","readiness","CPU","disk usage","usage","for",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":42},"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",[105],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"triage","skill mass triage","diagnose","produce","batch","file","json","parallel","results","use","build","summary","triggers","with","root","root cause","when",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":134,"publishedAt":42},"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",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[135,136,137,138,139,140,141,90,142,143,117,91,93,144,145,146,147,97,98],"skill kql queries","kql","queries","kubernetes","analytics","logs","templates","container","log","events","via","activity","errors",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":42},"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",[154],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[107,156,157,158,159,160,161,140,162,163,164,116,143,165,166,119,167,168,98,122,123],"skill koji triage","web","root cause analysis","tasks","packages","ui","analysis","broken","fetch","task","info","failure analysis","web ui",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":42},"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",[175],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[177,178,179,33,180,109,85,181,182,183,116,184,185,186,187,119,188,189,190,98,191,123],"skill fedora mirror injections","fedora","mirror","linux","pr","bootstrap","injection","dependency","bug","infra","entries","missing","argument","updates","backfill",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":42},"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",[198],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[200,201,202,139,85,203,204,88,205,143,118,206,93,207,208,123],"skill deployment context","deployment","context","yaml","monitoring","workspace","discover","name","cluster"]