[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AWACE1JWAWT2VQ767EAQG":3,"skill-same:01M69AWACE1JWAWT2VQ767EAQG":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},"01M69AWACE1JWAWT2VQ767EAQG","azldev-comp-toml",null,"Read this before authoring, editing, or reviewing a *.comp.toml file; do not work from memory. Explains the azldev component definition format and review workflow, covering component structure, spec sources, build config, release calculation, render options, file organization, overlay hygiene, stale files, disabled tests, and testing verification. Triggers include comp.toml, component config, review component, component hygiene, spec source, upstream-distro, build defines, release calculation, includes.","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-comp-toml\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],"comp","azldev comp toml","azldev","toml","files","overlay","definition","calculation","render","sources","triggers","tests","upstream","do","testing","editing","file","config","component","workflow","memory","spec","review","2026-11-10 10:12:30",false,"---\nname: azldev-comp-toml\ndescription: \"Read this before authoring, editing, or reviewing a *.comp.toml file; do not work from memory. Explains the azldev component definition format and review workflow, covering component structure, spec sources, build config, release calculation, render options, file organization, overlay hygiene, stale files, disabled tests, and testing verification. Triggers include comp.toml, component config, review component, component hygiene, spec source, upstream-distro, build defines, release calculation, includes.\"\n---\n\n# Component definition files (`*.comp.toml`)\n\nA component definition tells azldev where a package's spec comes from and how to\ncustomize it for your distro. Every component lives under `[components.\u003Cname>]`.\n\nGet the authoritative, always-current field list from the schema:\n\n```sh\nazldev config generate-schema\n```\n\n## Structure\n\nA bare entry inherits everything from your distro's defaults — most upstream packages\nneed nothing more:\n\n```toml\n[components.curl]\n```\n\nAdd sub-tables only for what you change. The fields you will reach for most:\n\n| Field | Purpose |\n| --- | --- |\n| `spec` | where the spec comes from (see below) |\n| `overlays` \u002F `overlay-files` | targeted spec\u002Fsource edits (see the `azldev-overlays` skill) |\n| `build.defines` \u002F `build.with` \u002F `build.without` | RPM macro and bcond build tweaks |\n| `release.calculation` | how the `Release` tag is managed |\n| `render.skip-file-filter` | rendering edge-case escape hatch |\n\n## Spec source\n\nThe `spec` field selects where the spec is fetched from. When omitted, the component\ninherits the distro default (normally an upstream import).\n\n```toml\n# Upstream import (the usual case) — inherits the distro's upstream version\n[components.curl]\n\n# Upstream, but pinned to a specific upstream distro\u002Fversion\n[components.curl]\nspec = { type = \"upstream\", upstream-distro = { name = \"fedora\", version = \"rawhide\" } }\n\n# Upstream package whose name differs from the component name\n[components.mydistro-rpm-config]\nspec = { type = \"upstream\", upstream-name = \"redhat-rpm-config\" }\n\n# Local spec that lives in your repo (not imported from an upstream distro)\n[components.mydistro-release]\nspec = { type = \"local\", path = \"mydistro-release.spec\" }\n```\n\n## Build configuration\n\n```toml\n[components.mypackage.build]\ndefines = { rhel = \"11\" }      # override RPM macros\nwith = [\"feature_x\"]            # enable %bcond_with conditionals\nwithout = [\"plugin_rhsm\"]       # disable %bcond_with conditionals\n```\n\n## Release calculation\n\n`release.calculation` controls the `Release:` tag. There are four modes:\n\n- `auto` (default) — leave `%autorelease` unchanged; otherwise bump a static\n  integer Release once for each fingerprint-derived synthetic change.\n- `autorelease` — force `%autorelease` handling (use when auto-detection misreads a\n  spec that wraps `%autorelease` in a conditional).\n- `static` — require a non-`%autorelease` static release. The default legacy\n  calculation supports only an integer, `integer%{?dist}`, or `integer%{dist}`;\n  other forms require `manual` or an overlay.\n- `manual` — you own the `Release:` value. Use this only when render fails with a\n  \"non-standard Release tag\" error. **A `manual` component is not bumped by the\n  render\u002Fcommit\u002Famend cycle, so increment its release yourself in the same change**\n  (see the `azldev-update-component` skill).\n\n```toml\n[components.mypackage.release]\ncalculation = \"manual\"\n```\n\nThe temporary `--rpmdev-bumpspec` flag on `comp build`, `comp render`, and\n`comp prepare-sources` opts into transactional host handling while Azure Linux\nmigrates. Only that path requires `rpmdev-bumpspec`, `rpmdev-packager`, `rpm`,\n`rpmspec`, and Python with its RPM module. It preserves the fixed team\nidentity\u002Fcomment\u002Fdatestamp and strict source-EVR transaction checks; locks and\nsynthetic history still determine the number and order of bumps. Without the\nflag, no bumpspec runtime discovery occurs and the legacy static calculation is\nused. `%autorelease` behavior is unchanged on either path.\n\n## Render configuration\n\n`render.skip-file-filter = true` keeps all source and patch files during render.\nazldev normally prunes files not referenced by the rendered spec; set this only for\nthe rare spec whose `Source`\u002F`Patch` filenames use macros the filter cannot expand.\n\n## File organization\n\n- **Inline** — put simple, customization-free components directly in a shared config\n  file (e.g. `[components.jq]`).\n- **Dedicated** — give a component its own `\u003Cname>\u002F\u003Cname>.comp.toml` once it needs\n  overlays, build config, or a local spec. Rule of thumb: anything more than\n  `[components.\u003Cname>]` earns a dedicated file.\n- A parent config picks up dedicated files through an `includes` glob, for example\n  `includes = [\"**\u002F*.comp.toml\"]`.\n\n## Review checklist\n\nStart with `azldev comp list -p \u003Cname> -q -O json`, then use\n`azldev comp query -p \u003Cname> -q -O json` when the review needs parsed spec details.\nFor a change review, focus on the diff while checking enough surrounding context to\nensure it fits the component and repository conventions.\n\n- **Organization:** The component follows the repository's inline-versus-dedicated-file\n  convention; its name matches upstream or sets `spec.upstream-name`; no stale or\n  orphaned component files remain.\n- **Spec source:** The default upstream source is preferred. Pins explain why they are\n  needed, and local specs are used only when overlays cannot express the change.\n- **Overlays:** Every overlay explains why it exists. Prefer structured overlay types\n  over regex; scope unavoidable `spec-search-replace` expressions by section and, when\n  applicable, package, and use TOML literal strings. `spec-search-replace` cannot span\n  lines. Remove overlays that upstream has made unnecessary. See the `azldev-overlays` skill.\n- **Build config:** Defines and bcond overrides are necessary and correspond to the\n  spec. If `build.check.skip = true`, require a specific `build.check.skip_reason` and\n  verify that fixing the tests is impractical; skipped `%check` is a last resort.\n- **Release mode:** `auto` is the default. Force `autorelease` or `static` only when\n  auto-detection is wrong. Use `manual` only for a non-standard release tag, and verify\n  the component increments its release itself.\n- **Generated state:** The lock matches the final component inputs, and rendered output\n  contains the intended changes without unrelated drift.\n- **Testing:** Changes that can affect RPM output were built and smoke-tested in a mock\n  chroot. Organization, comment, or documentation-only metadata edits do not require a\n  rebuild when the resolved component inputs are unchanged.\n\nReport findings by severity: errors for correctness or required-policy violations,\nwarnings for maintainability risks, and info for optional improvements. Prefer small,\nactionable fixes over unrelated cleanup.\n\n## Documenting changes\n\nAdd a TOML comment explaining *why* a non-obvious field is set (a version pin, a\nworkaround), and link the upstream commit or bug when the change is based on one. For\noverlays, use the overlay `metadata` table instead (see the `azldev-overlays` skill).\n\nGenerated by `azldev docs agent`; do not hand-edit.\n","# Component definition files (`*.comp.toml`)\n\nA component definition tells azldev where a package's spec comes from and how to\ncustomize it for your distro. Every component lives under `[components.\u003Cname>]`.\n\nGet the authoritative, always-current field list from the schema:\n\n```sh\nazldev config generate-schema\n```\n\n## Structure\n\nA bare entry inherits everything from your distro's defaults — most upstream packages\nneed nothing more:\n\n```toml\n[components.curl]\n```\n\nAdd sub-tables only for what you change. The fields you will reach for most:\n\n| Field | Purpose |\n| --- | --- |\n| `spec` | where the spec comes from (see below) |\n| `overlays` \u002F `overlay-files` | targeted spec\u002Fsource edits (see the `azldev-overlays` skill) |\n| `build.defines` \u002F `build.with` \u002F `build.without` | RPM macro and bcond build tweaks |\n| `release.calculation` | how the `Release` tag is managed |\n| `render.skip-file-filter` | rendering edge-case escape hatch |\n\n## Spec source\n\nThe `spec` field selects where the spec is fetched from. When omitted, the component\ninherits the distro default (normally an upstream import).\n\n```toml\n# Upstream import (the usual case) — inherits the distro's upstream version\n[components.curl]\n\n# Upstream, but pinned to a specific upstream distro\u002Fversion\n[components.curl]\nspec = { type = \"upstream\", upstream-distro = { name = \"fedora\", version = \"rawhide\" } }\n\n# Upstream package whose name differs from the component name\n[components.mydistro-rpm-config]\nspec = { type = \"upstream\", upstream-name = \"redhat-rpm-config\" }\n\n# Local spec that lives in your repo (not imported from an upstream distro)\n[components.mydistro-release]\nspec = { type = \"local\", path = \"mydistro-release.spec\" }\n```\n\n## Build configuration\n\n```toml\n[components.mypackage.build]\ndefines = { rhel = \"11\" }      # override RPM macros\nwith = [\"feature_x\"]            # enable %bcond_with conditionals\nwithout = [\"plugin_rhsm\"]       # disable %bcond_with conditionals\n```\n\n## Release calculation\n\n`release.calculation` controls the `Release:` tag. There are four modes:\n\n- `auto` (default) — leave `%autorelease` unchanged; otherwise bump a static\n  integer Release once for each fingerprint-derived synthetic change.\n- `autorelease` — force `%autorelease` handling (use when auto-detection misreads a\n  spec that wraps `%autorelease` in a conditional).\n- `static` — require a non-`%autorelease` static release. The default legacy\n  calculation supports only an integer, `integer%{?dist}`, or `integer%{dist}`;\n  other forms require `manual` or an overlay.\n- `manual` — you own the `Release:` value. Use this only when render fails with a\n  \"non-standard Release tag\" error. **A `manual` component is not bumped by the\n  render\u002Fcommit\u002Famend cycle, so increment its release yourself in the same change**\n  (see the `azldev-update-component` skill).\n\n```toml\n[components.mypackage.release]\ncalculation = \"manual\"\n```\n\nThe temporary `--rpmdev-bumpspec` flag on `comp build`, `comp render`, and\n`comp prepare-sources` opts into transactional host handling while Azure Linux\nmigrates. Only that path requires `rpmdev-bumpspec`, `rpmdev-packager`, `rpm`,\n`rpmspec`, and Python with its RPM module. It preserves the fixed team\nidentity\u002Fcomment\u002Fdatestamp and strict source-EVR transaction checks; locks and\nsynthetic history still determine the number and order of bumps. Without the\nflag, no bumpspec runtime discovery occurs and the legacy static calculation is\nused. `%autorelease` behavior is unchanged on either path.\n\n## Render configuration\n\n`render.skip-file-filter = true` keeps all source and patch files during render.\nazldev normally prunes files not referenced by the rendered spec; set this only for\nthe rare spec whose `Source`\u002F`Patch` filenames use macros the filter cannot expand.\n\n## File organization\n\n- **Inline** — put simple, customization-free components directly in a shared config\n  file (e.g. `[components.jq]`).\n- **Dedicated** — give a component its own `\u003Cname>\u002F\u003Cname>.comp.toml` once it needs\n  overlays, build config, or a local spec. Rule of thumb: anything more than\n  `[components.\u003Cname>]` earns a dedicated file.\n- A parent config picks up dedicated files through an `includes` glob, for example\n  `includes = [\"**\u002F*.comp.toml\"]`.\n\n## Review checklist\n\nStart with `azldev comp list -p \u003Cname> -q -O json`, then use\n`azldev comp query -p \u003Cname> -q -O json` when the review needs parsed spec details.\nFor a change review, focus on the diff while checking enough surrounding context to\nensure it fits the component and repository conventions.\n\n- **Organization:** The component follows the repository's inline-versus-dedicated-file\n  convention; its name matches upstream or sets `spec.upstream-name`; no stale or\n  orphaned component files remain.\n- **Spec source:** The default upstream source is preferred. Pins explain why they are\n  needed, and local specs are used only when overlays cannot express the change.\n- **Overlays:** Every overlay explains why it exists. Prefer structured overlay types\n  over regex; scope unavoidable `spec-search-replace` expressions by section and, when\n  applicable, package, and use TOML literal strings. `spec-search-replace` cannot span\n  lines. Remove overlays that upstream has made unnecessary. See the `azldev-overlays` skill.\n- **Build config:** Defines and bcond overrides are necessary and correspond to the\n  spec. If `build.check.skip = true`, require a specific `build.check.skip_reason` and\n  verify that fixing the tests is impractical; skipped `%check` is a last resort.\n- **Release mode:** `auto` is the default. Force `autorelease` or `static` only when\n  auto-detection is wrong. Use `manual` only for a non-standard release tag, and verify\n  the component increments its release itself.\n- **Generated state:** The lock matches the final component inputs, and rendered output\n  contains the intended changes without unrelated drift.\n- **Testing:** Changes that can affect RPM output were built and smoke-tested in a mock\n  chroot. Organization, comment, or documentation-only metadata edits do not require a\n  rebuild when the resolved component inputs are unchanged.\n\nReport findings by severity: errors for correctness or required-policy violations,\nwarnings for maintainability risks, and info for optional improvements. Prefer small,\nactionable fixes over unrelated cleanup.\n\n## Documenting changes\n\nAdd a TOML comment explaining *why* a non-obvious field is set (a version pin, a\nworkaround), and link the upstream commit or bug when the change is based on one. For\noverlays, use the overlay `metadata` table instead (see the `azldev-overlays` skill).\n\nGenerated by `azldev docs agent`; do not hand-edit.\n",{"name":5,"description":7},"4.0","431ad36a7a827e8ec414e96ae75517ec1ded115d",".agents\u002Fskills\u002Fazldev-comp-toml",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-comp-toml",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Fazurelinux --skill azldev-comp-toml",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Fazurelinux --skill azldev-comp-toml","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fazurelinux\u002Fblob\u002F4.0\u002F.agents\u002Fskills\u002Fazldev-comp-toml\u002FSKILL.md",true,[],[71,99,122,146,167,190],{"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,39,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,35,112,113,114,115,116,117,29,118,119,120,121],"triage","skill mass triage","diagnose","produce","batch","json","parallel","results","use","build","summary","with","root","root cause","when",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":132,"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",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[133,134,135,136,137,138,139,90,140,141,116,91,93,142,143,144,145,97,98],"skill kql queries","kql","queries","kubernetes","analytics","logs","templates","container","log","events","via","activity","errors",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"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",[152],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[107,154,155,156,157,158,159,138,160,161,162,115,141,163,164,29,165,166,98,120,121],"skill koji triage","web","root cause analysis","tasks","packages","ui","analysis","broken","fetch","task","info","failure analysis","web ui",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"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",[173],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[175,176,177,40,178,109,85,179,180,181,115,182,183,184,185,29,186,187,188,98,189,121],"skill fedora mirror injections","fedora","mirror","linux","pr","bootstrap","injection","dependency","bug","infra","entries","missing","argument","updates","backfill",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"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",[196],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[198,199,200,137,85,201,202,88,203,141,117,204,93,205,206,121],"skill deployment context","deployment","context","yaml","monitoring","workspace","discover","name","cluster"]