1,660 free skills
Debugging skills
Skills for systematic debugging — reproducing bugs, reading stack traces, bisecting regressions, and diagnosing flaky failures.
Sourced from real, public repositories — synced daily, never invented.
1,660 free skills
Skills for systematic debugging — reproducing bugs, reading stack traces, bisecting regressions, and diagnosing flaky failures.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
desktop-mobile-tauri
agents-inc/skills
Tauri 2.x mobile development - iOS via WKWebView, Android via Android WebView, mobile plugins, Swift/Kotlin native code, permissions, debugging
stride-shader-asset-workflow
tebjan/stride-skills
Use when adding, renaming, or debugging Stride SDSL shader files (`*.sdsl`) in a Stride project. Enforces the correct shader registration workflow across `.sdpkg` asset folders, `.csproj` linked shader items, generated shader key files (`*.sdsl.cs`), and forced Stride asset rebuild targets before runtime shader debugging, so agents do not misdiagnose stale asset database/module errors as shader code errors.
ros2-debugging
miuav/vibe-coding-ros2
ROS2 调试技能 - 节点调试、话题分析、bag 回放、rqt 工具使用
deco-site-memory-debugging
decocms/deco-start
Debug memory issues on current blocks sites. Cloudflare Workers (@decocms/tanstack) sites are diagnosed via the tail-worker exceededMemory/exceededCpu capture in ClickHouse plus wrangler tail/dev — there is no live production process to attach to. Node/RSC (@decocms/nextjs) sites use Node's own --inspect CDP flow (process.memoryUsage(), forced GC, heap snapshots).
stack
hjoelh/skills
Analyze the current branch or a GitHub pull request and plan a review-friendly stack of new pull requests, splitting work only when the boundaries materially improve reviewability. Use when a change may benefit from multiple ordered PRs.
regression-tester
terminalskills/skills
>-
flaky-test
gravitational/teleport
Run when the user asks to investigate, troubleshoot, or fix a flaky Go test.
flaky-test-detector
arabelatso/skills-4-se
Identifies non-deterministic or unreliable tests through static code analysis and test result analysis. Use when Claude needs to find flaky tests, analyze test reliability, or investigate intermittent test failures. Supports Python (pytest, unittest) and Java (JUnit, TestNG) test frameworks. Trigger when users mention "flaky tests", "intermittent failures", "non-deterministic tests", "unreliable tests", or ask to "find flaky tests", "analyze test stability", or "why tests fail randomly".
find-resource-leaks
dykyi-roman/awesome-claude-code
Detects resource leaks in PHP code. Finds unclosed file handles, database connections not released, streams not freed, missing finally blocks, temporary files not cleaned.
debugging
1mangesh1/dev-skills-collection
Debugging techniques, tools, and workflows. Use when user asks to "debug this code", "find the bug", "why is this failing", "trace this error", "debug memory leak", "profile this code", "debug network issue", "fix segfault", "debug race condition", "find performance bottleneck", "step through code", "debug async", "debug concurrency", "memory profiling", "CPU profiling", or mentions debugging techniques, error tracing, stack traces, breakpoints, profiling, memory debugging, or troubleshooting code.
source-maps
thedaviddias/front-end-checklist
Use when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
clean-up-comments
thedaviddias/front-end-checklist
Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Validate the final browser-facing markup, not just the source framework abstraction.
debug
angad-kandhari/deliberate
Debugging discipline. Load when the task is fixing a bug, triaging a symptom, or chasing a failing test. Covers reproducing before reasoning, separating symptom from cause, bisecting systematically, not masking what you don't understand, suspecting assumptions, fixing the class not the instance, and leaving a regression test.
network-log-analysis
vahagn-madatyan/netsec-skills-suite
>-
git-bisect
manastalukdar/ai-devstudio
Automated git bisect for bug hunting with test script execution
debug
jjongguet/oh-my-product
Reproduce or inspect a failure, isolate root cause, and validate a fix.
logging
cloudflare/sandbox-sdk
Use when adding logs, debugging, or working with the Logger across the SDK and container runtime. Covers the constructor-injection pattern, child loggers, env-var configuration, and test mocking. (project)
find-traces
axiomhq/cli
Analyze OpenTelemetry distributed traces from Axiom. Use when investigating a trace ID, finding traces by criteria (errors, latency, service), or debugging distributed system issues.
nuxt-test-utils-skilld
nuxt/scripts
ALWAYS use when writing code importing \"@nuxt/test-utils\". Consult for debugging, best practices, or modifying @nuxt/test-utils, nuxt/test-utils, nuxt test-utils, nuxt test utils, test-utils, test utils.
web-game-foundations
openai/plugins
Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy.
build-run-debug
openai/plugins
Build, run, and debug macOS apps with shell-first Xcode and Swift workflows. Use when launching apps or diagnosing build, startup, or runtime failures.
temporal-developer
temporalio/agent-skills
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET and Ruby. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or Temporal Cloud, or working with durable execution concepts like signals, queries, heartbeats, versioning, continue-as-new, child workflows, or saga patterns. Also use when the user mentions "run a Temporal workflow from the CLI", "start a dev server", "run temporal server start-dev", "temporal workflow start", "temporal workflow execute", "temporal workflow signal", "temporal workflow query", "temporal workflow update".
developing-with-docker
spillwavesolutions/developing-with-docker-agentic-skill
Debugging-first guidance for professional Docker development across CLI, Compose, Docker Desktop, and Rancher Desktop. Use when asked to "debug Docker", "troubleshoot containers", "fix Docker networking", "resolve volume permissions", or "Docker Compose issues", and when explaining cross-platform runtime behavior (Linux, macOS, Windows/WSL2) or Docker runtime architecture.
tsconfig
epicenterhq/epicenter
TypeScript config conventions for this monorepo: the two-base layering, the eight leaf tiers, and the never-redeclare list. Use when adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module resolution.
automation
vercel-labs/native
Automation and verification guide for running Native SDK apps. Use when the user asks to test a running app, inspect runtime state, list windows, wait for readiness, drive widgets, take deterministic screenshots, send bridge commands, debug why automation is not connected, create smoke tests, or verify a Native SDK example in a GUI-capable session.
embedded-engineer
furkankuyumcu54/opencode-embedded-engineer
Embedded firmware development and code review for STM32, ARM Cortex-M, and RTOS projects. Use when writing, reviewing, or refactoring C/C++ firmware for microcontrollers — especially STM32 with HAL/LL, DMA, interrupts, FreeRTOS, and peripheral drivers. Also use when debugging hardware-near code, designing driver architectures, or evaluating embedded system tradeoffs.
embedded-debugger
adancurusul/embedded-debugger-mcp
Embedded hardware debugging workflow for probe-rs targets using embedded-debugger-mcp. Use when Codex or Claude Code needs to inspect debug probes, validate embedded debugger setup, start the MCP server, guide a user through ARM Cortex-M/RISC-V flashing/debugging/RTT workflows, or operate without installing an MCP client by using the CLI plus prompts.
redis-cli
sickn33/agentic-awesome-skills
Redis command-line interface (redis-cli) reference and usage guide. Use this skill whenever the user mentions redis-cli, Redis CLI, or any task involving querying, inspecting, debugging, or managing Redis from the command line. Triggers on key/value reads and writes, SCAN or keyspace...
elk-kibana-dashboards
nordz0r/skills
Work with Elasticsearch and Kibana for log analysis, observability triage, and dashboard design. Use when Codex needs to build or troubleshoot Kibana dashboards, Discover searches, Lens or TSVB visualizations, KQL or Lucene filters, Elasticsearch DSL aggregations, index templates, mappings, runtime fields, data views, alerts, or ELK-based investigations.
create-docker-compose-dev
dykyi-roman/awesome-claude-code
Generates Docker Compose development configurations for PHP projects. Creates full development stacks with database, cache, queue, and debugging tools.
analytics
matteocervelli/llms
Run SQL queries against psql, BigQuery, or MySQL from the terminal, including natural-language-to-SQL and schema exploration. Use when analyzing data, inspecting DB state, or debugging tables. Trigger on "query the database", "SQL", "show me data from", "explore table".
cubepi-trace
cubeplexai/cubepi
Use when debugging a cubepi/cubebox agent run — a missing final reply, a tool that misbehaved, a 4xx from the model, wrong token/cache numbers, or "why did the agent do that?". Reads the JSONL traces cubepi writes per run via the `cubepi trace` CLI (ls / view / follow / stats) to inspect the span tree, errors, tool inputs/outputs, and token usage. Triggers on phrases like "查一下这个 run", "trace 一下", "为什么最后一轮没回复", "工具结果不对", "看 trace".
perf-profile
codephobiia/claude-roblox-game-studio
Performance profiling guide — what to measure, how to use MicroProfiler, and common Roblox bottlenecks. Use when debugging performance issues.
threejs-game-director
chrislaupama/threejs-game-skills
Primary entrypoint for complete Three.js browser game creation, premium iteration, and automatic phase orchestration. Use by default for build-a-game, upgrade, polish, premium, AAA, high-fidelity, from-scratch, endless runner, arcade, action, release-ready, or showcase requests. For broad work, first load sibling public skill files for gameplay systems, AAA graphics, UI, debug/profile, and QA/release. For premium games with characters, vehicles, ships, weapons, buildings, signature props, skies, textures, decals, logos, icons, GUI art, audio/SFX/voice needs, or less-basic graphics, load threejs-3d-generator, threejs-image-generator, and/or threejs-audio-generator before deciding generated assets are unnecessary. Keep skill-loading, reference, asset-sourcing, and phase-execution ledgers so users do not choose skills manually.
debugging
hoangnb24/skills
Use when blocked workers, test failures, build errors, runtime crashes, or integration issues need systematic root-cause debugging. Reads history/learnings/critical-patterns.md to avoid re-solving known issues. Writes debug notes that compounding can later capture.
tel-language
bautistapessagno/token-efficient-language
Write, read, and understand TEL (Token Efficient Language) — a compact DSL that represents C programs using minimal tokens for LLM-efficient coding. Use this skill whenever the user asks to write code in TEL, convert C to TEL, convert TEL to C, review TEL code, explain TEL syntax, debug TEL programs, or mentions 'TEL', 'Token Efficient Language', or asks for token-efficient C code. Also trigger when the user wants to write C code but mentions reducing tokens, LLM optimization, or compact syntax. If a .tel file is involved in any way, use this skill.
stack-trace-exposure
thedaviddias/front-end-checklist
Use when reviewing error handling middleware, API route handlers, or server responses for security-sensitive information disclosure.
ai-assist-observability-audit
jparkerweb/ai-assistant-skills
17-dimension observability audit with tier activation, health scoring, and cost analysis. Covers logging, metrics, tracing, alerting, SLOs, profiling, security observability, and developer experience. Use when assessing observability posture, identifying telemetry gaps, or optimizing observability costs.
git-bisect-assistant
arabelatso/skills-4-se
Automatically performs git bisect to identify the first bad commit that introduced a bug or failure. Use when debugging regressions, tracking down when a test started failing, or identifying which commit broke functionality. Handles flaky tests with retry logic and provides comprehensive reports with bisect logs and confidence levels.
Debugging
aia-11-hn-mib/mib-mockinterviewaibot
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.
log-analysis
autohandai/community-skills
Analyze application logs to identify errors, performance issues, and security anomalies. Use when debugging issues, monitoring system health, or investigating incidents. Handles various log formats including Apache, Nginx, application logs, and JSON logs.
stacks
hairyf/blockchain-skills
Stacks blockchain node and mining — RPC API, testnet transactions, PoX mining, event observer, SIPs, property testing, release process, profiling, and service setup.
sentry-fix-issues
getsentry/webvitals.com
Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.
ia-debugging
iliaal/whetstone
>-
fix-flaky-test
microsoft/aspire
Reproduces and fixes flaky or quarantined tests. Tries local reproduction first (fast), then falls back to CI reproduce workflow (reproduce-flaky-tests.yml). Use this when asked to investigate, reproduce, debug, or fix a flaky test, a quarantined test, or an intermittently failing test.
close-flaky-issues
clickhouse/clickhouse
Audit open "flaky test" GitHub issues and close those whose tests are no longer failing on master. Cross-references CI history from play.clickhouse.com with git log to attribute fixes.
gh-fix-ci
openai/plugins
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use `gh` for Actions check and log inspection before implementing any approved fix.
ocaml
bsene/skills
Write, review, debug, and explain OCaml code and dune projects. Use whenever the user mentions OCaml, .ml/.mli files, dune, dune-project, opam, Alcotest, katas or exercises written in OCaml, or asks to convert JS/TS/PHP logic into OCaml. Trigger even if the user just pastes OCaml code with a compiler error and asks "what's wrong here", asks to set up a new dune project, or asks for the OCaml idiom for something they already know how to do in JS/TS. The user is an experienced JS/TS/PHP developer but a genuine OCaml beginner — explanations should assume strong general programming skill and zero OCaml-specific knowledge, never the reverse.
django-debug
ristemingov/django-claude-setup
When the user needs to debug a Django application, diagnose errors, set up logging, or use developer tools. Use when the user says "debug," "error," "500 error," "exception," "traceback," "logging," "Django Debug Toolbar," "shell_plus," "print debugging," "pdb," "breakpoint," "why is this failing," "not working," "unexpected behavior," "ImproperlyConfigured," "DoesNotExist," "IntegrityError," "CSRF," "403," "404," or "500." For performance-specific debugging, see django-performance.
django-expert
felipe3dfx/skills
Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.
django-attack-probe
dolphinllc/claude-security-skills
Authorized self-pentest probe targeting Django and DRF-specific weaknesses. Tests DEBUG-page leak, ALLOWED_HOSTS bypass via Host header, default admin path enumeration, ORM raw() injection, mass-assignment via ModelSerializer, and DRF AllowAny on mutating endpoints. Use when the user asks to "pentest" their own Django app.
rc-kubernetes
rightcodehere/skills
Deploys, manages, and debugs Kubernetes in production — Deployments, Services, Gateway API, service mesh (Istio/Linkerd/Cilium), zero-trust networking (NetworkPolicy), pod security hardening (Pod Security Standards, non-root, read-only filesystem), autoscaling (HPA, PDB), and debugging. Use when users ask to write K8s manifests, deploy to a cluster, debug pods, configure ingress, set up autoscaling, or harden cluster security.
supabase
practicalswan/agent-skills
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
firebase-development
2389-research/firebase-development
This skill should be used when working with Firebase projects, including initializing projects, adding Cloud Functions or Firestore collections, debugging emulator issues, or reviewing Firebase code. Triggers on "firebase", "firestore", "cloud functions", "emulator", "firebase auth", "deploy to firebase", "firestore rules".
firebase-development:debug
2389-research/firebase-development
This skill should be used when troubleshooting Firebase emulator issues, rules violations, function errors, auth problems, or deployment failures. Triggers on "error", "not working", "debug", "troubleshoot", "failing", "broken", "permission denied", "emulator issue".
reproduction-trace-instrumenter
arabelatso/skills-4-se
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.
dbt-troubleshoot
altimateai/altimate-code
Debug dbt errors — compilation failures, runtime database errors, test failures, wrong data, and performance issues. Use when something is broken, producing wrong results, or failing to build. Powered by altimate-dbt.
scrape
zytedata/claude-skills
End-to-end web scraping workflow — from URL to working spider with web-poet page objects. Use this for full-site or multiple-page crawls that create a new scraping workflow. Do not use for fixing, debugging, or modifying an existing spider.
api-design-review
noorkhalel/saas-ai-skills
Review or design an API contract: REST, GraphQL, gRPC, events, webhooks, streaming, or OpenAPI/AsyncAPI. Use when the primary deliverable is an interface contract, compatibility assessment, or API-specific security/resilience guidance. Do not use for whole-system architecture planning, generic code review, database modeling, or implementation debugging.
ctf-reverse
isloverhatwhite/ctf-skills
Provides reverse engineering techniques for CTF challenges. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.