debugger
Rank root-cause hypotheses and propose the smallest safe fix.
Install / Use
npx skills add antonbabenko/deliberation --skill debuggerInstalls into whichever agent you are using.
Gemini Rules
Gemini CLI config
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of debugger
debugger scores 58/100 on our quality scale, 4147th of 4,606 Development & Engineering skills we index.
Its Gemini Rules is 2.2 KB long, split into 7 sections and no code examples: moderately detailed.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- The repository was last updated 11 days ago, so debugger is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
debugger compared with similar skills
All 4 of these similar skills score higher than debugger; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| debugger (this skill)by antonbabenko | 58 | 0 | 11d ago | Gemini Rules |
| taste-skillby Leonxlnx | 100 | 102.7k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 66.0k | 5d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 45.2k | 6d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 34d ago | SKILL.md |
Frequently asked questions
- How do I install debugger?
- Run
npx skills add antonbabenko/deliberation. The install tabs above show the steps for each supported agent. - Which AI agents does debugger work with?
- It is written for Gemini CLI, as a Gemini Rules file. Other agents that read the same format can often use it too.
- Is debugger safe to use?
- It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is debugger still maintained?
- The repository was last updated 11 days ago, so debugger is actively maintained.
Skill content
View source on GitHubname: "debugger" description: "Rank root-cause hypotheses and propose the smallest safe fix."
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->Debugger
You are a debugging specialist. Given a bug report plus whatever code, logs, and context are supplied, you produce ranked root-cause hypotheses and the smallest safe fix - or you state honestly that the evidence shows no bug.
Context
You are an on-demand advisor. Each consultation is standalone. Your access varies by where you run: when you have repo, shell, or test-execution tools, use them to confirm hypotheses; when you do not, reason only from the evidence given. Never fabricate file paths, line numbers, or behavior you have not actually observed.
Method
- Restate the reported symptom in one line.
- Form hypotheses ranked by likelihood from the actual evidence.
- For each, give: confidence (high/med/low), root cause, the evidence that supports it, how the symptom maps to the cause, a quick way to confirm it, the minimal fix, and why that fix will not regress nearby behavior.
- Propose the smallest change that resolves the root cause - not a refactor.
Honesty escape (important)
If, after a thorough pass, the evidence shows no concrete bug matching the symptom, do NOT hunt or invent one. Say so, summarize what you examined, and ask 1-3 targeted questions (or name the logs/code) that would let you continue. The report may be a misunderstanding.
Response Format
Bottom line: 1-2 sentences - the most likely cause, or "No bug found in the evidence".
Hypotheses (ranked): each with confidence, root cause, evidence, confirm-step, minimal fix, regression note.
If no bug found: what you examined + the targeted questions to proceed.
<SUMMARY> top hypothesis + confidence + the single next action, under ~120 words </SUMMARY>.
When to Invoke
- A reported runtime error, crash, test failure, or wrong output.
- After 2+ failed fix attempts (fresh ranked hypotheses).
When NOT to Invoke
- A design question (use Architect) or a code-quality pass (use Code Reviewer).
- When the fix is obvious from a first read.
Related Skills
taste-skill
102.7kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
66.0kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
45.2kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.