Is azure-kubernetes-automatic-readiness safe?
Grade A, 100/100. No meaningful risk found.
Aazure-kubernetes-automatic-readiness
.github/plugins/azure-skills/skills/azure-kubernetes/azure-kubernetes-automatic-readiness100/100 · No meaningful risk foundNo security findings
azure-kubernetes-automatic-readiness
.github/plugins/azure-skills/skills/azure-kubernetes/azure-kubernetes-automatic-readiness- Content hash
- sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
- Files
- 0
- Quality
- 100/100
Security findings
None of the 30 rules matched.
Files in this skill
Questions about azure-kubernetes-automatic-readiness
- Is azure-kubernetes-automatic-readiness safe to install?
- Our scanner gave azure-kubernetes-automatic-readiness grade A (100/100): no meaningful risk found. None of the 30 security rules matched. Static analysis cannot prove safety, so pin the reviewed revision with a lockfile.
- How do I install azure-kubernetes-automatic-readiness in Claude Code or Codex?
- Run skillhash add github:microsoft/azure-skills/.github/plugins/azure-skills/skills/azure-kubernetes/azure-kubernetes-automatic-readiness. It downloads the exact commit, checks the grade against your policy, writes skills.lock and installs it into .claude/skills and .agents/skills.
- What happens if azure-kubernetes-automatic-readiness changes upstream?
- Its content hash changes. skillhash verify fails in CI until you review the new version and update the lock. With a watch, you also get an alert.
More from microsoft/azure-skills
- A
azure-advisor
1.6kmicrosoft/azure-skills
Use Azure Advisor recommendations. WHEN: "show Advisor recommendations", "service retirements", "update recommendation status". DO NOT USE FOR: fixes or remediation (use azure-advisor-actionability).
No security findings - A
aks-gpu-inference
1.6kmicrosoft/azure-skills
Diagnose Day-2 AKS GPU and KAITO incidents using profile-aware, read-only evidence. WHEN: 'Insufficient nvidia.com/gpu', GPU pod Pending, model-load OOM, DCGM/VRAM, KAITO Workspace not ready, or GPU autoscaling. DO NOT USE FOR: setup (airunway-aks-setup), non-GPU incidents (aks-troubleshooting), standalone VM quota (azure-quotas), or generic cost (cost-analysis or cost-optimization from the optional azure-cost plugin).
No security findings - A
prepare
1.6kmicrosoft/azure-skills
No description in SKILL.md.
No security findings - A
aks-known-issues
1.6kmicrosoft/azure-skills
Lookup documented AKS fixes only when the prompt includes an exact catalog signature and all of its qualifiers: VMCannotFitEphemeralOSDisk; NodePoolMcVersionIncompatible; 'NodeImageVersion is not accepted'; AKS SkuNotAvailable with size, location, and zone; ZonalAllocationFailed with insufficient zone capacity; OverconstrainedAllocationRequest with listed constraints; nested AKS vmssCSE/CSE VMExtensionError_OutboundConnFail, VMExtensionError_K8SAPIServerConnFail, or VMExtensionError_K8SAPIServerDNSLookupFail; or AllocationFailed with the full cataloged internal-error or insufficient-regional-capacity message. Never use for quota errors, code-only or bare wrappers, generic symptoms, incomplete signatures, or failures outside AKS; use aks-troubleshooting or azure-diagnostics.
No security findings - A
aks-network-capture
1.6kmicrosoft/azure-skills
Collects bounded packet captures from AKS nodes and Azure network configuration for wire-level evidence. WHEN: "capture packets on an AKS node", "take a pcap", "run tcpdump on AKS", "prove where packets drop". Use for explicit packet-capture intent after read-only diagnostics, not general AKS connectivity or ingress troubleshooting.
No security findings - A
aks-troubleshooting
1.6kmicrosoft/azure-skills
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 (use aks-gpu-inference); cluster creation or provisioning (use azure-kubernetes); cost (use cost-analysis from the optional azure-cost plugin); pod rightsizing (use azure-kubernetes); a fully qualified documented AKS signature with every required nested qualifier (use aks-known-issues); standalone failures on non-AKS Azure resources (use azure-diagnostics). Unqualified errors and open-ended incidents stay here only for AKS.
No security findings - A
scaffold
1.6kmicrosoft/azure-skills
No description in SKILL.md.
No security findings - A
azure-advisor-actionability
1.6kmicrosoft/azure-skills
Remediate Azure Advisor recommendations. WHEN: "fix Advisor recommendation".
No security findings