fact-check-workflow
Structured workflow for fact-checking claims in journalism. Use when verifying statements for publication, rating claims for fact-check articles, or building pre-publication verification processes. Includes claim extraction, evidence gathering, rating scales, and correction protocols.
What this skill does
# Fact-check workflow
Fact-checking is systematic, not intuitive. This skill provides structure for claim verification, evidence documentation, and rating decisions.
## When to use
- Pre-publication fact-checking of articles
- Dedicated fact-check stories (rating claims)
- Verifying source statements during reporting
- Building fact-checking protocols for a newsroom
- Training staff on verification standards
## The fact-check process
```
1. Identify claim → 2. Research claim → 3. Gather evidence →
4. Contact sources → 5. Rate/verify → 6. Document → 7. Publish/correct
```
## Step 1: Claim extraction
### What to check
**Check:**
- Factual assertions ("X happened," "Y is true")
- Statistics and numbers
- Dates and timelines
- Quotes and attributions
- Causal claims ("X caused Y")
**Don't check (opinions):**
- "This policy is good/bad"
- "We should do X"
- Predictions about the future
- Matters of taste or preference
### Claim extraction template
```markdown
## Claim log
**Article/Source:** [where the claim appeared]
**Date:** [when]
### Claim 1
**Statement:** [exact quote or paraphrase]
**Speaker:** [who said it]
**Context:** [surrounding context]
**Type:** [statistic/historical/quote/causal]
**Priority:** [high/medium/low based on importance to story]
**Status:** [pending/verified/false/unverifiable]
### Claim 2
[same structure]
```
### Prioritizing claims
| Priority | Criteria |
|----------|----------|
| **High** | Central to the story's thesis, easily checkable, high consequence if wrong |
| **Medium** | Supporting detail, takes more effort to verify |
| **Low** | Peripheral detail, commonly accepted, minimal consequence |
Check high-priority claims first. Check all claims if time allows.
## Step 2: Research the claim
### Primary sources first
| Claim type | Primary sources |
|------------|-----------------|
| Statistics | Original study, government data, survey methodology |
| Quotes | Audio/video recording, transcript, direct confirmation |
| Historical | Contemporary news accounts, official records |
| Scientific | Peer-reviewed research, expert consensus |
| Legal | Court documents, official filings |
| Financial | SEC filings, audited statements |
### Secondary source evaluation
If you must use secondary sources:
- How close are they to the original?
- Do they cite their sources?
- Do multiple independent sources confirm?
- Is there any contradicting coverage?
### Research documentation template
```markdown
## Research for Claim: [brief description]
### Primary sources checked
| Source | What it says | Confirms/Contradicts |
|--------|--------------|---------------------|
| [source] | [finding] | [confirms/contradicts/partial] |
### Secondary sources checked
| Source | What it says | Reliability |
|--------|--------------|-------------|
| [source] | [finding] | [high/medium/low] |
### Gaps in evidence
- [What you couldn't find]
- [What you still need]
```
## Step 3: Evidence gathering
### Types of evidence
| Evidence type | Strength | Notes |
|---------------|----------|-------|
| Official documents | Strong | Court records, government reports, filings |
| Primary data | Strong | Original datasets, your own analysis |
| Expert consensus | Strong | Multiple independent experts agree |
| On-record sources | Medium | Named source with direct knowledge |
| Contemporary accounts | Medium | News coverage from the time |
| Off-record sources | Weak | Use to guide reporting, not as evidence |
| Social media posts | Weak | Can be deleted, context matters |
### Evidence checklist
```markdown
## Evidence for: [claim]
### Documentary evidence
- [ ] Government records
- [ ] Court documents
- [ ] Corporate filings
- [ ] Published research
- [ ] Official statements/press releases
### Human sources
- [ ] Direct witnesses
- [ ] Subject matter experts
- [ ] Involved parties (on record)
- [ ] Involved parties (for response)
### Data verification
- [ ] Original dataset obtained
- [ ] Methodology reviewed
- [ ] Calculations independently verified
- [ ] Sample size adequate
### Contradicting evidence
- [ ] Searched for conflicting sources
- [ ] Contradictions documented
- [ ] Discrepancies explained
```
## Step 4: Contact sources
### Right of response
**Always contact:**
- People/organizations being fact-checked
- Give specific claims you're checking
- Give reasonable deadline (24-48 hours minimum)
- Document their response (or non-response)
### Source contact template
```markdown
Subject: Request for comment - [Publication] fact-check
Dear [Name],
I'm a [title] at [publication] working on a fact-check of [context].
Specifically, I'm examining this claim:
"[Exact claim being checked]"
I want to give you the opportunity to provide any evidence supporting this claim, clarify the context, or offer any corrections.
My deadline is [date/time]. Please let me know if you need more time.
[Your name]
[Contact info]
```
### Document responses
```markdown
## Source response log
### [Source name]
**Contacted:** [date/time, method]
**Deadline given:** [date/time]
**Response received:** [date/time] / No response
**Summary:** [what they said]
**Evidence provided:** [any documentation]
**Direct quote for publication:** "[quote]"
```
## Step 5: Rating the claim
### Standard rating scales
**Binary (for internal fact-checking):**
- Verified
- False
- Unverifiable
**Graduated (for fact-check articles):**
| Rating | Criteria |
|--------|----------|
| **True** | Accurate and complete, nothing significant omitted |
| **Mostly true** | Accurate but needs context or minor clarification |
| **Half true** | Partially accurate but leaves out critical context |
| **Mostly false** | Contains some truth but overall misleading |
| **False** | Not accurate; contradicted by evidence |
| **Pants on fire** | Not accurate AND ridiculous (use sparingly) |
### Rating decision template
```markdown
## Rating decision: [claim]
**Claim:** [exact statement]
**Speaker:** [who said it]
**Our rating:** [rating]
### Evidence supporting the claim
- [Evidence 1]
- [Evidence 2]
### Evidence contradicting the claim
- [Evidence 1]
- [Evidence 2]
### Key context missing from the claim
- [Context 1]
- [Context 2]
### Source response
[What they said when contacted]
### Reasoning
[Explain why this rating, not another]
### Confidence level
[High/Medium/Low and why]
```
## Step 6: Documentation
### The fact-check file
For every claim verified, maintain:
```markdown
## Fact-check record
**Claim:** [exact statement]
**Source:** [who said it, where, when]
**Checked by:** [your name]
**Date checked:** [date]
### Verification
**Rating:** [rating]
**Primary evidence:** [list with links/locations]
**Supporting evidence:** [list]
**Contradicting evidence:** [if any]
### Sources contacted
- [Name]: [response summary]
- [Name]: [no response as of date]
### Notes
[Any additional context, caveats, future considerations]
### Files
- [List of saved documents, screenshots, etc.]
```
### Archiving evidence
- Save screenshots with timestamps (URLs can change)
- Archive web pages (Wayback Machine, Archive.today)
- Download documents (don't just link)
- Keep original files separate from your analysis
## Step 7: Corrections
### When to correct
| Situation | Action |
|-----------|--------|
| Factual error | Correct immediately, note correction |
| Missing context | Add context, may not need formal correction |
| Updated information | Update, note "Updated: [date]" |
| Source disputes characterization | Evaluate claim, correct if warranted |
### Correction template
```markdown
**Correction [date]:** An earlier version of this article stated [incorrect claim].
In fact, [correct information]. We regret the error.
```
### Correction log
```markdown
## Correction record
**Article:** [title/URL]
**Original publication:** [date]
**Error discovered:** [date]
**Error type:** [factual/context/attribution/etc.]
**Original text:**
[what was published]
**Corrected text:*Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.