debug-buttercup

Name: debug-buttercup
Availability: InStock
Author: rohanbhatia27

Diagnose Buttercup CRS issues on Kubernetes using kubectl commands.

1|Updated Apr 7, 2026

Search Tags:#Kubernetes #diagnosis #Buttercup CRS #Kubernetes debugging #Kubernetes monitoring

Ready to run

npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill debug-buttercup-rohanbhatia27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-buttercup
Source: https://github.com/rohanbhatia27/rohanstutoring-redesign/tree/main/.agents/skills/debug-buttercup
Command: npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill debug-buttercup-rohanbhatia27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive set of commands and scripts to diagnose and troubleshoot common issues in the Buttercup Cyber Reasoning System (CRS) running on Kubernetes.

Core Features & Use Cases

Pod Status & Events: Offers commands to check pod status, events, and resource usage.
Redis Health: Includes commands to inspect Redis health, queue depths, and task registry.
Queue Inspection: Allows checking of queue lengths and consumer group lags.
Health Checks: Provides instructions for checking pod health files.
Telemetry: Offers guidance on using OpenTelemetry and Signoz for distributed tracing.
Volume and Storage: Includes commands to inspect PVC status and disk usage.
Deployment Config Verification: Offers commands to verify Helm values and pod resource limits.
Service-Specific Debugging: Provides quick references for debugging specific services.
Diagnostic Script: Runs an automated triage snapshot to collect essential information.

Quick Start

Run the diagnose.sh script to collect essential diagnostic information for the Buttercup CRS.

Frequently Asked Questions about debug-buttercup

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

FAQPage Schema

How do I diagnose issues in the Buttercup CRS on Kubernetes?▼

To diagnose Buttercup CRS issues on Kubernetes, run the diagnose.sh script to collect a triage snapshot, or manually check pod status, events, resource usage, Redis health, and queue depths using kubectl commands.

What is the best way to check Redis health and queue depths in a Kubernetes cluster?▼

Checking Redis health and queue depths in Kubernetes involves inspecting the Redis instance, task registry, and consumer group lags. This Skill provides specific commands to monitor these metrics for the Buttercup CRS.

Can I use kubectl commands to inspect PVC status and disk usage for Buttercup CRS?▼

Yes, you can use kubectl commands to inspect PVC status and disk usage. This Skill includes commands to verify volume storage, Helm values, and pod resource limits for the Buttercup Cyber Reasoning System.

Does this Kubernetes debugging tool support distributed tracing for Buttercup CRS?▼

Distributed tracing for Buttercup CRS is supported through OpenTelemetry and Signoz. This Skill offers guidance on using these tools to monitor telemetry and trace issues across your Kubernetes deployment.

What do I need to troubleshoot Buttercup Cyber Reasoning System pods on Kubernetes?▼

To troubleshoot Buttercup CRS pods, you need access to the Kubernetes cluster and familiarity with kubectl commands. This allows you to check pod health files, events, and resource limits effectively.

Why are Buttercup CRS queue lengths increasing and how do I debug consumer group lag?▼

Debugging increasing queue lengths and consumer group lag in Buttercup CRS requires inspecting Redis health and queue depths. This Skill provides the necessary commands to check these metrics and diagnose task processing bottlenecks.