2.7K skills · sorted by relevance
[omh] Native program crashes or corrupts memory: prepare hypothesis-driven debugging of native binaries and instruct the executor to drive a DAP debugger instead of printf. Use when the user says: native-debugging, native debugging, native binary, segfault, segmentation fault, core dump, stack corruption, memory corruption.
The English summary is being prepared. Showing the original description.
Collect Anima SDK debug evidence for support tickets and troubleshooting. Use when filing Anima support requests, debugging code generation issues, or collecting diagnostic data for the Anima team. Trigger with: "anima debug bundle", "anima support ticket", "anima diagnostics".
The English summary is being prepared. Showing the original description.
You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "dev-debug", "テストが失敗する", "ビルドエラーを直して", "デバッグ", "debug failing tests", "fix build error", "エラーを修正", "コンパイルエラー", "環境の問題を解決". テスト失敗、ビルドエラー、環境問題など様々なエラーパターンをカテゴリ別に診断し、最小コンテキストで修正する。
The English summary is being prepared. Showing the original description.
Generates a developer debug menu with feature flag toggles, environment switching, network log viewer, cache clearing, crash trigger, and diagnostic info export. Only included in DEBUG builds. Use when user wants a debug panel, dev tools menu, or shake-to-debug functionality.
The English summary is being prepared. Showing the original description.
Use when inspecting .debug_info or .debug_line sections with dwarfdump or readelf, working with split-DWARF .dwo files, setting up debuginfod, or checking how LTO and stripping affect debug info.
The English summary is being prepared. Showing the original description.
昇腾AscendC算子调试工具（msDebug）技能，含两大流程：①上板调试——算子加 -g -O0 编译后由 msdebug 拉起，支持断点、单步、变量/内存打印、核切换、寄存器读取；②coredump解析——用户指定 core 文件路径后，msdebug 加载解析挂掉代码行/异常调用栈/现场变量。触发关键词：msdebug、算子调试、上板调试、断点、单步调试、打印变量、读内存、核切换、寄存器、coredump、core文件、调用栈、崩溃解析
The English summary is being prepared. Showing the original description.
Uses x64dbg to dynamically debug Windows malware: setting strategic breakpoints on APIs, stepping through unpacking and decryption, dumping memory at the right moment, and manipulating execution to reach hidden code. Activates for requests to debug malware with x64dbg, set API breakpoints, or step through unpacking in a debugger.
The English summary is being prepared. Showing the original description.
システムログを分析してエラーの根本原因を特定し、段階的に深堀りしていくデバッグ専門家スキル。 アプリケーションログ、システムログ、クラウドサービスログなど様々な形式に対応。 5 Whys、タイムライン分析、Fishbone分析などのRCA（根本原因分析）手法を用いて 問題の本質を突き止め、再発防止策まで提案する。 Use when analyzing system logs to find error root causes, debugging application issues, or performing technical post-mortem analysis with log data. For organizational incident management processes (post-incident review, corrective action plans, incident reports without log data), use incident-rca-specialist instead. Triggers: "analyze this log", "find the root cause", "debug this error", "why is this failing", "log analysis", "what caused this crash", "troubleshoot this issue"
The English summary is being prepared. Showing the original description.
Agent fallback for CBaseEntity_DrawDebugTextOverlays (auto-generated, category: vfunc). Locate CBaseEntity::DrawDebugTextOverlays in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CBaseEntity_DrawDebugTextOverlays, CBaseEntity::DrawDebugTextOverlays
The English summary is being prepared. Showing the original description.
Debug Python: pdb REPL + debugpy remote (DAP).
The English summary is being prepared. Showing the original description.
Guides debugging through reproduction, comparison with working examples, hypothesis testing, and a focused fix. It starts with a repeatable check for the exact symptom and uses regression tests to verify the result.
Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.
Inspect production HTML for development comments, debug code, console logs, and temporary markup. Remove unnecessary remnants, check comments for sensitive information, and preserve comments needed for accessibility or legal purposes.
Investigate complex bugs by assigning competing explanations to parallel agents. Compare code evidence, contradictory findings, and confidence levels to identify likely root causes, then check that a fix resolves the original failure and related edge cases.
Investigate CUDA crashes in SGLang using logs and inputs saved before execution. Inspect tensor shapes, data types, and numerical anomalies, with guidance for separate process logs and additional CUDA debugging tools.
Connect to an existing Chrome browser or launch one with an explicit debugging port for sharing across agents and tools. It also covers scanning local CDP ports, the connection endpoints used to control a browser.
Adapt an AI agent’s approach to brainstorming, implementation, debugging, review, teaching, or release preparation. Defines how each mode should ask questions, prioritize work, and present results, with automatic mode selection and explicit switching examples.
Plan, set up, audit, and debug analytics tracking with GA4 and Google Tag Manager. Define events and their parameters, configure conversion tracking, and investigate missing or duplicate data using structured checks and prioritized fixes.
Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying optimization patterns (→ See `samber/cc-skills-golang@golang-performance` skill), or designing new code (→ See `samber/cc-skills-golang@golang-safety` skill for defensive coding, `samber/cc-skills-golang@golang-concurrency` skill for concurrency design).
The English summary is being prepared. Showing the original description.
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the demonstrated root cause. Use when the user says: app-debugging, app debugging, application debugging, root cause, root-cause, find the root cause, root cause analysis, flaky test.
The English summary is being prepared. Showing the original description.
Collect Apollo.io debug evidence for support. Use when preparing support tickets, documenting issues, or gathering diagnostic information for Apollo problems. Trigger with phrases like "apollo debug", "apollo support bundle", "collect apollo diagnostics", "apollo troubleshooting info".
The English summary is being prepared. Showing the original description.
Collect Anthropic Claude API debug evidence for support and troubleshooting. Use when encountering persistent API issues, preparing support tickets, or collecting diagnostic information including request IDs and rate limit headers. Trigger with phrases like "anthropic debug", "claude debug bundle", "collect anthropic logs", "anthropic diagnostic", "claude support ticket".
The English summary is being prepared. Showing the original description.