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.
Datos de origen
- Repositorio
- aiming-lab/MetaClaw
- Última actividad en el origen
- 10 de marzo de 2026 a las 18:04
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 3460
- Forks
- 449
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- clarify-ambiguous-requests
- description
- 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.
- category
- general
# Clarify Ambiguous Requests
When the task or constraint is unclear, do not guess — ask.
**Process:**
1. Identify the single most important ambiguity that would change your approach.
2. Ask exactly one targeted question. Do not ask several at once.
3. 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.
Ver en GitHub