AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

azure-diagnostics

Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-diagnostics at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 42

troubleshooting/aks/optional-aks-operations.md

Optional AKS Operations Handoff

Baseline AKS intake, Azure-side health checks, Kubernetes evidence, and safe remediation guidance remain in this guide. Offer the sibling aks-skills plugin only when one focused workflow materially fits the current incident.

Select the focused skill

| Skill | Exact boundary | |-------|----------------| | aks-troubleshooting | A live AKS incident in any scope bucket, including workload crashes, node, networking, ingress, upgrade, or scaling problems, where deeper target-bound operational investigation would help. An application-level cause does not exclude an AKS workload incident. | | aks-known-issues | An exact, fully qualified catalog signature is present. A quota error, unqualified capacity symptom, or incomplete wrapper is not enough; an exact fully qualified catalog capacity signature remains eligible. | | aks-network-capture | The customer explicitly requests packet capture and separately approves the bounded pcap plan. Generic network troubleshooting stays here. | | aks-gpu-inference | An existing AKS GPU or inference deployment has a Day-2 incident. Initial setup stays in airunway-aks-setup. |

Host and consent flow

  1. Use the host-provided available-skill inventory, or an approved read-only host capability query. Do not require a CLI just to inspect availability and do not guess from literal skill-name prefixes.
  2. If the selected skill is present, invoke it through the host-native skill mechanism.
  3. If it is missing and useful, explain the focused benefit and ask before using the host-supported plugin manager. Do not silently install the plugin, add it as a dependency, or bypass host policy. After installation, confirm the selected skill appears in the host's available-skill inventory before invoking it. If the host activates newly installed components only in a new session or after a restart, say so, continue this baseline guide now, and report the focused skill as installed but not yet active rather than used.
  4. If installation is declined or unsupported, continue this baseline guide with available reads or supplied evidence. Do not repeatedly prompt, stop without help, or pretend the optional skill executed.

Installing the plugin does not approve resource changes or packet capture. Follow the selected workflow's separate execution and mutation approvals.