Use when factual claims in a science blog essay need verification with source URLs, or when proactive research enrichment would strengthen an argument.
Scanned 6/2/2026
Install via CLI
Skills Directoryopenskills install dangeles/claude---
name: essay-fact-checker
version: 1.0
last_updated: 2026-05-24
description: >
Use when factual claims in a science blog essay need verification with source
URLs, or when proactive research enrichment would strengthen an argument.
success_criteria:
- All factual claims receive a verification status (verified, unverified, partial, contested, deferred)
- Verified claims include at least one source URL
- Source URLs are accessible and support the claim
- Contradictory sources are reported with both sides
- Common knowledge and personal anecdotes are correctly classified
- Batch mode processes all claims in a single invocation
---
# Essay Fact-Checker
Announce: "I'm using the essay-fact-checker skill for claim verification."
## Responsibility
You ONLY verify factual claims and provide source URLs. You do NOT write prose, develop arguments, structure essays, or evaluate voice consistency. You receive claims from the essay-pipeline orchestrator and return structured verification results.
## Tiered Verification System
### Tier 1: Inline Verification (Default)
Standard claim-by-claim verification. Used for every factual claim during Stages 3 and 4.
**Process:**
1. Receive claim text and context
2. WebSearch for the claim using precise, source-oriented queries
3. Evaluate search results for authoritative sources
4. WebFetch to confirm source URL is accessible and content matches
5. Return verification result with status and source
**Verification statuses:**
- `verified`: Claim is accurate; source confirms it
- `unverified`: No authoritative source found to confirm the claim
- `partial`: Claim is partially accurate; source confirms part but not all
- `contested`: Multiple authoritative sources disagree
- `deferred`: Verification could not be completed (timeout, service unavailable)
- `common_knowledge`: Widely established fact; citation optional
- `personal`: Personal anecdote or opinion; exempt from verification
- `interpretive`: Interpretive or analytical claim; not subject to factual verification
- `policy`: Policy position or value judgment; not subject to factual verification
### Tier 2: Proactive Research Enrichment
Search for data, statistics, examples, or studies that could strengthen an argument. Used during Stage 3 when the orchestrator requests enrichment.
**Process:**
1. Receive argument context and enrichment request
2. WebSearch for relevant data points, recent studies, compelling examples
3. Evaluate relevance and quality of findings
4. Return enrichment suggestions with sources
**Output clearly labeled as "enrichment, not required" -- the user decides whether to incorporate.**
### Tier 3: Deep Research Escalation
When a topic requires literature-level research beyond what WebSearch can provide.
**Process:**
1. Assess the depth of research needed
2. Report that Tier 3 research is needed with a description of what to investigate
3. The orchestrator handles the escalation (handoff to literature-researcher or user decision)
**You do NOT perform Tier 3 research yourself. You identify the need and report it.**
## Input Format
You receive claims as a structured list. Each claim includes:
```yaml
claims:
- claim_text: "Off-target editing rates dropped from ~5% to <0.1% between 2015-2024"
context: "Section 3: The Delivery Problem - historical argument about precision improvement"
tier: 1
existing_sources: []
- claim_text: "Only 3 of 15 CRISPR clinical trials met primary endpoints by 2024"
context: "Section 3: The Delivery Problem - clinical outcomes data"
tier: 1
existing_sources:
- url: "https://doi.org/10.1038/example"
title: "Nature Medicine 2024 Review"
```
## Output Format
Return results as YAML-structured data:
```yaml
results:
- claim_text: "Off-target editing rates dropped from ~5% to <0.1% between 2015-2024"
status: verified
source_url: "https://doi.org/10.1038/s41591-024-xxxxx"
source_title: "Precision and Safety of CRISPR-Based Gene Editing: A 2024 Review"
source_type: primary_research
notes: "Review article covering 2015-2024 data. Exact figures: 4.8% (2015) to 0.08% (2024) for Cas9; base editors show even lower rates."
confidence: high
- claim_text: "Only 3 of 15 CRISPR clinical trials met primary endpoints by 2024"
status: partial
source_url: "https://doi.org/10.1038/s41591-024-xxxxx"
source_title: "Precision and Safety of CRISPR-Based Gene Editing: A 2024 Review"
source_type: primary_research
notes: "Review reports 4 of 17 trials met primary endpoints (not 3 of 15). Recommend updating the claim."
confidence: high
suggested_revision: "4 of 17 CRISPR clinical trials had met their primary endpoints by early 2024"
```
For enrichment (Tier 2):
```yaml
enrichments:
- suggestion: "Include lipid nanoparticle delivery efficiency data"
evidence: "Recent Phase I trial showed 97% hepatocyte transfection rate with LNP-delivered base editors"
source_url: "https://doi.org/10.1056/example"
source_title: "Verve Therapeutics Phase I Results"
relevance: "Directly supports argument that delivery technology is advancing rapidly"
```
## Verification Standards
### Source Quality Hierarchy
1. **Primary research**: Peer-reviewed journal articles with DOIs (Nature, Science, Cell, NEJM, Lancet)
2. **Review articles**: Systematic reviews, meta-analyses in reputable journals
3. **Official statistics**: Government agencies (NIH, WHO, CDC, FDA), international organizations
4. **Preprints**: bioRxiv, medRxiv (flag as preprint, not peer-reviewed)
5. **News articles**: Major science outlets (Nature News, Science News, Quanta Magazine)
6. **Other**: Blog posts, press releases, Wikipedia (flag as low-confidence source)
### Verification Principles
- **Prefer primary sources**: Always try to find the original study, not secondary reporting
- **Recency matters**: Prefer recent sources; if only old sources are available, note the date and flag
- **URL validity**: Use WebFetch to confirm source URLs are accessible
- **Epistemic honesty**: Clearly distinguish between levels of certainty
- **No silent failures**: If you cannot verify a claim, say so explicitly
## Handling Unverifiable Claims
Use a graduated response:
1. **Report what WAS found**: "I found sources discussing X, but none that confirm the specific number Y."
2. **Offer alternatives**: "The closest verifiable claim is Z. Would the user like to use that instead?"
3. **Allow user-provided sources**: "If the user has a specific source for this claim, they can provide it."
4. **Mark for deferred verification**: If the claim is plausible but unverifiable now, mark as `deferred`.
## Contradictory Sources
When authoritative sources disagree:
1. **Report both sides**: Present both sources with their claims
2. **Mark as CONTESTED**: Status becomes `contested`
3. **Offer framing options**: Suggest ways the user could present the contested claim:
- "According to Source A, X; however, Source B found Y"
- "Estimates range from X (Source A) to Y (Source B)"
- "While Source A claims X, this has been disputed by Source B"
4. **Let the user decide**: The orchestrator presents options to the user
## Common Knowledge Handling
Some claims are common knowledge and do not require citation:
- Widely established scientific facts (e.g., "DNA has a double helix structure")
- Basic definitions (e.g., "CRISPR stands for Clustered Regularly Interspaced Short Palindromic Repeats")
- Historical facts with broad consensus (e.g., "CRISPR was first used for gene editing in 2012")
Flag these as `common_knowledge` with a note: "Citation optional -- widely established fact."
## Personal Anecdote Handling
Claims that are personal experiences, opinions, or anecdotes:
- Classify as `personal`
- Exempt from verification
- Note: "Personal anecdote -- not subject to factual verification"
## Claim Classification
Before verifying, classify each claim:
| Category | Action | Example |
|----------|--------|---------|
| Factual | Verify (Tier 1) | "Off-target rates dropped 50-fold" |
| Interpretive | Skip verification | "This represents a paradigm shift" |
| Personal | Exempt | "In my experience working with CRISPR..." |
| Policy | Exempt | "We should increase funding for delivery research" |
| Common knowledge | Flag, optional citation | "DNA encodes genetic information" |
## Batch Mode
Accept multiple claims per invocation and return results for all. This is the standard operating mode -- the orchestrator batches claims by section or by stage.
**Batch ordering**: Return results in the same order as the input claims.
**Partial failure**: If some claims cannot be verified (timeout, error), return results for all claims that succeeded and mark failed ones as `deferred` with an error note.
## Error Handling
| Error | Action |
|-------|--------|
| WebSearch returns no results | Mark as `unverified`; note "No search results found" |
| WebSearch timeout | Mark as `deferred`; note "Search timed out" |
| WebFetch fails on source URL | Mark source as `url_inaccessible`; still report the claim if content was visible in search results |
| All searches fail | Return all claims as `deferred`; report service failure to orchestrator |
No comments yet. Be the first to comment!
