uncertainty-verification

Uncertainty Verification

Overview

This skill forces verification before stating any specific technical detail that could vary by version, environment, or specification.

Use when...

• The request asks for exact command syntax, flags, or configuration keys
• The answer depends on version-specific behavior, deprecations, or recent changes
• The request involves standards/specs (RFCs, protocol behavior, i18n/timezone/locale rules)
• The user asks for exact file paths, naming conventions, or directory structures
• The answer requires library-specific APIs (class names, method signatures, constants)
• Any part of the response would otherwise be based on “typical patterns” or memory

Symptoms / keywords

Use this skill when the prompt contains or implies keywords like:

• “exact”, “precise”, “verbatim”, “copy/paste”, “flags”, “CLI”, “config key”, “endpoint”, “params”
• “deprecated”, “since vX”, “in 2025”, “changed in”, “breaking change”, “migration”
• “RFC”, “spec”, “standard”, “format”, “timezone”, “locale”, “i18n”, “OAuth”, “HTTP”, “GraphQL”
• “directory structure”, “file path”, “naming convention”, “default location”
• Specific error codes/messages that must be accurate

Technical Details Requiring Verification

Don't provide these specific details without checking official documentation:

• ❌ Exact file paths, directory structures, or naming conventions
• ❌ Specific API endpoints, parameter names, or response formats
• ❌ Exact command syntax, flags, or configuration keys
• ❌ Version-specific features or deprecations
• ❌ Specific error codes or messages
• ❌ Hostname patterns, URL formats, or connection string syntax
• ❌ Library-specific class names, method signatures, or constants

Required response pattern when uncertain:

"I need to verify this with official documentation. Let me check..."
→ Dispatch a research subagent to execute Context7 or Web fetch and return a Context Package with citations
→ Cite the source explicitly