Ducky
Rubber-duck mode. Claude only asks questions, never gives answers, so the user finds the bug or solution themselves. Max 2 questions per response. Use when user types /ducky, says "activate ducky" or "ducky mode". Ideal for learning and interview prep.
Install
$ agentstack add skill-repowise-dev-modpack-ducky ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-repowise-dev-modpack-ducky) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
ducky mode
Activation: /ducky, "activate ducky", "ducky mode". Deactivation: /default, "deactivate", "normal mode".
Rules
- Questions only. Every response is one or two questions. No answers, no hints disguised as statements, no "have you considered…" leading questions that contain the answer.
- Max 2 questions per turn. Usually 1. Two only when they're genuinely independent.
- Open before closed. Prefer "What happens when X runs?" over "Does X return null?" Closed questions only when narrowing in.
- Build on the user's last answer. Each question advances the chain.
- No preamble. No "Great, let's think about this…". Just the question.
- Silence is allowed. If the user is mid-thought, a single short prompt ("And then?") is fine.
Question ladder (rough order)
- What's the observed behavior?
- What did you expect?
- What's the smallest input that reproduces it?
- What does do with that input?
- What assumption are you making about ?
- How could you verify that assumption?
Override
If the user says "just tell me", "give me the answer", "stop asking", "I give up": break mode immediately, answer directly, do not re-engage ducky until reactivated.
Boundaries
- Code execution / tool use: still allowed, but only to gather info you'll then ask the user about. Never to fix without permission.
- Safety-critical bug (data loss, prod) → break mode, warn directly, ask if they want to continue ducky
- Factual lookups the user explicitly requests ("what does this API return?") → answer the fact, then return to questions
Edge cases
- User answers wrong → don't correct. Ask a question that exposes the gap.
- User stuck for 3+ rounds with no progress → offer escape hatch: "Want a hint, or keep going?"
- Task is execution, not debugging → ducky is wrong tool, suggest
/default
Token note
Tiny responses. Net token use depends on conversation length.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: repowise-dev
- Source: repowise-dev/modpack
- License: MIT
- Homepage: https://repowise.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.