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.
Systematic root-cause debugging methodology. An agent skill from poteto/noodle.
Install Debugging
$ npx skills add poteto/noodle --skill debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install poteto/noodle debugging --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/poteto/noodle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debugging .claude/skills/debugging && 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 "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .claude/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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/poteto/noodle/tree/main/.agents/skills/debuggingType 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 poteto/noodle --skill debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install poteto/noodle debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debugging .agents/skills/debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .agents/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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 poteto/noodle --skill debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install poteto/noodle debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debugging .cursor/skills/debugging && 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 "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .cursor/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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/poteto/noodle.git --path .agents/skills/debugging--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 poteto/noodle --skill debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install poteto/noodle debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debugging .gemini/skills/debugging && 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 "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .gemini/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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 poteto/noodle debuggingInstalls 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 poteto/noodle --skill debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debugging .github/skills/debugging && 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 "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .github/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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 poteto/noodle --skill debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install poteto/noodle debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/poteto/noodle.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debugging .opencode/skills/debugging && 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 "debugging" agent skill from https://github.com/poteto/noodle/tree/main/.agents/skills/debugging into .opencode/skills/debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging", 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
debugging- GitHub stars
- 437
- Token cost
- ~980 tokens
- SKILL.md length
- 484 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- MIT
At a glance
Systematic root-cause debugging methodology. An agent skill from poteto/noodle.
- Works in 7 steps: Reproduce. Get the exact error. Run the… → Read the error. The error message, stack… → Suspect state before code. Before… → …
- Any technical problem — errors
- SKILL.md covers Process, Noodle-Specific Diagnostics, When Stuck and Anti-Patterns, plus 1 more section
- Calls git
What it does
Debugging is an agent skill from poteto/noodle. Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
Its SKILL.md is about 980 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 Debugging and Root cause analysis. The repository describes itself as: Orchestrate agents using skills. The licence is MIT.
When your agent uses it
- Any technical problem — errors
- Unexpected behavior
Example prompts
- “fix this”
- “s wrong”
- “investigate”
- “/debugging”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Reproduce. Get the exact error. Run the failing command, read the full output. If you can't reproduce, you can't verify your fix.
- Read the error. The error message, stack trace, and line numbers are data. Read all of it before forming hypotheses. Most bugs tell you…
- Suspect state before code. Before debugging code, check persistent state — especially on restart bugs or environment drift. See…
- Isolate. Narrow the scope. Which file? Which function? Which line? Use binary search: comment out half, see if it still fails, repeat.
- Find root cause. The first "fix" that comes to mind is usually a symptom fix. Ask "why?" until you hit the actual cause
- Fix and verify. Fix the root cause, not the symptom. Then verify: run the test, run the build, exercise the feature path. "It compiles" is…
- Check for the pattern. If the bug existed in one place, grep for the same pattern elsewhere. Fix all instances, or make it structurally…
What it can do on your machine
Read from SKILL.md and the folder at commit 82d2921. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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
Debugging loads about 980 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 484 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 passed
The automated check found no risky patterns in SKILL.md.
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 poteto/noodle at commit 82d2921, republished under its MIT licence (© poteto). 484 words, ~980 tokens.
Download SKILL.mdSave it as
.claude/skills/debugging/SKILL.md (or your agent's skills folder).- name
- debugging
- description
- Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
Debugging
Read [[principles/fix-root-causes]] before starting. Every debugging session follows that principle: trace to root cause, never paper over symptoms.
Process
Reproduce. Get the exact error. Run the failing command, read the full output. If you can't reproduce, you can't verify your fix.
Read the error. The error message, stack trace, and line numbers are data. Read all of it before forming hypotheses. Most bugs tell you exactly where they are.
Suspect state before code. Before debugging code, check persistent state — especially on restart bugs or environment drift. See [[principles/fix-root-causes]].
- Noodle state:
.noodle/orders.json(stale items?),.noodle/sessions/(orphaned?),.noodle.toml(valid?) - Environment: tmux sessions (
tmux ls), lock files, cached artifacts - Config:
.noodle.tomlvalidation (noodle startreports diagnostics), skill frontmatter parse errors - Persistent files: brain/ notes, plan files, todos — check for corruption or stale references
- Noodle state:
Isolate. Narrow the scope. Which file? Which function? Which line? Use binary search: comment out half, see if it still fails, repeat.
Find root cause. The first "fix" that comes to mind is usually a symptom fix. Ask "why?" until you hit the actual cause:
- Test fails → mock is wrong → interface changed → type doesn't match runtime shape → fix the type
- Build fails → import error → circular dependency → restructure the modules
- Runtime crash → undefined value → missing null check → data source returns null on empty → handle empty case at the source
Fix and verify. Fix the root cause, not the symptom. Then verify: run the test, run the build, exercise the feature path. "It compiles" is not verification.
Check for the pattern. If the bug existed in one place, grep for the same pattern elsewhere. Fix all instances, or make it structurally impossible.
Show full SKILL.md (206 more words)Show less
Noodle-Specific Diagnostics
When debugging Noodle infrastructure failures:
| Symptom | Check first |
|---|---|
| Cook won't start | tmux ls, .noodle/orders.json validity, skill resolver paths |
| Orders stuck | .noodle/orders.json for stale items, .noodle.toml adapter config |
| Missing skill | .noodle.toml [skills] paths, .agents/skills/<name>/SKILL.md exists |
| Stale mise | .noodle/mise.json generated_at timestamp, backlog sync script |
| Session orphaned | .noodle/sessions/<id>/meta.json status, tmux ls for zombie sessions |
When Stuck
- Instrument, don't guess. Add logging at key points to see actual values. Read actual state ([[principles/prove-it-works]]).
- Diff what changed.
git diff,git log,git bisect. Most bugs are recent. - Simplify. Strip the failing case to minimum reproduction. Remove everything unrelated.
- Change one thing at a time. Multiple changes at once make it impossible to know what fixed (or broke) it.
- Check assumptions. The bug is often in the part you're sure is correct. Verify everything.
Anti-Patterns
- Bypass flags (
--no-verify,--force,SKIP_CHECK=true) silence symptoms without fixing causes. - Retry loops hide intermittent bugs behind probability.
- Shotgun debugging — changing three things to "see if it helps" — obscures causality.
- Adding guards (
if (x !== undefined)) without asking why x is undefined.
After Fixing
If this bug could recur or affected your understanding, capture the lesson. Write a brain note, update a skill, or add a todo. The system should get smarter from every bug. See [[principles/encode-lessons-in-structure]].
© poteto, 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 .agents/skills/debugging of poteto/noodle.
Open the folder on GitHubat commit 82d2921
Compare with similar skills
Debugging 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 |
|---|---|---|---|---|---|---|
| Debugging this skillpoteto/noodle | 437 | — | ~980 | Automated safety check: Pass | 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 poteto/noodle
All 26 skills in this repoMeditate
poteto/noodle
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities.
Ruminate
poteto/noodle
Mine past Claude Code and Codex conversations for uncaptured patterns, corrections, and knowledge.
Ast Grep
poteto/noodle
Structural code search via ast-grep — use when code shape and element relationships matter, not just text.
Execute
poteto/noodle
Implementation methodology for executing tasks. An agent skill from poteto/noodle.
Noodle
poteto/noodle
Operate the Noodle CLI — explain commands, find flags, create/edit .noodle.toml config.
Plan
poteto/noodle
Systematic planning for medium-to-large tasks. An agent skill from poteto/noodle.
Related
Categories
Questions about Debugging
What does Debugging do?
Systematic root-cause debugging methodology. An agent skill from poteto/noodle. Debugging is an agent skill from poteto/noodle. Systematic root-cause debugging methodology.
When should I use Debugging?
Debugging fits situations like: any technical problem — errors; unexpected behavior.
How do I install Debugging in Claude Code?
Run `npx skills add poteto/noodle --skill debugging -a claude-code`. Or copy the skill folder (.agents/skills/debugging in poteto/noodle) into .claude/skills/debugging in your project. Claude Code loads it when a task matches its description.
How do I install Debugging in Codex?
Run `npx skills add poteto/noodle --skill debugging -a codex`. Or copy the skill folder (.agents/skills/debugging in poteto/noodle) into .agents/skills/debugging in your project. Codex loads it when a task matches its description.
Can I use Debugging 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 poteto/noodle --skill debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging, .gemini/skills/debugging, .github/skills/debugging and .opencode/skills/debugging in your project.
What does Debugging need to run?
Going by SKILL.md and its folder, Debugging needs the command-line tools its instructions call (git).
Does Debugging 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 Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging use?
Debugging 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 Debugging use?
About 980 tokens (SKILL.md is roughly 3.9k 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 Debugging?
Skills that share tags, products or a category with Debugging: 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 Debugging?
poteto (a GitHub user) maintains it in poteto/noodle, which has 437 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on March 19, 2026.
Source: poteto/noodle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.