AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 5.4k
Forks
714

01 前言 Front Matter

name
skill-deployment-context
description
[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.
user-invocable
false
disable-model-invocation
false

02 资源文件 4

03 SKILL.md 正文

Koji Deployment Context Discovery

Always resolve context before running queries. Never assume resource names.

Step 1: Locate deployment_summary.yaml (if available)

This file is typically generated by the Koji deployment pipeline (e.g., as an Azure DevOps pipeline artifact) and stored at the repository root as ./deployment_summary.yaml. It should contain resource_group, aks_cluster_name, subscription_id, and monitoring resource names/IDs.

  • If the file exists, open it and use its values as the source of truth for the deployment context.
  • If the file does not exist (e.g., in a new or manually provisioned environment), skip to Steps 2–4 and resolve the deployment context directly from Azure.
  • If the user needs help obtaining this file, offer to run az commands to discover the values and generate it for them.

Step 2: If subscription is missing

Run: az account show --query id -o tsv

Step 3: If deployment does not match the summary

Ask the user for the resource group or AKS cluster name.

Step 4: Discover monitoring resources dynamically

az monitor log-analytics workspace list --resource-group <RG> -o table
az resource list --resource-group <RG> --resource-type Microsoft.Monitor/accounts -o table
az resource list --resource-group <RG> --resource-type Microsoft.Dashboard/grafana -o table

Naming convention

Resources follow <prefix>-koji-*:

  • Resource group: <prefix>-koji-rg-<suffix>
  • AKS cluster: <prefix>-koji-aks
  • Log Analytics: <prefix>-koji-logs
  • Azure Monitor: <prefix>-koji-monitor
  • Grafana: <prefix>-koji-grafana

MCP tools for context discovery

Tool Purpose
aks_cluster_get List/get AKS cluster details
aks_nodepool_get List/get node pool details
monitor_table_list List tables in a Log Analytics workspace

Prerequisites: Node.js (npx) and an active az login session.

04 同仓库更多 Skills

microsoft
microsoft/azurelinux

skill-metrics

[Skill] metrics, azure-monitor, aks - Query Azure Monitor metrics for Koji AKS node CPU, memory, disk usage, and pod readiness.

Skill与智能体开发
★ 5.4k
microsoft
microsoft/azurelinux

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.

Skill与智能体开发
★ 5.4k
microsoft
microsoft/azurelinux

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.

运维与部署Skill与智能体开发
★ 5.4k
microsoft
microsoft/azurelinux

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.

Skill与智能体开发
★ 5.4k
microsoft
microsoft/azurelinux

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 / 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.

Skill与智能体开发
★ 5.4k
microsoft
microsoft/azurelinux

skill-aks-health

[Skill] aks, aks health, cluster health, node pool, activity logs - Inspect Koji AKS cluster health, node pool status, autoscaling, activity logs, deployment failures, and Azure control-plane operations.

Skill与智能体开发
★ 5.4k