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.
소스 정보
- 저장소
- aiming-lab/MetaClaw
- 최근 소스 활동
- 2026년 3월 10일 18:04
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3,456
- 포크
- 450
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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.
GitHub에서 보기