メニュー
Kubernetes cluster access via loctl (kubectl, helm, stern). Use when checking pod health, inspecting resources, or streaming logs from pods.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Coordinate full-strength Claude and Codex teammates in detached tmux sessions with external stall monitoring, durable file channels, completion markers, and resumable conversations. Use when work can be divided into independent tasks, when the user asks for teammates or subagents, or when delegating research, implementation, frontend, review, or long-running work across model accounts.
Coordinate full-strength Claude and Codex teammates in detached tmux sessions with external stall monitoring, durable file channels, completion markers, and resumable conversations. Use when work can be divided into independent tasks, when the user asks for teammates or subagents, or when delegating research, implementation, frontend, review, or long-running work across model accounts.
Drive the kautopilot binary as a thin in-session controller: ticket/free-form request → merge-ready PRs across one or more repos, as ONE flat session. The binary owns all state, prompts, and next-step decisions; this skill just runs what `kautopilot next` yields. Use when running /kautopilot.
Drive the kautopilot binary as a thin in-session controller: ticket/free-form request → merge-ready PRs across one or more repos, as ONE flat session. The binary owns all state, prompts, and next-step decisions; this skill just runs what `kautopilot next` yields. Use when running /kautopilot.
Iteratively review-and-resolve the current changes using parallel subagent reviewers across multiple lenses (bugs, quality, completion), looping until every reviewer is satisfied. Use when running /floop, or when asked to deeply review and harden a diff until all critiques are addressed.
Give the user a fast, ADHD/dyslexia-friendly recap of the current work or conversation — the outcome first, then what (if anything) you need from them. Use when running /summary, or when asked to "summarize", "recap", "where are we", "catch me up", or "what do you need from me".
| name | liftoff-kubernetes |
| description | Kubernetes cluster access via loctl (kubectl, helm, stern). Use when checking pod health, inspecting resources, or streaming logs from pods. |
The qa/ops prefix does not scope Kubernetes access -- it only routes observability/ArgoCD endpoints. kubectl/helm/stern reach the same set of contexts under either prefix; the --context flag is what selects the cluster.
List the authoritative context set with:
loctl qa list contexts
Context name patterns and their purposes:
| Pattern | Purpose |
|---|---|
eks-qa-* | QA |
eks-prod-* | Production (us-east, ap-northeast) |
eks-stage-* | Staging |
eks-ops-* | Operations (Mimir, Grafana, monitoring) |
eks-data-* | Data platform |
eks-dashboard-* | Dashboards |
eks-llm-* | LLM workloads |
KUBECONFIG points at a generated agent config bound to the role in ~/.loctl/config.yaml (default vungle2-EngineeringRole; check/switch with loctl role)AWS_PROFILE is set to that same configured role -- server-side safety is exactly that role's RBAC, nothing more--help flag anywhere in the args bypasses the verb checkexec, debug, port-forward, and wait are allowed but are not read-only -- they can mutate state; use them only for read-only investigation, never to change anythingqa or ops prefix is required -- no default--context -- there is no defaultloctl qa list contextsAllowed verbs: get, describe, logs, top, explain, api-resources, api-versions, version, config, auth, cluster-info, debug, exec, port-forward, wait, diff
Warning: exec/debug/port-forward/wait can mutate -- investigation only, never mutation.
loctl qa kubectl --context eks-qa-us-east-1b get nodes
loctl ops kubectl --context eks-prod-us-east-1b get pods -n api
loctl ops kubectl --context eks-ops-us-east-1c get pods -n grafana
loctl ops kubectl --context eks-ops-us-east-1c get events -n grafana --sort-by=.lastTimestamp
loctl qa kubectl --context eks-qa-us-east-1b top pods -n grafana --sort-by=cpu
Allowed commands: get, history, list, ls, show, status, template, version, search, repo, env, diff
Note: uses --kube-context (not --context). The configured role may lack RBAC for helm list/status in some namespaces.
loctl qa helm --kube-context eks-qa-us-east-1b show values argocd
loctl ops helm --kube-context eks-ops-us-east-1c show values mimir
loctl qa stern --context eks-qa-us-east-1b my-app -n default --tail=10
loctl ops stern --context eks-prod-us-east-1b my-app -n api --tail=10