Debug Buttercup
Skill Verified ActiveDebugs the Buttercup CRS (Cyber Reasoning System) running on Kubernetes. Use when diagnosing pod crashes, restart loops, Redis failures, resource pressure, disk saturation, DinD issues, or any service misbehavior in the crs namespace. Covers triage, log analysis, queue inspection, and common failure patterns for: redis, fuzzer-bot, coverage-bot, seed-gen, patcher, build-bot, scheduler, task-server, task-downloader, program-model, litellm, dind, tracer-bot, merger-bot, competition-api, pov-reproducer, scratch-cleaner, registry-cache, image-preloader, ui.
To help users quickly diagnose and resolve issues within Buttercup CRS deployments on Kubernetes by providing automated diagnostics and actionable troubleshooting steps.
Features
- Automated triage script for Kubernetes.
- Detailed guidance on diagnosing common Buttercup CRS failures.
- Analysis of pod status, events, and resource utilization.
- Specific debugging steps for Redis, queues, and core services.
Use Cases
- Use when pods in the `crs` namespace are crashing or exhibiting unexpected behavior.
- Use when diagnosing cascading failures originating from a shared dependency like Redis.
- Use when investigating resource pressure or disk saturation issues within the `crs` namespace.
- Use to inspect queue depths and task progression when services appear stalled.
Non-Goals
- Deploying or upgrading Buttercup CRS (use Helm and deployment guides).
- Debugging issues outside the `crs` Kubernetes namespace.
- General Kubernetes administration or debugging unrelated to Buttercup CRS.
Documentation
- info:Configuration & parameter referenceWhile the script uses environment variables like `BUTTERCUP_NAMESPACE`, these are documented in the script's usage comment, and explicit parameters are not a primary feature of this diagnostic script.
Installation
First, add the marketplace
/plugin marketplace add trailofbits/skills/plugin install debug-buttercup@trailofbitsQuality Score
VerifiedTrust Signals
Similar Extensions
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Ctx Doctor
100Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
LangSmith Observability
99LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.