Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Triage restarting pods (crs namespace) v1.0.0

Use this resource to diagnose pods that restart or fail in cascade in the crs namespace

New

  • 370 downloads
  • 121 likes
  • 147 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install kubernetes-crash-triage

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent follows a triage routine: pod status, events, warnings, then logs from the previous container instance that crashed. You get the likely cause, resource limits compared with intended values and the commands to run. The failure-pattern reference file it cites is not included.

Mostly picked by

Updated November 2, 2026

Card for the “Triage restarting pods (crs namespace)” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: triage routine and kubectl commands
  • SKILL.md: restart, OOMKilled and Redis cases

Good fit for

  • Several services restart at once in the crs namespace
  • A pod goes OOMKilled and you are looking for the limit at fault

Not for

    Tags

    • kubernetes
    • diagnosis
    • oomkilled
    • crashloop
    • redis

    About

    You say

    “Diagnose why the queue service keeps restarting in the crs namespace.”

    Card for the “Triage restarting pods (crs namespace)” skill

    Skill published by sickn33 under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to diagnose pods that restart or fail in cascade in the crs namespace
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1.1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md11.6 KB

    Origin and licence

    Listed unmodified

    Author
    sickn33
    Source
    github.com/sickn33/agentic-awesome-skills/tree/e9809578fd426a284af017c5db99f8eb6628e6ca/skills/debug-buttercup
    Licence
    MIT

    Notice

    « debug-buttercup » (sickn33, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.