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.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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.
- Repository
- aiming-lab/MetaClaw
- Commit
922caf3
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.