MetaClaw avoid-acting-on-assumptions
Common mistake — proceeding with assumptions about ambiguous requirements instead of asking a clarifying question first. This skill reminds you to stop and ask before acting on uncertain interpretations.
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/avoid-acting-on-assumptions" ~/.claude/skills/aiming-lab-metaclaw-avoid-acting-on-assumptions && rm -rf "$T"
manifest:
memory_data/skills/avoid-acting-on-assumptions/SKILL.mdsource content
Avoid Acting on Assumptions
Mistake pattern: User says something ambiguous → you assume the most likely interpretation → you deliver something → it's wrong.
Fix: When requirements are ambiguous, ask ONE clarifying question. The cost of pausing to ask is always lower than the cost of delivering the wrong result.
Especially risky assumptions:
- The target programming language or framework.
- Whether a file should be overwritten or appended.
- What "clean up" or "improve" means in context.
- Whether a test environment or production is the target.