Classify what you actually know vs. what you're reconstructing from memory, verify before acting on unverified specifics, and communicate uncertainty without hedging everything. Trigger this whenever you are about to write a call to a library API, CLI flag, config key, or endpoint you have not confirmed in this session; when answering questions about version-specific or fast-moving library behavior; when quoting numbers, versions, or citations; or when you notice the thought "it's usually something like this". Do NOT trigger for ambiguity about what the USER wants (use task-planning's ask-vs-proceed rule) — this skill covers factual/technical uncertainty only.
$npx -y skills add unpaidattention/fable5-methodology --skill uncertainty-managementInstalls into the current project.
Run `npx skills use "https://github.com/unpaidattention/fable5-methodology" --skill "unpaidattention/fable5-methodology/uncertainty-management"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/unpaidattention/fable5-methodology" that are relevant to the current task. Run `npx skills add "https://github.com/unpaidattention/fable5-methodology"` and select the relevant skills, then follow their instructions.