---

name: kubernetes-namespace-triage description: "Triage one unhealthy Kubernetes namespace using workload, service, and pod detail evidence."

Kubernetes Namespace Triage

Triage one unhealthy Kubernetes namespace using workload, service, and pod detail evidence.

Required Aident Actions

• <action-tag>cli:kubectl:get_deployments</action-tag> (required inputs: namespace): List deployments in a namespace (JSON).
• <action-tag>cli:kubectl:get_pods</action-tag> (required inputs: namespace): List pods in a namespace (JSON).
• <action-tag>cli:kubectl:get_services</action-tag> (required inputs: namespace): List services in a namespace (JSON).
• <action-tag>cli:kubectl:describe_pod</action-tag> (required inputs: pod_name, namespace): Describe a specific pod.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or rAction · Get Deploymentsexecution.

Workflow

1. Confirm the requested outcome, source materiaAction · Get Podsceptance criteria.
2. Apply the source-derived guidance below to cAction · Get Servicesnvoking an Action.
3. Select only the Aident Actions whose documented Action · Describe Podo not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Start with namespace-wide state, then describe only the pods implicated by observed failures.
• Separate confirmed conditions from hypotheses that require logs or cluster events.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.