[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CV17SAWATJB0N2BWQD47N":3,"skill-same:01M75CV17SAWATJB0N2BWQD47N":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CV17SAWATJB0N2BWQD47N","debug-buttercup",null,"Debugs 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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdebug-buttercup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: debug-buttercup\ndescription: >\n  Debugs the Buttercup CRS (Cyber Reasoning System) running on Kubernetes.\n  Use when diagnosing pod crashes, restart loops, Redis failures, resource pressure,\n  disk saturation, DinD issues, or any service misbehavior in the crs namespace.\n  Covers triage, log analysis, queue inspection, and common failure patterns\n  for: redis, fuzzer-bot, coverage-bot, seed-gen, patcher, build-bot, scheduler,\n  task-server, task-downloader, program-model, litellm, dind, tracer-bot,\n  merger-bot, competition-api, pov-reproducer, scratch-cleaner, registry-cache,\n  image-preloader, ui.\n---\n\n# Debug Buttercup\n\n## When to Use\n\n- Pods in the `crs` namespace are in CrashLoopBackOff, OOMKilled, or restarting\n- Multiple services restart simultaneously (cascade failure)\n- Redis is unresponsive or showing AOF warnings\n- Queues are growing but tasks are not progressing\n- Nodes show DiskPressure, MemoryPressure, or PID pressure\n- Build-bot cannot reach the Docker daemon (DinD failures)\n- Scheduler is stuck and not advancing task state\n- Health check probes are failing unexpectedly\n- Deployed Helm values don't match actual pod configuration\n\n## When NOT to Use\n\n- Deploying or upgrading Buttercup (use Helm and deployment guides)\n- Debugging issues outside the `crs` Kubernetes namespace\n- Performance tuning that doesn't involve a failure symptom\n\n## Namespace and Services\n\nAll pods run in namespace `crs`. Key services:\n\n| Layer | Services |\n|-------|----------|\n| Infra | redis, dind, litellm, registry-cache |\n| Orchestration | scheduler, task-server, task-downloader, scratch-cleaner |\n| Fuzzing | build-bot, fuzzer-bot, coverage-bot, tracer-bot, merger-bot |\n| Analysis | patcher, seed-gen, program-model, pov-reproducer |\n| Interface | competition-api, ui |\n\n## Triage Workflow\n\nAlways start with triage. Run these three commands first:\n\n```bash\n# 1. Pod status - look for restarts, CrashLoopBackOff, OOMKilled\nkubectl get pods -n crs -o wide\n\n# 2. Events - the timeline of what went wrong\nkubectl get events -n crs --sort-by='.lastTimestamp'\n\n# 3. Warnings only - filter the noise\nkubectl get events -n crs --field-selector type=Warning --sort-by='.lastTimestamp'\n```\n\nThen narrow down:\n\n```bash\n# Why did a specific pod restart? Check Last State Reason (OOMKilled, Error, Completed)\nkubectl describe pod -n crs \u003Cpod-name> | grep -A8 'Last State:'\n\n# Check actual resource limits vs intended\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.containers[0].resources}'\n\n# Crashed container's logs (--previous = the container that died)\nkubectl logs -n crs \u003Cpod-name> --previous --tail=200\n\n# Current logs\nkubectl logs -n crs \u003Cpod-name> --tail=200\n```\n\n### Historical vs Ongoing Issues\n\nHigh restart counts don't necessarily mean an issue is ongoing -- restarts accumulate over a pod's lifetime. Always distinguish:\n- `--tail` shows the end of the log buffer, which may contain old messages. Use `--since=300s` to confirm issues are actively happening now.\n- `--timestamps` on log output helps correlate events across services.\n- Check `Last State` timestamps in `describe pod` to see when the most recent crash actually occurred.\n\n### Cascade Detection\n\nWhen many pods restart around the same time, check for a shared-dependency failure before investigating individual pods. The most common cascade: Redis goes down -> every service gets `ConnectionError`\u002F`ConnectionRefusedError` -> mass restarts. Look for the same error across multiple `--previous` logs -- if they all say `redis.exceptions.ConnectionError`, debug Redis, not the individual services.\n\n## Log Analysis\n\n```bash\n# All replicas of a service at once\nkubectl logs -n crs -l app=fuzzer-bot --tail=100 --prefix\n\n# Stream live\nkubectl logs -n crs -l app.kubernetes.io\u002Fname=redis -f\n\n# Collect all logs to disk (existing script)\nbash deployment\u002Fcollect-logs.sh\n```\n\n## Resource Pressure\n\n```bash\n# Per-pod CPU\u002Fmemory\nkubectl top pods -n crs\n\n# Node-level\nkubectl top nodes\n\n# Node conditions (disk pressure, memory pressure, PID pressure)\nkubectl describe node \u003Cnode> | grep -A5 Conditions\n\n# Disk usage inside a pod\nkubectl exec -n crs \u003Cpod> -- df -h\n\n# What's eating disk\nkubectl exec -n crs \u003Cpod> -- sh -c 'du -sh \u002Fcorpus\u002F* 2>\u002Fdev\u002Fnull'\nkubectl exec -n crs \u003Cpod> -- sh -c 'du -sh \u002Fscratch\u002F* 2>\u002Fdev\u002Fnull'\n```\n\n## Redis Debugging\n\nRedis is the backbone. When it goes down, everything cascades.\n\n```bash\n# Redis pod status\nkubectl get pods -n crs -l app.kubernetes.io\u002Fname=redis\n\n# Redis logs (AOF warnings, OOM, connection issues)\nkubectl logs -n crs -l app.kubernetes.io\u002Fname=redis --tail=200\n\n# Connect to Redis CLI\nkubectl exec -n crs \u003Credis-pod> -- redis-cli\n\n# Inside redis-cli: key diagnostics\nINFO memory          # used_memory_human, maxmemory\nINFO persistence     # aof_enabled, aof_last_bgrewrite_status, aof_delayed_fsync\nINFO clients         # connected_clients, blocked_clients\nINFO stats           # total_connections_received, rejected_connections\nCLIENT LIST          # see who's connected\nDBSIZE               # total keys\n\n# AOF configuration\nCONFIG GET appendonly     # is AOF enabled?\nCONFIG GET appendfsync   # fsync policy: everysec, always, or no\n\n# What is \u002Fdata mounted on? (disk vs tmpfs matters for AOF performance)\n```\n\n```bash\nkubectl exec -n crs \u003Credis-pod> -- mount | grep \u002Fdata\nkubectl exec -n crs \u003Credis-pod> -- du -sh \u002Fdata\u002F\n```\n\n### Queue Inspection\n\nButtercup uses Redis streams with consumer groups. Queue names:\n\n| Queue | Stream Key |\n|-------|-----------|\n| Build | fuzzer_build_queue |\n| Build Output | fuzzer_build_output_queue |\n| Crash | fuzzer_crash_queue |\n| Confirmed Vulns | confirmed_vulnerabilities_queue |\n| Download Tasks | orchestrator_download_tasks_queue |\n| Ready Tasks | tasks_ready_queue |\n| Patches | patches_queue |\n| Index | index_queue |\n| Index Output | index_output_queue |\n| Traced Vulns | traced_vulnerabilities_queue |\n| POV Requests | pov_reproducer_requests_queue |\n| POV Responses | pov_reproducer_responses_queue |\n| Delete Task | orchestrator_delete_task_queue |\n\n```bash\n# Check stream length (pending messages)\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XLEN fuzzer_build_queue\n\n# Check consumer group lag\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XINFO GROUPS fuzzer_build_queue\n\n# Check pending messages per consumer\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XPENDING fuzzer_build_queue build_bot_consumers - + 10\n\n# Task registry size\nkubectl exec -n crs \u003Credis-pod> -- redis-cli HLEN tasks_registry\n\n# Task state counts\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD cancelled_tasks\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD succeeded_tasks\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD errored_tasks\n```\n\nConsumer groups: `build_bot_consumers`, `orchestrator_group`, `patcher_group`, `index_group`, `tracer_bot_group`.\n\n## Health Checks\n\nPods write timestamps to `\u002Ftmp\u002Fhealth_check_alive`. The liveness probe checks file freshness.\n\n```bash\n# Check health file freshness\nkubectl exec -n crs \u003Cpod> -- stat \u002Ftmp\u002Fhealth_check_alive\nkubectl exec -n crs \u003Cpod> -- cat \u002Ftmp\u002Fhealth_check_alive\n```\n\nIf a pod is restart-looping, the health check file is likely going stale because the main process is blocked (e.g. waiting on Redis, stuck on I\u002FO).\n\n## Telemetry (OpenTelemetry \u002F Signoz)\n\nAll services export traces and metrics via OpenTelemetry. If Signoz is deployed (`global.signoz.deployed: true`), use its UI for distributed tracing across services.\n\n```bash\n# Check if OTEL is configured\nkubectl exec -n crs \u003Cpod> -- env | grep OTEL\n\n# Verify Signoz pods are running (if deployed)\nkubectl get pods -n platform -l app.kubernetes.io\u002Fname=signoz\n```\n\nTraces are especially useful for diagnosing slow task processing, identifying which service in a pipeline is the bottleneck, and correlating events across the scheduler -> build-bot -> fuzzer-bot chain.\n\n## Volume and Storage\n\n```bash\n# PVC status\nkubectl get pvc -n crs\n\n# Check if corpus tmpfs is mounted, its size, and backing type\nkubectl exec -n crs \u003Cpod> -- mount | grep corpus_tmpfs\nkubectl exec -n crs \u003Cpod> -- df -h \u002Fcorpus_tmpfs 2>\u002Fdev\u002Fnull\n\n# Check if CORPUS_TMPFS_PATH is set\nkubectl exec -n crs \u003Cpod> -- env | grep CORPUS\n\n# Full disk layout - what's on real disk vs tmpfs\nkubectl exec -n crs \u003Cpod> -- df -h\n```\n\n`CORPUS_TMPFS_PATH` is set when `global.volumes.corpusTmpfs.enabled: true`. This affects fuzzer-bot, coverage-bot, seed-gen, and merger-bot.\n\n### Deployment Config Verification\n\nWhen behavior doesn't match expectations, verify Helm values actually took effect:\n\n```bash\n# Check a pod's actual resource limits\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.containers[0].resources}'\n\n# Check a pod's actual volume definitions\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.volumes}'\n```\n\nHelm values template typos (e.g. wrong key names) silently fall back to chart defaults. If deployed resources don't match the values template, check for key name mismatches.\n\n## Service-Specific Debugging\n\nFor detailed per-service symptoms, root causes, and fixes, see [references\u002Ffailure-patterns.md](references\u002Ffailure-patterns.md).\n\nQuick reference:\n\n- **DinD**: `kubectl logs -n crs -l app=dind --tail=100` -- look for docker daemon crashes, storage driver errors\n- **Build-bot**: check build queue depth, DinD connectivity, OOM during compilation\n- **Fuzzer-bot**: corpus disk usage, CPU throttling, crash queue backlog\n- **Patcher**: LiteLLM connectivity, LLM timeout, patch queue depth\n- **Scheduler**: the central brain -- `kubectl logs -n crs -l app=scheduler --tail=-1 --prefix | grep \"WAIT_PATCH_PASS\\|ERROR\\|SUBMIT\"`\n\n## Diagnostic Script\n\nRun the automated triage snapshot:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fdiagnose.sh\n```\n\nPass `--full` to also dump recent logs from all pods:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fdiagnose.sh --full\n```\n\nThis collects pod status, events, resource usage, Redis health, and queue depths in one pass.\n","# Debug Buttercup\n\n## When to Use\n\n- Pods in the `crs` namespace are in CrashLoopBackOff, OOMKilled, or restarting\n- Multiple services restart simultaneously (cascade failure)\n- Redis is unresponsive or showing AOF warnings\n- Queues are growing but tasks are not progressing\n- Nodes show DiskPressure, MemoryPressure, or PID pressure\n- Build-bot cannot reach the Docker daemon (DinD failures)\n- Scheduler is stuck and not advancing task state\n- Health check probes are failing unexpectedly\n- Deployed Helm values don't match actual pod configuration\n\n## When NOT to Use\n\n- Deploying or upgrading Buttercup (use Helm and deployment guides)\n- Debugging issues outside the `crs` Kubernetes namespace\n- Performance tuning that doesn't involve a failure symptom\n\n## Namespace and Services\n\nAll pods run in namespace `crs`. Key services:\n\n| Layer | Services |\n|-------|----------|\n| Infra | redis, dind, litellm, registry-cache |\n| Orchestration | scheduler, task-server, task-downloader, scratch-cleaner |\n| Fuzzing | build-bot, fuzzer-bot, coverage-bot, tracer-bot, merger-bot |\n| Analysis | patcher, seed-gen, program-model, pov-reproducer |\n| Interface | competition-api, ui |\n\n## Triage Workflow\n\nAlways start with triage. Run these three commands first:\n\n```bash\n# 1. Pod status - look for restarts, CrashLoopBackOff, OOMKilled\nkubectl get pods -n crs -o wide\n\n# 2. Events - the timeline of what went wrong\nkubectl get events -n crs --sort-by='.lastTimestamp'\n\n# 3. Warnings only - filter the noise\nkubectl get events -n crs --field-selector type=Warning --sort-by='.lastTimestamp'\n```\n\nThen narrow down:\n\n```bash\n# Why did a specific pod restart? Check Last State Reason (OOMKilled, Error, Completed)\nkubectl describe pod -n crs \u003Cpod-name> | grep -A8 'Last State:'\n\n# Check actual resource limits vs intended\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.containers[0].resources}'\n\n# Crashed container's logs (--previous = the container that died)\nkubectl logs -n crs \u003Cpod-name> --previous --tail=200\n\n# Current logs\nkubectl logs -n crs \u003Cpod-name> --tail=200\n```\n\n### Historical vs Ongoing Issues\n\nHigh restart counts don't necessarily mean an issue is ongoing -- restarts accumulate over a pod's lifetime. Always distinguish:\n- `--tail` shows the end of the log buffer, which may contain old messages. Use `--since=300s` to confirm issues are actively happening now.\n- `--timestamps` on log output helps correlate events across services.\n- Check `Last State` timestamps in `describe pod` to see when the most recent crash actually occurred.\n\n### Cascade Detection\n\nWhen many pods restart around the same time, check for a shared-dependency failure before investigating individual pods. The most common cascade: Redis goes down -> every service gets `ConnectionError`\u002F`ConnectionRefusedError` -> mass restarts. Look for the same error across multiple `--previous` logs -- if they all say `redis.exceptions.ConnectionError`, debug Redis, not the individual services.\n\n## Log Analysis\n\n```bash\n# All replicas of a service at once\nkubectl logs -n crs -l app=fuzzer-bot --tail=100 --prefix\n\n# Stream live\nkubectl logs -n crs -l app.kubernetes.io\u002Fname=redis -f\n\n# Collect all logs to disk (existing script)\nbash deployment\u002Fcollect-logs.sh\n```\n\n## Resource Pressure\n\n```bash\n# Per-pod CPU\u002Fmemory\nkubectl top pods -n crs\n\n# Node-level\nkubectl top nodes\n\n# Node conditions (disk pressure, memory pressure, PID pressure)\nkubectl describe node \u003Cnode> | grep -A5 Conditions\n\n# Disk usage inside a pod\nkubectl exec -n crs \u003Cpod> -- df -h\n\n# What's eating disk\nkubectl exec -n crs \u003Cpod> -- sh -c 'du -sh \u002Fcorpus\u002F* 2>\u002Fdev\u002Fnull'\nkubectl exec -n crs \u003Cpod> -- sh -c 'du -sh \u002Fscratch\u002F* 2>\u002Fdev\u002Fnull'\n```\n\n## Redis Debugging\n\nRedis is the backbone. When it goes down, everything cascades.\n\n```bash\n# Redis pod status\nkubectl get pods -n crs -l app.kubernetes.io\u002Fname=redis\n\n# Redis logs (AOF warnings, OOM, connection issues)\nkubectl logs -n crs -l app.kubernetes.io\u002Fname=redis --tail=200\n\n# Connect to Redis CLI\nkubectl exec -n crs \u003Credis-pod> -- redis-cli\n\n# Inside redis-cli: key diagnostics\nINFO memory          # used_memory_human, maxmemory\nINFO persistence     # aof_enabled, aof_last_bgrewrite_status, aof_delayed_fsync\nINFO clients         # connected_clients, blocked_clients\nINFO stats           # total_connections_received, rejected_connections\nCLIENT LIST          # see who's connected\nDBSIZE               # total keys\n\n# AOF configuration\nCONFIG GET appendonly     # is AOF enabled?\nCONFIG GET appendfsync   # fsync policy: everysec, always, or no\n\n# What is \u002Fdata mounted on? (disk vs tmpfs matters for AOF performance)\n```\n\n```bash\nkubectl exec -n crs \u003Credis-pod> -- mount | grep \u002Fdata\nkubectl exec -n crs \u003Credis-pod> -- du -sh \u002Fdata\u002F\n```\n\n### Queue Inspection\n\nButtercup uses Redis streams with consumer groups. Queue names:\n\n| Queue | Stream Key |\n|-------|-----------|\n| Build | fuzzer_build_queue |\n| Build Output | fuzzer_build_output_queue |\n| Crash | fuzzer_crash_queue |\n| Confirmed Vulns | confirmed_vulnerabilities_queue |\n| Download Tasks | orchestrator_download_tasks_queue |\n| Ready Tasks | tasks_ready_queue |\n| Patches | patches_queue |\n| Index | index_queue |\n| Index Output | index_output_queue |\n| Traced Vulns | traced_vulnerabilities_queue |\n| POV Requests | pov_reproducer_requests_queue |\n| POV Responses | pov_reproducer_responses_queue |\n| Delete Task | orchestrator_delete_task_queue |\n\n```bash\n# Check stream length (pending messages)\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XLEN fuzzer_build_queue\n\n# Check consumer group lag\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XINFO GROUPS fuzzer_build_queue\n\n# Check pending messages per consumer\nkubectl exec -n crs \u003Credis-pod> -- redis-cli XPENDING fuzzer_build_queue build_bot_consumers - + 10\n\n# Task registry size\nkubectl exec -n crs \u003Credis-pod> -- redis-cli HLEN tasks_registry\n\n# Task state counts\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD cancelled_tasks\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD succeeded_tasks\nkubectl exec -n crs \u003Credis-pod> -- redis-cli SCARD errored_tasks\n```\n\nConsumer groups: `build_bot_consumers`, `orchestrator_group`, `patcher_group`, `index_group`, `tracer_bot_group`.\n\n## Health Checks\n\nPods write timestamps to `\u002Ftmp\u002Fhealth_check_alive`. The liveness probe checks file freshness.\n\n```bash\n# Check health file freshness\nkubectl exec -n crs \u003Cpod> -- stat \u002Ftmp\u002Fhealth_check_alive\nkubectl exec -n crs \u003Cpod> -- cat \u002Ftmp\u002Fhealth_check_alive\n```\n\nIf a pod is restart-looping, the health check file is likely going stale because the main process is blocked (e.g. waiting on Redis, stuck on I\u002FO).\n\n## Telemetry (OpenTelemetry \u002F Signoz)\n\nAll services export traces and metrics via OpenTelemetry. If Signoz is deployed (`global.signoz.deployed: true`), use its UI for distributed tracing across services.\n\n```bash\n# Check if OTEL is configured\nkubectl exec -n crs \u003Cpod> -- env | grep OTEL\n\n# Verify Signoz pods are running (if deployed)\nkubectl get pods -n platform -l app.kubernetes.io\u002Fname=signoz\n```\n\nTraces are especially useful for diagnosing slow task processing, identifying which service in a pipeline is the bottleneck, and correlating events across the scheduler -> build-bot -> fuzzer-bot chain.\n\n## Volume and Storage\n\n```bash\n# PVC status\nkubectl get pvc -n crs\n\n# Check if corpus tmpfs is mounted, its size, and backing type\nkubectl exec -n crs \u003Cpod> -- mount | grep corpus_tmpfs\nkubectl exec -n crs \u003Cpod> -- df -h \u002Fcorpus_tmpfs 2>\u002Fdev\u002Fnull\n\n# Check if CORPUS_TMPFS_PATH is set\nkubectl exec -n crs \u003Cpod> -- env | grep CORPUS\n\n# Full disk layout - what's on real disk vs tmpfs\nkubectl exec -n crs \u003Cpod> -- df -h\n```\n\n`CORPUS_TMPFS_PATH` is set when `global.volumes.corpusTmpfs.enabled: true`. This affects fuzzer-bot, coverage-bot, seed-gen, and merger-bot.\n\n### Deployment Config Verification\n\nWhen behavior doesn't match expectations, verify Helm values actually took effect:\n\n```bash\n# Check a pod's actual resource limits\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.containers[0].resources}'\n\n# Check a pod's actual volume definitions\nkubectl get pod -n crs \u003Cpod-name> -o jsonpath='{.spec.volumes}'\n```\n\nHelm values template typos (e.g. wrong key names) silently fall back to chart defaults. If deployed resources don't match the values template, check for key name mismatches.\n\n## Service-Specific Debugging\n\nFor detailed per-service symptoms, root causes, and fixes, see [references\u002Ffailure-patterns.md](references\u002Ffailure-patterns.md).\n\nQuick reference:\n\n- **DinD**: `kubectl logs -n crs -l app=dind --tail=100` -- look for docker daemon crashes, storage driver errors\n- **Build-bot**: check build queue depth, DinD connectivity, OOM during compilation\n- **Fuzzer-bot**: corpus disk usage, CPU throttling, crash queue backlog\n- **Patcher**: LiteLLM connectivity, LLM timeout, patch queue depth\n- **Scheduler**: the central brain -- `kubectl logs -n crs -l app=scheduler --tail=-1 --prefix | grep \"WAIT_PATCH_PASS\\|ERROR\\|SUBMIT\"`\n\n## Diagnostic Script\n\nRun the automated triage snapshot:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fdiagnose.sh\n```\n\nPass `--full` to also dump recent logs from all pods:\n\n```bash\nbash {baseDir}\u002Fscripts\u002Fdiagnose.sh --full\n```\n\nThis collects pod status, events, resource usage, Redis health, and queue depths in one pass.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fdebug-buttercup",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill debug-buttercup",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill debug-buttercup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill debug-buttercup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdebug-buttercup\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Ffailure-patterns.md","REFERENCE","参考文档",5647,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdebug-buttercup\u002Freferences\u002Ffailure-patterns.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fdiagnose.sh","SCRIPT","脚本",4217,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fdebug-buttercup\u002Fscripts\u002Fdiagnose.sh",[59,66,73,82,89,96],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]