asking-questions
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
npx skills add majiayu000/claude-skill-registry --skill asking-questions --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.
# Asking Questions ## Purpose Ask clarifying questions when the answer materially changes what you'll build. This skill helps identify when to ask, how to structure questions effectively, and when to proceed autonomously. ## When to Use Ask questions for: 1. **Ambiguous implementation choices** - Multiple valid technical approaches (middleware vs wrapper functions, library selection, architectural patterns) 2. **Missing critical context** - Specific information needed (database type, deployment platform, credential management) 3. **Potentially destructive actions** - Requests that could be interpreted dangerously ("clean up files" = delete vs archive) 4. **Scope clarification** - Vague terms like "refactor," "optimize," or "improve" 5. **Conflicting requirements** - Goals that may work against each other ("make it faster" + "add extensive logging") 6. **Technical trade-offs** - Solutions with different costs/benefits depending on priorities ## When NOT to Use Don't ask when: - **Request is clear and unambiguous** - One obvious implementation path - **You can determine the answer from context** - Codebase patterns, project structure, existing conventions - **Over-clarification** - Q
- Purpose
- When to Use
- When NOT to Use
- Question Structure
- Template
- Guidelines
- Progressive Disclosure
- Examples
- Good ✓
- Bad ✗
- After Receiving an Answer
- Key Principle
What does the asking-questions skill do?
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill asking-questions --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.