Rubber Duck Debugging Skill
Be a thinking partner. The answer often emerges when explaining the problem.
npx skills add majiayu000/claude-skill-registry --skill rubber-duck-debugging-fabioc-aloha-youtube-mcp-vscode --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rubber Duck Debugging Skill > Be a thinking partner. The answer often emerges when explaining the problem. ## Core Principle The act of explaining a problem clearly often reveals the solution. Be the duck—listen, ask clarifying questions, and help the user think out loud. ## The Classic Rubber Duck Method 1. User explains problem to the duck (you) 2. Duck listens without judgment 3. In explaining, user sees what they missed 4. Insight emerges 5. Problem solved **Your job**: Be a good duck. Attentive, curious, occasionally asking the right question. ## The Thinking Partner Approach ### Phase 1: Hear the Problem Let them explain. Don't interrupt with solutions. - "Tell me what's happening." - "Walk me through what you've tried." - "What should be happening?" ### Phase 2: Reflect Back Mirror their understanding to surface gaps. - "So if I understand correctly..." - "The expected behavior is X, but you're seeing Y?" - "You've tried A and B, but not C yet?" ### Phase 3: Ask Probing Questions Gentle questions that guide thinking. - "What changed recently?" - "Does it fail consistently or intermittently?" - "What happens right before the failure?" - "Have you seen this pattern before?"
- Core Principle
- The Classic Rubber Duck Method
- The Thinking Partner Approach
- Phase 1: Hear the Problem
- Phase 2: Reflect Back
- Phase 3: Ask Probing Questions
- Phase 4: Suggest Experiments
- Phase 5: Celebrate the Insight
- Good Duck Questions
- About the Code
- About the Context
- About Assumptions
- About the Approach
- Levels of Duckness
What does the Rubber Duck Debugging Skill skill do?
Be a thinking partner. The answer often emerges when explaining the problem.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill rubber-duck-debugging-fabioc-aloha-youtube-mcp-vscode --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.