pod-troubleshooting

Debug pod crashes, CrashLoopBackOff, ImagePullBackOff, OOMKilled, init container errors, and EBUSY config failures. Use when: Pods are not Running, containers are restarting, init containers fail, or the pod is Running but the application inside isn't working. Don't use when: Flux reconciliation is the problem (use flux-debugging). Don't use for registry-level image issues (use zot-registry). Don't use for Ceph/storage failures (use storage-ops). Don't use for deploying changes (use gitops-deploy). Outputs: Diagnosis of why the pod is unhealthy, with specific cause identified and remediation steps.

Jump to install

Repository: rajsinghtech/openclaw-workspace
Last source activity: February 12, 2026 at 15:14
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/rajsinghtech/openclaw-workspace --skill pod-troubleshooting

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

code-review

Structured PR review — security scan, correctness, consistency, style. Covers diff analysis, comment posting via gh, and priority-based finding reports. Use when: A PR needs review, someone asks for code feedback, or changes need security/correctness validation before merge. Also use for pre-commit review of your own changes. Don't use when: The issue is a runtime pod failure (use pod-troubleshooting), a Flux reconciliation error (use flux-debugging), or a CI build failure (use ci-diagnosis). Don't use for architecture-level design discussions (use architecture-design instead). Outputs: Review comment posted on the PR via `gh pr review`, or a structured findings report grouped by severity (Critical/High/Medium/Low).

2026-02-20

openspec-workflow

Spec-driven development workflow — proposals, requirements, design docs, task breakdowns, and implementation using the OpenSpec framework. Use when: Starting a new feature or change that needs planning, someone says "I want to build X", creating proposals or specs, breaking down requirements into tasks, or transitioning from planning to implementation. Don't use when: Debugging or troubleshooting (use appropriate troubleshooting skill). Don't use for Kubernetes manifest changes (use pr-workflow). Don't use for reviewing existing code (use code-review). Outputs: OpenSpec change folder with proposal.md, specs/, design.md, and tasks.md. Implementation follows directly from tasks.md.

2026-02-20

session-review

Analyze agent sessions for tool failures, retry patterns, knowledge gaps, context limits, and config drift. Use when: Running periodic session reviews (cron), investigating agent reliability issues, looking for recurring failure patterns, or identifying workspace improvements from real usage. This is the primary skill for Robert's review cron job. Don't use when: You're making changes to fix issues (use workspace-improvement for that). Don't use for live debugging of a current issue (use the appropriate troubleshooting skill). Don't use for code review of PRs (use code-review). Outputs: Session analysis report with categorized findings (tool failures, retries, knowledge gaps, config drift), severity ratings, and proposed fixes. Written to /tmp/outputs/session-review.md for handoff.

2026-02-20

View all from this repository

name	Pod Troubleshooting
description	Debug pod crashes, CrashLoopBackOff, ImagePullBackOff, OOMKilled, init container errors, and EBUSY config failures. Use when: Pods are not Running, containers are restarting, init containers fail, or the pod is Running but the application inside isn't working. Don't use when: Flux reconciliation is the problem (use flux-debugging). Don't use for registry-level image issues (use zot-registry). Don't use for Ceph/storage failures (use storage-ops). Don't use for deploying changes (use gitops-deploy). Outputs: Diagnosis of why the pod is unhealthy, with specific cause identified and remediation steps.
requires	["kubectl"]