Essential command-line tools and system utilities.
This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.
Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.
Dumps and analyzes Graal IR compiler graphs showing optimization decisions. Use BGV format with bgv2json/seafoam to inspect escape analysis, boxing removal, inlining decisions, and call node types. Reveals what compiler actually optimized vs intended. Use as last resort after basic profiling when root cause remains unclear.
Systematically trace bugs backward through call stack to find original trigger
Use when animation doesn't work as expected, has bugs, or behaves inconsistently
Sagebaseのロギング規約とベストプラクティス。print文禁止、loggerの使用基準、ログレベルの使い分けをカバー。ログ出力を追加・修正する時、デバッグコードを書く時にアクティベートします。
agent-browser CLI の仕様と使い方に関する知識を提供。ヘッドレスブラウザ自動化、スナップショット、セレクター、セッション管理、ネットワーク制御について回答。Use when user asks about agent-browser, browser automation, snapshots, selectors, sessions, or web scraping. Also use when user says agent-browser について, ブラウザ自動化, スナップショット, セレクター, セッション管理.
Find root cause before attempting fixes through systematic investigation phases. WHEN: MUST use when encountering bugs, test failures, errors, build failures. Invoke with "/systematic-debugging" or "debug systematically". Use ESPECIALLY after multiple failed fixes or under time pressure. WHEN NOT: Issue is already understood with clear root cause, writing new features, simple typos.
Use when fixing a bug or analyzing a stack trace. Enforces systematic debugging methodology to prevent shotgun debugging and verify fixes.
Teaches when type assertions are safe versus dangerous in TypeScript. Use when considering using 'as' keyword, type casting, or when working with external data that might use assertions instead of proper validation.
Use when animation "feels wrong" but you can't pinpoint why—debugging floaty movement, stiff characters, unclear action, or any motion that isn't working and needs systematic troubleshooting.
Debug errors from screenshots with deep analysis to fix the immediate issue and proactively identify related errors. Use this when the user provides an error screenshot, says "debug this", or wants to fix runtime/compile errors.
Analyzes iOS test results from xcodebuild test runs. Use immediately after running xcodebuild test, when tests fail, when the user asks to check test results/failures, or when investigating test issues. Automatically locates the latest .xcresult file and presents detailed failure analysis with file locations.
Agente autónomo especializado en auditoría de código (bugs, seguridad, performance).
Detects Ralph Loop completion beyond <promise> tags. Use when checking if a task is complete, verifying completion status, or detecting graceful exit conditions. Implements 4-signal detection: test loops, done signals, completion indicators, and fix plan verification.
4-phase root cause debugging process. Use when fixing bugs or investigating issues.
Debug failed GPU CLI runs. Analyze error messages, diagnose OOM errors, fix sync issues, troubleshoot connectivity, and resolve common problems. Turn cryptic errors into actionable fixes.
eBPF development in Go using github.com/cilium/ebpf (and bpf2go) for tracing and networking (kprobes/uprobes, tracepoints, XDP, TC). Use when writing/reviewing/debugging Go + eBPF code, setting up CO-RE/BTF toolchains, integrating maps and ringbuf/perf events, or diagnosing verifier/load/attach failures on Linux.
Use for bugs, test failures, or unexpected behavior needing root cause
