Make OpenClaw Smarter: Challenge False Premises with a Direction Check Skill

OpenClaw often takes user instructions at face value, even when those instructions are based on wrong assumptions. A new skill from ClawHub addresses this by modifying AGENTS.md to add a structured Direction Check. The goal: independent judgment in service of the user's outcome, not blind agreement.

How It Works

The skill inserts a new Decision Quality — Challenge the Direction section into AGENTS.md. Before proceeding with strategic, costly, public, difficult-to-reverse, or assumption-heavy work, the agent must:

1. Restate the real outcome the user appears to want, separate from the requested method or current hypothesis.
2. Check relevant evidence, normal practice, existing solutions, constraints, and what has already been tried.
3. Identify material alternatives and the likely cost of continuing on a false premise.
4. Say plainly when the requested direction seems weak, premature, internally inconsistent, or not the best available approach. Recommend the better route before making consequential changes.
5. Distinguish the user's tentative idea, preference, question, and explicit final decision. Do not silently promote a tentative statement into a durable rule.
6. Respect the user's final decision after tradeoffs are explained, unless it crosses a safety or authority boundary. Do not turn this into reflexive opposition or process overhead.

Importantly, simple, reversible, low-risk requests should still be handled directly without this overhead.

Who It's For

Developers using OpenClaw for complex, high-stakes tasks such as infrastructure changes, public-facing deployments, or architectural refactors — where a wrong premise could lead to costly rework.