OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Diagnose failures by root cause, not symptom. An agent skill from TheDecipherist/claude-code-mastery-project-starter-kit.
Install Debugger
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debugger --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/debugger .claude/skills/debugger && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .claude/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debuggerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debugger --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/debugger .agents/skills/debugger && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .agents/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debugger --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/debugger .cursor/skills/debugger && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .cursor/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git --path .claude/skills/debugger--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debugger --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/debugger .gemini/skills/debugger && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .gemini/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debuggerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/debugger .github/skills/debugger && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .github/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheDecipherist/claude-code-mastery-project-starter-kit debugger --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/debugger .opencode/skills/debugger && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugger" agent skill from https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit/tree/main/.claude/skills/debugger into .opencode/skills/debugger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugger", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugger- GitHub stars
- 338
- Token cost
- ~669 tokens
- SKILL.md length
- 345 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose failures by root cause, not symptom. An agent skill from TheDecipherist/claude-code-mastery-project-starter-kit.
- Works in 6 steps: Reproduce before anything else. Build… → State observed vs expected, precisely.… → Rank two or three hypotheses. Order by… → …
- Intermittent bugs
- SKILL.md covers Method, Production incidents and Non-negotiable
- Calls git
What it does
Debugger is an agent skill from TheDecipherist/claude-code-mastery-project-starter-kit. Diagnose failures by root cause, not symptom. Use for crashes, stack traces, intermittent bugs, memory growth, race conditions, and "works locally, fails in prod" cases where you need a reproducible cause before a fix. Runs isolated and read-only, reports the root cause and fix.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis, Debugging and Async programming. The repository describes itself as: The definitive starting point for Claude Code projects. Based on Claude Code Mastery Guides V1-V5. The licence is MIT.
When your agent uses it
- Intermittent bugs
- Race conditions
- Fails in prod cases where you need a reproducible cause before a fix
Example prompts
- “works locally, fails in prod”
- “/debugger”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Bash
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Reproduce before anything else. Build the smallest script or test that triggers the failure every time. If you cannot reproduce it, stop…
- State observed vs expected, precisely. "Under condition X, the system does Y; it should do Z." If you can't fill that in, you don't…
- Rank two or three hypotheses. Order by likelihood, weighted toward whatever changed most recently. Name each one.
- Falsify the top hypothesis with the cheapest possible probe. One log line, one targeted grep, one assertion. Try to prove yourself wrong…
- Fix, and add the regression test in the same change. The test must fail on the old code and pass on the new. Fix without test is not done.
- Record the root cause and one prevention step. What it was, what the falsifying probe showed, and the one change that stops the whole…
What it can do on your machine
Read from SKILL.md and the folder at commit 61fbb99. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugger loads about 669 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 345 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TheDecipherist/claude-code-mastery-project-starter-kit at commit 61fbb99, republished under its MIT licence (© TheDecipherist). 345 words, ~669 tokens.
Download SKILL.mdSave it as
.claude/skills/debugger/SKILL.md (or your agent's skills folder).- name
- debugger
- description
- Diagnose failures by root cause, not symptom. Use for crashes, stack traces, intermittent bugs, memory growth, race conditions, and "works locally, fails in prod" cases where you need a reproducible cause before a fix. Runs isolated and read-only, reports the root cause and fix.
- allowed-tools
- Read, Grep, Bash
- when_to_use
- - User reports a crash, exception, stack trace, or failing behavior and wants the cause - A bug is intermittent, environment-specific, or not reproducing…
- context
- fork
Debugger
You find root causes. You do not patch symptoms, and you do not guess.
Method
Work these in order. Do not skip ahead.
- Reproduce before anything else. Build the smallest script or test that triggers the failure every time. If you cannot reproduce it, stop. The bug is now "why can't I reproduce this," and you investigate that gap instead of writing a fix blind.
- State observed vs expected, precisely. "Under condition X, the system does Y; it should do Z." If you can't fill that in, you don't understand the bug yet.
- Rank two or three hypotheses. Order by likelihood, weighted toward whatever changed most recently. Name each one.
- Falsify the top hypothesis with the cheapest possible probe. One log line, one targeted grep, one assertion. Try to prove yourself wrong before writing any fix. A hypothesis you only confirmed is one you didn't test.
- Fix, and add the regression test in the same change. The test must fail on the old code and pass on the new. Fix without test is not done.
- Record the root cause and one prevention step. What it was, what the falsifying probe showed, and the one change that stops the whole class from recurring.
Production incidents
For anything live, do these three before opening a source file. Most incidents resolve here.
- Change correlation first. What deployed, what flag flipped, what config changed, what traffic shifted in the 30 minutes before the first error.
git log --since, deploy history, flag state. A correlated change usually is the answer. - Trace to the first failing span. Start from the earliest operation that errored or blew its latency budget, not the symptom the user reported. The symptom is downstream.
- Logs, tightly windowed. ±2 minutes around that first error, filtered to the failing service and correlation ID.
grep,jq,awk.
Non-negotiable
- Never ship a fix for a bug you could not reproduce.
- The fix and its regression test land together or not at all.
- Every fix ends with one named prevention measure.
© TheDecipherist, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/debugger of TheDecipherist/claude-code-mastery-project-starter-kit.
Open the folder on GitHubat commit 61fbb99
Compare with similar skills
Debugger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugger this skillTheDecipherist/claude-code-mastery-project-starter-kit | 338 | — | ~669 | Automated safety check: Notes | MIT | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT | |
| Systematic DebuggingChrisWiles/claude-code-showcase | 6.1k | 3 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Systematic Debugging
ChrisWiles/claude-code-showcase
Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.
Debugging and Error Recovery
addyosmani/agent-skills
Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.
More from TheDecipherist/claude-code-mastery-project-starter-kit
All 24 skills in this repoCreate Service
TheDecipherist/claude-code-mastery-project-starter-kit
Scaffold a new microservice that follows the project's server/handlers/adapters architecture.
CSS Structure
TheDecipherist/claude-code-mastery-project-starter-kit
Where CSS should live. An agent skill from TheDecipherist/claude-code-mastery-project-starter-kit.
Docker
TheDecipherist/claude-code-mastery-project-starter-kit
Production Docker best practices for writing Dockerfiles, Compose files, and Swarm stacks.
Docker Swarm
TheDecipherist/claude-code-mastery-project-starter-kit
Production Docker Swarm deployment rules: what changes when a compose file goes from a single node to a multi-node Swarm.
Mongodb Backups
TheDecipherist/claude-code-mastery-project-starter-kit
Production MongoDB backup and restore practices that the documentation gets wrong.
Mongodb Replica Sets
TheDecipherist/claude-code-mastery-project-starter-kit
Production MongoDB replica-set operation: topology, durability, host tuning, and the container-specific gotchas Claude gets wrong.
Related
Categories
Questions about Debugger
What does Debugger do?
Diagnose failures by root cause, not symptom. An agent skill from TheDecipherist/claude-code-mastery-project-starter-kit. Debugger is an agent skill from TheDecipherist/claude-code-mastery-project-starter-kit. Diagnose failures by root cause, not symptom.
When should I use Debugger?
Debugger fits situations like: intermittent bugs; race conditions; fails in prod cases where you need a reproducible cause before a fix.
How do I install Debugger in Claude Code?
Run `npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a claude-code`. Or copy the skill folder (.claude/skills/debugger in TheDecipherist/claude-code-mastery-project-starter-kit) into .claude/skills/debugger in your project. Claude Code loads it when a task matches its description.
How do I install Debugger in Codex?
Run `npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a codex`. Or copy the skill folder (.claude/skills/debugger in TheDecipherist/claude-code-mastery-project-starter-kit) into .agents/skills/debugger in your project. Codex loads it when a task matches its description.
Can I use Debugger in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheDecipherist/claude-code-mastery-project-starter-kit --skill debugger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugger, .gemini/skills/debugger, .github/skills/debugger and .opencode/skills/debugger in your project.
What does Debugger need to run?
Going by SKILL.md and its folder, Debugger needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Grep, Bash.
Does Debugger access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Debugger safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Debugger use?
Debugger is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debugger use?
About 669 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugger?
Skills that share tags, products or a category with Debugger: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugger?
TheDecipherist (a GitHub user) maintains it in TheDecipherist/claude-code-mastery-project-starter-kit, which has 338 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on June 29, 2026.
Source: TheDecipherist/claude-code-mastery-project-starter-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.