Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and…
A structured method for finding the underlying cause of a problem by asking “why?” repeatedly. It is intended for bugs, production incidents, performance problems, and recurring failures.
Debug fleet TUI performance issues — UI loop stalls, frozen sidebar, sluggish attach, or background CPU spikes. Reads perfwatch stall dumps and the debug.log heartbeat to identify what blocked the Bubble Tea Update() loop or stole cycles from the PTY. Trigger on: "TUI is stuck/frozen/laggy", "UI hangs", "everything…
Diagnose slow, expensive, or regressed Apache Spark and PySpark applications by comparing runtime evidence against a healthy run. Use for long stages, stragglers, skew, shuffle, spill, garbage collection, poor parallelism, small files, slow scans, scheduler delay, executor imbalance, and unexplained compute-cost…
Iterative multi-round codebase audit with diminishing-returns detection. Run 5-20+ rounds, each focusing on one specific area. Built from 19 rounds of dogfooding pi-crew on itself.
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida modules (50+), idautils iterators, and common…
Inspect and explain bmad-loop run artifacts under .bmad-loop/runs/. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Reconstruct terminal-redraw captures before interpreting…
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Inspect this machine's live resource usage via the Agentinel CLI — find runaway / zombie / leaking AI-agent processes (Claude Code, Codex, Gemini, OpenCode, MCP & dev servers, Ollama…), duplicate sessions, heavy memory users, and reclaimable disk caches. Use when the user asks what's eating RAM/CPU/disk, whether they…
Triage a TT-Studio bug-report ZIP / log bundle (named tt-studio-logs-ttbr- or referenced as ttbr-) to root-cause why a model deploy, board allocation, or Voice Agent pipeline failed. Use when the user shares a path to a TT-Studio log bundle, mentions a bug report ID like ttbr- , or attaches a screenshot of the…
Triage, diagnose, and fix failing Prefect 3 pipelines in this repo. Surveys recent failed flow runs and deployment arming state, groups failures by root cause, classifies each against a failure taxonomy, and drives fixes through branch → PR → label → dev run → merge. Use when asked to check on broken pipelines, find…
Use this skill when the user wants to add DevInspector (dev-inspector-mcp) to their project, integrate MCP for their editor, set up ACP agents, click-to-source in browser, or debug "inspector not showing" / "MCP not connecting" issues. Triggers on phrases like "add dev inspector", "click to component", "setup…
Use when building, changing, or deploying an instancez backend - editing instancez.yaml (tables, RLS, auth, storage, rpc, functions), running the inz CLI, or debugging why a query is denied. instancez is a single-binary Supabase-compatible backend defined by one YAML file.
Resolve which dependency versions are actually installed, from composer show and composer.lock, when diagnosing version-specific behavior such as a method, argument or class that does not exist in the release that is really running. For the PHP runtime itself (version, OS, loaded extensions) use the…
Local-first code graph builder with 5-signal hybrid search. Use when analyzing codebases, searching for code architecture, exploring dependencies, or building code graphs from source code and documents.
Deobfuscate .NET binaries loaded in dnSpy via MCP tools. Use this skill whenever the user wants to decrypt strings, rename obfuscated symbols, simplify control flow, detect proxy calls, remove anti-tamper protections, or make obfuscated .NET code readable. Also trigger when the user mentions deobfuscation, string…
Debug and trace C/C++/Rust programs with the GNU Debugger (GDB) without blocking the agent. Use when you need to set tracepoints, inspect variables, or monitor a running process while staying responsive to the user.
Audit AHK v2 code for silent failures and inadequate error handling. Hunts for empty catch blocks, swallowed errors, broad bare-catches that hide unrelated failures, and fallbacks that mask problems from the user. TRIGGER when: user says "audit errors", "check error handling", "find silent failures", "review error…
Proactive bug-hunting methodology — autonomous codebase reconnaissance to find latent bugs, hidden failure modes, and ticking time bombs BEFORE they detonate in production. Use this skill whenever the user asks to "find bugs", "hunt for issues", "audit this codebase", "what could go wrong", "find what's broken"…
Debug and extend Open Edit agent tools (sandbox, skills, style memory, TOOLTABLE). Use when working on openedit/agent/, runscript/sandbox, style profiles, searchassets, or the 26 tool callables.
Design, review, and debug visual rendering tests: reftests (independent oracle), golden/snapshot regression tests, probe tests (pixel assertions without vision), SVG reftest suites, and Figma refig suites. Use when adding pixel diffs, choosing an oracle strategy, or comparing renderer output against a ground truth.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: