Debugger
Skill VerificadoSystematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, troubleshooting bugs, investigating crashes, analyzing stack traces, fixing broken code, or when user mentions debugging, error, bug, crash, or "not working".
This skill provides a detailed, step-by-step guide for identifying and resolving software issues. It outlines a structured debugging process, common bug patterns, and strategies like binary search and rubber duck debugging, culminating in a standardized output format for analysis and fixes.
Instalación
npx skills add shubhamsaboo/awesome-llm-appsEjecuta el CLI de skills de Vercel (skills.sh) mediante npx — requiere Node.js en local y al menos un agente compatible con skills instalado (Claude Code, Cursor, Codex, …). Asume que el repositorio sigue el formato de agentskills.io.
Extensiones similares
Docker Debugger
95Debug Docker containers, fix Dockerfile issues, optimize images, and troubleshoot docker-compose. Use when having Docker problems, container issues, or optimizing Docker builds.
OpenClaw Config
98Manage OpenClaw bot configuration - channels, agents, security, and autopilot settings
react-devtools-inline
97Embed react-devtools within a website
React DevTools Core
95Use react-devtools outside of the browser
React DevTools
95Use react-devtools outside of the browser
Bright Data — Browser Session Debugger
95Debug Bright Data Scraping Browser sessions using the Browser Sessions API. Use this skill when the user encounters a Bright Data browser session error, puppeteer stack trace, failed scraper run, or asks about session bandwidth, duration, captchas, or connection issues. Also use when a Bright Data scraper produces unexpected results such as empty data, 0 items found, missing products, or fewer results than expected — session data can reveal whether the issue is network/proxy-side (blocks, captchas, redirects, timeouts) or client-side (selectors, extraction logic). Triggers on phrases like 'why did my session fail', 'debug my bright data session', 'check my scraping browser sessions', 'how much bandwidth did my scraper use', 'got 0 results', 'found 0', 'scraper returned empty', 'scraper not working', 'script didn't work', or when a Bright Data error code or brd.superproxy.io stack trace appears in the conversation. Requires BRIGHTDATA_API_KEY environment variable.