debug-buttercup

Automate Buttercup CRS debugging on Kubernetes with kubectl diagnostics.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Ramprasad4121/srp --skill debug-buttercup-ramprasad4121
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-buttercup
Source: https://github.com/Ramprasad4121/srp/tree/main/skills-repos/trailofbits/plugins/debug-buttercup/skills/debug-buttercup
Command: npx skills add https://github.com/Ramprasad4121/srp --skill debug-buttercup-ramprasad4121

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues within the Buttercup Cyber Reasoning System (CRS) deployed on Kubernetes, addressing common problems like pod crashes, resource exhaustion, and service failures.

Core Features & Use Cases

  • Triage and Diagnosis: Quickly assess the health of CRS pods and identify the root cause of failures using kubectl commands.
  • Log Analysis: Efficiently parse logs from multiple pods to pinpoint error messages and understand failure sequences.
  • Resource Monitoring: Check CPU, memory, and disk usage on pods and nodes to identify performance bottlenecks.
  • Redis and Queue Inspection: Diagnose issues with the central Redis instance and monitor the status of various task queues.
  • Use Case: When multiple services in the crs namespace are in a CrashLoopBackOff state, use this Skill to systematically check pod events, resource limits, and Redis connectivity to find the underlying cause, such as a disk pressure issue on the node or a stalled Redis instance.

Quick Start

Run the automated diagnostic script to collect a snapshot of the Buttercup CRS environment.

Frequently Asked Questions about debug-buttercup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a CrashLoopBackOff state for Buttercup CRS pods on Kubernetes?

Debug Buttercup CRS pods in CrashLoopBackOff on Kubernetes by running automated kubectl diagnostic commands to check pod status, events, and resource limits to identify the underlying failure cause.

How do I diagnose Redis queue backlogs and AOF cascades in a Kubernetes namespace?

Diagnose Redis queue backlogs and AOF cascades in a Kubernetes namespace by inspecting the central Redis instance health and monitoring task queue statuses to pinpoint stalled streams and disk saturation issues.

Why are my Kubernetes pods getting OOM killed during Buttercup CRS operations?

Kubernetes pods get OOM killed during Buttercup CRS operations when resource limits are exceeded; automate resource monitoring on pods and nodes to identify memory exhaustion and resolve CPU or disk bottlenecks.

What do I need to troubleshoot Buttercup CRS service failures on Kubernetes?

Troubleshooting Buttercup CRS service failures on Kubernetes requires kubectl access to the cluster and knowledge of Buttercup's internal services and Redis streams to parse pod logs and diagnose connectivity issues.

Can I use kubectl to find disk saturation issues affecting Buttercup pods in the crs namespace?

Use kubectl to find disk saturation issues affecting Buttercup pods in the crs namespace by executing diagnostic scripts that monitor resource usage and parse pod events to detect node disk pressure.