Loading...
Loading...
Found 1,691 Skills
Observe Before Editing
Identifies bugs, analyzes errors, performs root cause analysis, and proposes fixes
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case. Use when you have unoptimized-query-oracle*.log files from a failed roachtest and need to find the minimal SQL to reproduce the bug.
Create or update AgentDeploy SharedInfra and Service YAML files, validate them, deploy apps with the agentdeploy CLI and Platform API, poll status and explain output, and debug structured deployment failures. Use when a user wants to deploy, redeploy, or troubleshoot an app on an AgentDeploy installation.
Debugs errors and traces failures in AI agents and their tools. Use this skill when the user says: "the agent is failing", "tool call not working", "error in the pipeline", "debug this", "why is the agent doing X instead of Y", "trace the execution", "agent is stuck", "infinite loop", "model response won't parse", "context overflow". Identifies context errors, infinite loops, malformed tool calls, response parsing issues and subagent conflicts.
OpenOCD 下载与调试工具，用于探针探测、固件烧录、Flash 擦除、GDB Server 启动、目标复位控制、 Telnet 在线调试（halt/resume/step/寄存器/内存/断点）、GDB 源码级调试，以及 Semihosting/ITM 输出捕获和底层查询。 当用户提到 OpenOCD、ST-Link、CMSIS-DAP、DAPLink、FTDI、烧录固件、擦除 Flash、GDB Server、 reset、interface/target/board 配置、openocd.cfg、在线调试、单步、断点、寄存器查看、 内存读写、semihosting 时自动触发，也兼容 /openocd 显式调用。 即使用户只是说"烧录一下"、"启动 GDB Server"、"擦除芯片"、"看看寄存器"、"单步调试" 或"抓一下 semihosting"，只要上下文涉及 OpenOCD 支持的开源调试器就应触发此 skill。
MCP server for JavaScript reverse engineering in real browser environments with hooks, breakpoints, network tracing, deobfuscation, and environment reconstruction.
Convert single-node scripts to multi-node Slurm sbatch jobs and debug common multi-node failures. Covers srun-native vs uv run torch.distributed approaches, container setup, NCCL timeouts, OOM sizing for MoE models, and interactive allocation.
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
Code-verification session with the rubber duck — user explains code just written, finds edge cases, fixes planted bugs. Use after implementing a feature, or when they say "duck verify", "재확인해줘". Not for plan review (/duck-plan) or PR review (/duck-review).
Use this skill when the user needs to build Move code, or when when the user asks about sui move build.
Use when ANY Metal porting issue occurs - black screen, rendering artifacts, shader errors, wrong colors, performance regressions, GPU crashes