rubber-duck Skill
High-signal feedback on plans, designs, implementations, and partial progress. Catches bugs, logic errors, and design flaws that may not be apparent to the original author. Call this skill for any non-trivial task to get a second opinion — the best time is after planning but before implementing. Call it early and often Published by microsoft in vscode-team-kit.
What is rubber-duck Skill?
High-signal feedback on plans, designs, implementations, and partial progress. Catches bugs, logic errors, and design flaws that may not be apparent to the original author. Call this skill for any non-trivial task to get a second opinion — the best time is after planning but before implementing. Call it early and often Published by microsoft in vscode-team-kit. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use rubber-duck Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-team-kit
- Skill file: rubber-duck/skills/rubber-duck/SKILL.md
What it does
High-signal feedback on plans, designs, implementations, and partial progress. Catches bugs, logic errors, and design flaws that may not be apparent to the original author. Call this skill for any non-trivial task to get a second opinion — the best time is after planning but before implementing. Call it early and often
Skill instructions
Skill: Rubber Duck Constructive, high-signal feedback on whatever the user is working on — plans, designs, implementations, tests, or partial progress towards a goal. Acts as a devil's advocate: "why might this not work?" and "what could be improved?" Use this skill early and often. Catching issues during development is cheaper than catching them in review. How to run 1. Pick the subagent model from the table below. 2. Launch a general-purpose subagent with the critic prompt at the end of this file. 3. Fill in the <placeholders with a summary of what to review and how to inspect it. Give the subagent enough to orient — intent, files involved, risk areas — but do not paste raw diffs or full file contents. The subagent reads files itself. Model selection Choose a complementary, higher-order model so the critique comes from a different perspective: | Your model | Subagent model | |---|---| | Claude Sonnet (any) | Claude Opus 4.7 | | Claude Opus (any) | GPT 5.5 | | Claude Haiku (any) | Cla
Explore related resources
Frequently asked questions
What is rubber-duck?
rubber-duck is a open-source AI agent skill with Copy skill directory. High-signal feedback on plans, designs, implementations, and partial progress. Catches bugs, logic errors, and design flaws that may not be apparent to the original author.
Who is rubber-duck best for?
rubber-duck is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install rubber-duck?
Install or run rubber-duck using Copy skill directory. Check rubber-duck for the latest setup command.
Is rubber-duck actively maintained?
rubber-duck may need a closer maintenance check before production use.
Auto-fetched from GitHub.
