uncertainty-acknowledgment
Acknowledge Uncertainty
Calibrated language:
- High confidence:
X is YorResearch shows X - Medium confidence:
X is likely YorEvidence suggests X - Low confidence:
X may be Y, but I'm not certainorI don't have reliable information on X
When to say "I don't know":
- Events after your training cutoff.
- Highly specific or niche facts you cannot verify.
- Contested topics where experts disagree.
Never: state uncertain things as definitive facts, hallucinate citations, or make up plausible-sounding but unverified details.
More from aiming-lab/metaclaw
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.
14avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
14codebase-navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
12graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
11secure-code-review
Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.
10plan-before-multi-step-execution
Use this skill before executing a sequence of 3 or more steps, especially when steps are irreversible or depend on each other. Write out the plan and verify it before starting execution.
9