aks-troubleshooting
Verdict safe, but 3 findings (1 medium, 2 low), mainly unauthorized tool use, data exfiltration. Most recent scan 2026-10-22.
Second scanner: NVIDIA SkillSpector
The two scanners disagree: Cisco found nothing and SkillSpector says do not install. One of them has a blind spot here; read the skill before trusting either. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or InsufficientVCPUQuota, upgrade stuck, spot or zone disruption, a bare VMExtensionProvisioningError or AllocationFailed wrapper, an uncataloged capacity symptom, or 'investigate my AKS cluster'. DO NOT USE FOR: packet capture (use aks-network-capture); GPU or model-serving issues…
- Package
- 20 files, 128 KB
- SKILL.md
- 1547 words, 9 sections
- Code
- Shell (2)
- License
- MIT
SKILL.md covers: AKS Troubleshooting · Operating rules · Route by symptom · Scripts · AKS-specific gotchas · Log discipline · Deep diagnostics · Report · Reference
Findings
MEDIUM Bash: tainted data flows to dangerous sink Data Exfiltrationbehavioral
Variable $FQDN (line 2) flows to `curl` at line 4.
references/symptom-map.md:222
curl -k -Iv "https://$FQDN" # TCP + TLS connectivityLOW Script contacts a destination the documentation never mentions Unauthorized Tool Usestatic
Script contacts or configures 'aka.ms' but the skill documentation never visibly mentions it. Undocumented network destinations can indicate behaviour the manifest and description do not disclose.
scripts/pod-deep-dive.sh:25
LOW Script contacts a destination the documentation never mentions Unauthorized Tool Usestatic
Script contacts or configures 'jqlang.github.io' but the skill documentation never visibly mentions it. Undocumented network destinations can indicate behaviour the manifest and description do not disclose.
scripts/pod-deep-dive.sh:33
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 12 KB |
general-diagnostics.md | doc | 2.8 KB |
load-balancer-and-ingress.md | doc | 7.5 KB |
network-policy.md | doc | 1.2 KB |
networking.md | doc | 14 KB |
node-issues.md | doc | 15 KB |
pod-failures.md | doc | 8.0 KB |
spot-and-zone-issues.md | doc | 2.5 KB |
upgrade-operations.md | doc | 4.5 KB |
references/api-server-webhooks-tunnel.md | doc | 6.3 KB |
references/auto-upgrade-evidence.md | doc | 4.4 KB |
references/azure-mcp.md | doc | 2.5 KB |
references/azure-network-path.md | doc | 7.6 KB |
references/command-flows.md | doc | 3.3 KB |
references/inspektor-gadget.md | doc | 8.1 KB |
references/report-template.md | doc | 1.1 KB |
references/structured-input-modes.md | doc | 3.8 KB |
references/symptom-map.md | doc | 15 KB |
scripts/cluster-snapshot.sh | script | 3.8 KB |
scripts/pod-deep-dive.sh | script | 3.6 KB |
External hosts referenced
learn.microsoft.com aka.ms jqlang.github.io kubernetes.io
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Environment variables referenced
AKS_SUBSCRIPTION_ID INSTANCE_ID PROVIDER_ID COREDNS_SOURCE_SUBNET_ID NODE_NIC_ID COREDNS_ROUTE_TABLE_ID COREDNS_SUBNET_NSG_ID COREDNS_NODE_NIC_ID AZURE_HTTP_USER_AGENT COREDNS_PROVIDER_ID SOURCE_SUBNET_ID VMSS_VM_ID AKS_ARTIFACTS_DIR COREDNS_INSTANCE_ID COREDNS_NODE_SUBNET_ID COREDNS_POD_SUBNET_ID DEST_PORT NODE_SUBNET_ID POD_SUBNET_ID
Package contents recorded 2026-10-22 at commit f49ac319a7d3. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/microsoft/azure-skills
- Raw scan result: microsoft-azure-skills-github-plugins-aks-skills-skills-aks-troubleshooting-scan.json
- Badge for your README:
 - Request a re-scan