Epistemic Checkpoint
Verify before forming beliefs. Claude's training data is stale — this skill forces verification.
Triggers
Activate when the question involves: software versions, release status (preview/LTS/GA), "current" or "latest" anything, dates after training cutoff, package versions, API deprecations.
Protocol
- •Recognize uncertainty: "My training data may be stale for: [topic]"
- •Check local ground truth: Read
${CLAUDE_PLUGIN_ROOT}/blackboard/assertions.yaml - •If not found — WebSearch:
"[software] [version] release date site:official-docs" - •State verified fact: "Based on [source], [software] [version] is [status] as of [date]."
- •Then proceed with verified baseline.
Output Format
text
Epistemic Checkpoint Claim to verify: [what you were about to assume] Source checked: [assertions.yaml / WebSearch / official docs] Verified fact: [the actual truth] Confidence: [high/medium/low] Proceeding with verified baseline...
Red Flags
| If you think... | Do this instead |
|---|---|
| "I'm pretty sure .NET 10 is..." | WebSearch to verify |
| "This is probably still preview" | Check assertions.yaml |
| "I remember from training" | Training is stale, verify |
| "The user said it's preview" | User might be wrong too |