rubber-duck

Guide users through structured, purpose-labeled questions to surface hidden assumptions.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/FrogAi/Xenopus --skill rubber-duck-frogai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rubber-duck
Source: https://github.com/FrogAi/Xenopus/tree/main/Gemini/Skills/Gemini%203.1%20Pro/rubber-duck
Command: npx skills add https://github.com/FrogAi/Xenopus --skill rubber-duck-frogai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rubber-duck mode helps users think through problems by prompting with clarifying questions instead of giving direct solutions, making implicit assumptions explicit and guiding user to their own conclusions.

Core Features & Use Cases

  • One primary question per turn, with a labeled purpose to improve reasoning.
  • Gentle, non-solution-focused exploration that surfaces assumptions, gaps, and alternatives.
  • Exit mechanism to switch to solving mode on explicit user request.

Quick Start

Ask the user to restate the problem and start with a single clarifying question to expose underlying assumptions.

Frequently Asked Questions about rubber-duck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use clarifying questions to debug a problem instead of looking for direct solutions?

Structured clarifying questions debug problems by forcing you to restate the issue and expose hidden assumptions, guiding you to your own conclusions rather than providing direct solutions.

What is the rubber duck debugging technique and how does it help with critical thinking?

Rubber duck debugging is an interactive questioning technique that helps critical thinking by prompting you with one purpose-labeled question per turn to surface implicit assumptions and gaps in your reasoning.

How do I surface hidden assumptions when reasoning through a complex technical issue?

You surface hidden assumptions by engaging in non-solution-focused exploration, cycling through clarification and reflection phases that incrementally reveal gaps and alternatives before reaching a conclusion.

Can I switch from a questioning mode to getting a direct solution when I am ready?

Yes, you can switch to solving mode through an explicit exit mechanism, requesting a direct solution whenever you feel you have sufficiently explored the problem and exposed your underlying assumptions.

Does this questioning approach work for debugging tasks across different technical domains?

Yes, this question-first reasoning approach is designed for debugging and thinking tasks across domains, helping you incrementally build insights regardless of the specific technical environment.

What is the best way to start a conversation that reveals assumptions in my logic?

The best way to start is to restate the problem, followed by a single clarifying question designed to expose underlying assumptions and prompt structured, purpose-labeled exploration.