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
codebase-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.
12avoid-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.
11plan-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.
9task-decomposition
Use this skill when a user presents a large, vague goal. Break it into concrete, ordered sub-tasks before starting any work. Apply whenever the request is larger than a single focused action.
9data-validation-first
Use this skill before any data analysis, transformation, or modeling. Always inspect and validate the data before drawing conclusions or writing transformations.
9structured-progress-update
Use this skill when summarizing progress on an ongoing project or multi-step task. Give a clear, scannable status report whenever asked for an update or at the end of a work session.
9