memory_data/skills/avoid-acting-on-assumptions/SKILL.md
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.
npx skillsauth add aiming-lab/metaclaw avoid-acting-on-assumptionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
development
Use this skill when creating charts, plots, or dashboards. Choose the visualization type that best communicates the data relationship before writing any plotting code.
testing
Use this skill before taking any action that is hard to reverse — deleting files, overwriting data, sending messages, pushing to remote, modifying production systems. Always pause, state what you are about to do, and confirm before executing.
research
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
tools
Use this skill when deciding which tools to call in an agentic workflow. Always choose the minimal, most direct tool for each step and avoid redundant or speculative tool calls.