epistemic-checkpoint

Included with Lifetime

$97 forever

Force verification before answering questions involving versions, dates, status, or "current" state. Prevents hallucinations at the REASONING level by checking assertions.yaml and WebSearch before forming beliefs. Triggers on software versions, release status, dates, and package versions.

General

What this skill does


# Epistemic Checkpoint

Force verification before answering questions involving versions, dates, status, or "current" state.

## Purpose

Prevents the ROOT CAUSE of hallucinations - not just blocking wrong output, but preventing wrong
REASONING. Claude's training data is stale; this skill forces verification before forming beliefs.

## Triggers

Activate this skill when the question involves ANY of:

- Software versions (.NET, Node, React, Python, etc.)
- Release status (preview, LTS, GA, RC, deprecated)
- "Current" or "latest" anything
- Dates that might be after training cutoff
- Package versions
- API deprecations

## MANDATORY Protocol

### Step 1: Recognize Uncertainty

Say to yourself: **"My training data may be stale for: [topic]"**

### Step 2: Check Local Ground Truth

```text
Read ${CLAUDE_PLUGIN_ROOT}/blackboard/assertions.yaml
Search for relevant entries
```

If found - use that value with high confidence.

### Step 3: If Not in Assertions - WebSearch

```text
WebSearch("[software] [version] release date site:official-docs")
WebSearch("[software] LTS release 2025")
```

Prefer official sources:

- microsoft.com/dotnet for .NET
- nodejs.org for Node
- python.org for Python

### Step 4: State Verified Facts

Say: **"Based on [source], [software] [version] is [status] as of [date]."**

### Step 5: THEN Proceed

Only now answer the actual question with the verified baseline.

## Red Flag Thoughts (REJECT THESE)

| If you think... | Actually do... |
|-----------------|----------------|
| "I'm pretty sure .NET 10 is..." | WebSearch to verify |
| "This is probably still preview" | Check assertions.yaml |
| "I remember this from training" | Training is stale, verify |
| "This is a simple factual question" | Simple facts are often WRONG |
| "The user said it's preview" | User might be wrong too, verify |

## Anti-Pattern Examples

**WRONG:**

```text
"If targeting .NET 10 preview, use C# 14 extension types..."
```

**CORRECT:**

```text
"Let me verify .NET 10 status... [WebSearch] ...
.NET 10 is LTS (released November 2025), not preview.
Standard extension methods work fine."
```

**WRONG:**

```text
"React 19 is still in beta, so..."
```

**CORRECT:**

```text
"Checking React 19 status... [WebSearch] ...
React 19 was released December 2024 as stable.
Proceeding with React 19 stable patterns."
```

## Common Danger Patterns

| Topic | Danger Pattern | Likely Truth |
|-------|----------------|--------------|
| .NET | "preview", "not released" | .NET 10 LTS since Nov 2025 |
| React | "beta", "experimental" | React 19 stable since Dec 2024 |
| Node | "current" without version | Always specify exact version |
| Python | "3.x is latest" | Verify - 3.13+ exists |

## Output Format

When this skill activates, structure your verification as:

```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...
```

Files: 2

Size: 13.9 KB

Complexity: 20/100

Category: General

Source: https://github.com/aiskillstore/marketplace/tree/main/skills/ancplua/epistemic-checkpoint

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts