Discover debugging
Automatically discover debugging and profiling skills when working with GDB, LLDB, breakpoints, profiling, stack traces, memory leaks, core dumps, or performance profiling. Activates for debugging development tasks.From its SKILL.md
npx -y skills add kenantang/codex-and-claude-skills --skill discover-debuggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 399 tokens by cl100k_base, as published. Nobody here has run it
Debugging Skills Discovery
Provides automatic access to comprehensive debugging skills.
When This Skill Activates
This skill auto-activates when you're working with:
- debugging
- GDB
- LLDB
- profiling
- memory leaks
- performance analysis
- troubleshooting
- diagnostics
- monitoring
- logging
- tracing
- metrics
- distributed tracing
- alerts
- dashboards
- observability
Available Skills
Quick Reference
The Debugging category contains 22 skills across 2 subcategories:
Debugging (14 skills):
- browser-devtools
- concurrency-debugging
- container-debugging
- core-dump-analysis
- crash-debugging
- distributed-systems-debugging
- gdb-fundamentals
- lldb-macos-debugging
- memory-leak-debugging
- network-debugging
- performance-profiling
- production-debugging
- python-debugging
- remote-debugging
Observability (8 skills): See ../observability/INDEX.md
Load Full Category Details
Read ../debugging/INDEX.md Read ../observability/INDEX.md
Progressive Loading
This gateway skill enables progressive loading:
- Level 1: Gateway loads automatically (you're here now)
- Level 2: Load category INDEX.md for full overview
- Level 3: Load specific skills as needed
Usage Instructions
- Auto-activation: This skill loads automatically when Claude Code detects debugging work
- Browse skills: Run
Read ../debugging/INDEX.mdfor full category overview - Load specific skills: Use bash commands above to load individual skills
Next Steps: Run Read ../debugging/INDEX.md to see full category details.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 399 tokens
Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06
- Find root cause before attempting any fixin 134 of 1020, across 118 files
- Create a failing test case before implementing a fixin 109 of 1020, across 95 files
- Read error messages and stack traces completelyin 102 of 1020, across 88 files
- Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
- Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
- Trace data flow backward to find the sourcein 84 of 1020, across 70 files
- Form a single hypothesis before testingin 78 of 1020, across 64 files
- Implement only one fix at a timein 76 of 1020, across 63 files
- Question the architecture if three fixes failin 73 of 1020, across 59 files
- Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
- Compare broken code against working examplesin 68 of 1020, across 57 files
- Write a regression test before applying the fixin 62 of 1020, across 55 files
Said here and by no other author read
- Read the debugging index file
- Read the observability index file
- Load specific skills as needed
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.