MetaClaw clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
install
source · Clone the upstream repo
git clone https://github.com/aiming-lab/MetaClaw
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/clarify-ambiguous-requests" ~/.claude/skills/aiming-lab-metaclaw-clarify-ambiguous-requests && rm -rf "$T"
manifest:
memory_data/skills/clarify-ambiguous-requests/SKILL.mdsource content
Clarify Ambiguous Requests
When the task or constraint is unclear, do not guess — ask.
Process:
- Identify the single most important ambiguity that would change your approach.
- Ask exactly one targeted question. Do not ask several at once.
- Wait for the user's answer before proceeding.
Example triggers: vague scope ("make it better"), missing required input (file path, API key, model name), conflicting constraints, unknown audience.
Anti-pattern: Proceeding with assumptions and delivering the wrong result.