fact-check
Verify claims in generated output against sources. Use as a separate pass AFTER content generation to catch hallucinations. Critical constraint - cannot be reliably combined with generation in a single pass.
What this skill does
# Fact-Check Skill
Systematic verification of claims in generated content. Designed to catch hallucinations, confabulations, and unsupported assertions.
## Why Separate Passes Matter
**The Fundamental Problem:** LLMs generate plausible-sounding content by predicting what should come next. This same mechanism produces hallucinations—confident statements that feel true but aren't. An LLM in generation mode cannot reliably catch its own hallucinations because:
1. **Attention is on generation**, not verification
2. **Coherence pressure** makes false claims feel correct in context
3. **Same weights** that produced the error will confirm it
4. **No external grounding** to contradict the confabulation
**The Solution:** Verification must be a separate cognitive pass with:
- Fresh attention focused solely on each claim
- Explicit source checking (not memory/training data)
- Adversarial stance toward the content
- External grounding where possible
## Diagnostic States
### F1: No Verification Pass
**Symptoms:** Content generated and delivered without any fact-checking.
**Risk:** Hallucinations pass through undetected.
**Intervention:** Run verification pass before delivery. Extract claims, check each against sources.
### F2: Self-Verification (Invalid)
**Symptoms:** Same pass asked to "check your facts" while generating.
**Risk:** False confidence—errors confirmed by same process that created them.
**Intervention:** Complete generation first, then run separate verification pass with explicit source requirements.
### F3: Memory-Based Verification (Unreliable)
**Symptoms:** Claims checked against "what I know" without external sources.
**Risk:** Hallucinations verified by hallucinated knowledge.
**Intervention:** Require explicit source citation for each verified claim. If no source available, mark as unverified.
### F4: Selective Verification
**Symptoms:** Only some claims checked; others assumed correct.
**Risk:** Unchecked claims may contain errors.
**Intervention:** Systematic extraction of ALL verifiable claims. Check each, or explicitly mark unchecked items.
### F5: Verification Complete
**Symptoms:** All claims extracted, each checked against sources, confidence levels assigned.
**Indicators:** Source citations present, unverified claims marked, confidence explicit.
## The Verification Process
### Phase 1: Claim Extraction
Extract every verifiable statement from the content.
**Claim types to extract:**
- Factual assertions ("X is Y", "X causes Y")
- Statistics and numbers ("40% of...", "in 2023...")
- Attributions ("According to X...", "Research shows...")
- Definitions ("X means...", "X is defined as...")
- Historical claims ("X happened in...", "X was founded by...")
- Causal claims ("X leads to Y", "X prevents Y")
- Comparative claims ("X is better than Y", "X is the largest...")
**What to skip:**
- Opinions clearly marked as such
- Hypotheticals and speculation (if labeled)
- Logical deductions from stated premises
- Direct quotes (verify attribution, not content)
### Phase 2: Claim Categorization
Categorize each claim by verifiability:
| Category | Description | Verification Strategy |
|----------|-------------|----------------------|
| **Verifiable-Hard** | Numbers, dates, names, quotes | Must match source exactly |
| **Verifiable-Soft** | General facts, processes, mechanisms | Source should substantially support |
| **Attribution** | "X said...", "According to..." | Verify source exists and said something similar |
| **Inference** | Conclusions drawn from evidence | Verify premises, assess reasoning |
| **Opinion-as-Fact** | Subjective claim stated as objective | Flag for rewording or qualification |
### Phase 3: Source Verification
For each claim, attempt verification:
```markdown
## Claim Verification Log
### Claim 1: "[exact claim text]"
- **Category:** [Verifiable-Hard/Soft/Attribution/Inference]
- **Source checked:** [specific source]
- **Finding:** [Confirmed/Partially supported/Not found/Contradicted]
- **Confidence:** [High/Medium/Low]
- **Notes:** [discrepancies, qualifications needed]
### Claim 2: ...
```
**Verification outcomes:**
| Outcome | Meaning | Action |
|---------|---------|--------|
| **Confirmed** | Source explicitly supports claim | Keep, cite source |
| **Partially supported** | Source supports part, not all | Qualify or narrow claim |
| **Not found** | No source located | Mark unverified, consider removing |
| **Contradicted** | Source says opposite | Remove or correct |
| **Outdated** | Source is dated; current state may differ | Update or add recency caveat |
### Phase 4: Confidence Assignment
Assign overall confidence to the content:
| Level | Criteria |
|-------|----------|
| **High** | All key claims verified; no contradictions found |
| **Medium** | Most claims verified; some unverified but plausible |
| **Low** | Significant claims unverified; some corrections needed |
| **Unreliable** | Multiple contradictions found; major revision needed |
## Hallucination Patterns
Common hallucination types to watch for:
### 1. Plausible Fabrication
**Pattern:** Specific details that sound right but don't exist.
**Examples:** Fake paper citations, non-existent statistics, invented quotes.
**Detection:** Verify specific claims against primary sources.
### 2. Confident Extrapolation
**Pattern:** Reasonable inference stated as established fact.
**Examples:** "Studies show..." (no specific study), "Experts agree..." (no citation).
**Detection:** Require specific source for any claim of external support.
### 3. Temporal Confusion
**Pattern:** Mixing information from different time periods.
**Examples:** Old statistics presented as current, defunct organizations described as active.
**Detection:** Check dates on sources, verify current status.
### 4. Attribution Drift
**Pattern:** Correct information attributed to wrong source.
**Examples:** Quote assigned to wrong person, finding attributed to wrong study.
**Detection:** Verify attribution specifically, not just content.
### 5. Amalgamation
**Pattern:** Combining details from multiple sources into one fictional source.
**Examples:** Invented study that combines real findings from separate papers.
**Detection:** Verify the specific source exists and contains all attributed claims.
### 6. Precision Inflation
**Pattern:** Adding false precision to vague knowledge.
**Examples:** "Approximately 47.3%" when only "about half" is supported.
**Detection:** Check if source actually provides that level of precision.
## Verification Checklist
Before releasing fact-checked content:
- [ ] **Claims extracted?** All verifiable statements identified
- [ ] **Sources checked?** Each claim verified against external source
- [ ] **Specific, not memory?** Verification used actual sources, not LLM training data
- [ ] **Contradictions flagged?** Conflicts between claims and sources noted
- [ ] **Unverified marked?** Claims without sources explicitly identified
- [ ] **Confidence stated?** Overall reliability level communicated
- [ ] **Separate pass?** Verification done after generation, not during
## Integration with Research Skill
| Research Phase | Fact-Check Role |
|----------------|-----------------|
| **During research** | Verify claims in sources themselves |
| **After synthesis** | Verify that synthesis accurately represents sources |
| **Before delivery** | Final pass to catch hallucinations in output |
**Handoff pattern:**
1. Research skill gathers and synthesizes information
2. Content is generated based on research
3. Fact-check skill runs as separate pass
4. Corrections made, confidence assigned
5. Output delivered with verification status
## Operational Constraints
### What This Skill Cannot Do
1. **Verify during generation** — Must be separate pass
2. **Catch all hallucinations** — Some may slip through
3. **Verify without sources** — No sources = unverified, not "verified by knowledge"
4. **Replace domain expertise** — Can check sources exist, not Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.