never-guess

Enforce uncertainty admission and prohibit fabricated facts in responses.

3|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/rayk/lucid-toolkit --skill never-guess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: never-guess
Source: https://github.com/rayk/lucid-toolkit/tree/main/plugins/luc/skills/never-guess
Command: npx skills add https://github.com/rayk/lucid-toolkit --skill never-guess

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Behavioral principle ensuring Claude never guesses when uncertain. Use when Claude's response involves facts it cannot verify, technical claims, or any statement where accuracy matters. Complements resolve-ambiguity skill.

Core Features & Use Cases

  • Admit uncertainty openly
  • Never fabricate or hallucinate
  • Offer user control over next steps
  • Integrates with resolve-ambiguity for tiered lookups

Quick Start

When uncertain, respond: "I'm not sure about [specific thing]. Would you like me to search authoritative sources, provide what I know, or check the context/files you've shared?"

Frequently Asked Questions about never-guess

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Claude from guessing or hallucinating when I'm unsure about facts?

Admit uncertainty explicitly instead of guessing. When uncertain about factual, technical, or current information, say 'I'm not sure about [specific thing]' and offer options: search authoritative sources, provide what you know, or check shared context. This prevents fabricated facts and keeps accuracy critical.

When should I use uncertainty acknowledgment instead of a confident answer?

Use it for factual claims, technical statements, current information, or any task where accuracy matters. If you cannot verify a fact from reliable context or knowledge, admit the gap openly rather than fabricate. This ensures responses stay truthful and user-directed.

How do I handle uncertain responses while still moving forward with my task?

Offer user control over next steps. Ask whether they want you to search online sources, provide partial knowledge, verify against files they've shared, or explore other resolution paths. This integrates uncertainty admission with tiered lookup workflows for verified information.

Can I use this approach alongside other verification methods?

Yes. This skill complements resolve-ambiguity for tiered lookups. Combine explicit uncertainty admission with web search, context review, or file verification to produce accurate, well-sourced answers instead of guesses.

What's the difference between admitting uncertainty and refusing to answer?

Admitting uncertainty means stating what you don't know while offering options to resolve it—search, partial knowledge, or verification. Refusing stops engagement. Uncertainty admission keeps the workflow active and user-directed toward verified facts.