kubernetes-axi
Use kubernetes-axi to discover, inspect, deploy, debug, scale, roll out, expose, and clean up Kubernetes workloads through safe TOON CLI workflows.
Works with
--- name: kubernetes-axi description: Use kubernetes-axi to discover, inspect, deploy, debug, scale, roll out, expose, and clean up Kubernetes workloads through safe TOON CLI workflows. license: MIT --- # kubernetes-axi Use `kubernetes-axi` when a task involves kubectl, manifests, Helm, Kustomize, pods, deployments, services, rollouts, logs, events, or cluster debugging. Run `npx -y kubernetes-axi` for live context. Use `npx -y kubernetes-axi doctor` before cluster work. Discover targets with `npx -y kubernetes-axi discover`. Plan before mutating: `npx -y kubernetes-axi plan --target <id> --environment <name>`. Mutations require `--execute`. Destructive deletes also require `--confirm <exact-name>`.
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
