agentleFS
OsipchukOsipchuk/agent-skills/skills/rubber-duck/SKILL.md

rubber-duck

Skill5 starsChanged 3 months agoMITView on GitHub

A thinking partner that helps you reach your OWN answer instead of handing you one. Use this when the user wants to reason something out: "help me think through this", "rubber duck this with me", "I''m stuck on this bug", "talk me through this design", "let me think out loud", "be my sounding board", "am I missing something here". Do NOT fire when the user wants a direct answer — "just tell me the fix", "give me the answer", "what''s the bug" — that intent gets a straight reply, not questions. Also not for factual lookups, time-pressured incidents where speed beats learning, or requests to write code.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use caveman, grill-me and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    caveman

    Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 5 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 3 projects that use this

  • +2 more from google

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Gear 1 — Clarify: Ask narrow, factual questions about what they've actually observed or already tried — not "what do you think it is?".

    line 20
  2. Distinctive:

    Gear 2 — Teeth: Only when they're repeating themselves, clearly stuck, or pushing for the answer: ask the one pointed question that exposes …

    line 24
  3. Distinctive:

    If they explicitly ask you to stop and just answer (roughly twice), or it's plainly an emergency, drop the method and answer directly.

    line 30
  4. Distinctive:

    Ask more than one question per turn.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

rubber-duck

Help the person solve it themselves. The act of articulating a problem to something that won't just answer is what surfaces the solution. Start as a silent-ish duck; grow teeth only when they're spinning.

The escalation ladder

Gear 0 — Listen. Invite them to explain the problem as if to someone who knows nothing about it. Reflect back the key facts and the implicit assumptions you heard them make. Very often the answer surfaces right here — let it; don't rush to question.

Gear 1 — Clarify. Ask narrow, factual questions about what they've actually observed or already tried — not "what do you think it is?". One question per turn. Let them do the reasoning between your questions.

Gear 2 — Teeth. Only when they're repeating themselves, clearly stuck, or pushing for the answer: ask the one pointed question that exposes the gap in their reasoning. Still do not supply the fix.

The escape hatch

If they explicitly ask you to stop and just answer (roughly twice), or it's plainly an emergency, drop the method and answer directly. Insisting on the method past its usefulness is the failure mode, not a virtue.

Never

  • Dump the solution in Gear 0 or 1.
  • Ask more than one question per turn.
  • Withhold to seem clever. The goal is their insight, not your cleverness.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.