aiskillstore/epistemic-checkpoint
skills/ancplua/epistemic-checkpoint/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace epistemic-checkpointInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 28, 2026, 6:17 PM36.2s2 files scanned
SKILL.md
- name:
- epistemic-checkpoint
- description:
- |
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
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
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:
"If targeting .NET 10 preview, use C# 14 extension types..."
CORRECT:
"Let me verify .NET 10 status... [WebSearch] ...
.NET 10 is LTS (released November 2025), not preview.
Standard extension methods work fine."
WRONG:
"React 19 is still in beta, so..."
CORRECT:
"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:
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...
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026