claim-investigation
Systematically investigate social media claims and viral content. Use when fact-checking complex claims, when decomposing multi-part assertions, or when investigating narratives that mix facts with interpretation.
What this skill does
# Claim Investigation: Systematic Fact-Checking Skill
You help systematically investigate claims from social media and other sources, separating verifiable facts from narrative interpretation and identifying what can and cannot be confirmed.
## Core Principle
Complex claims typically combine verifiable facts with unverifiable interpretations. Effective investigation decomposes claims into atomic components, verifies each independently, and clearly distinguishes between confirmed facts and narrative framing.
## Phase 1: Claim Decomposition
### 1.1 Extract Atomic Claims
Break the statement into individual verifiable claims. Each should be:
- A single factual assertion
- Independently verifiable
- Free of narrative interpretation
**Example Decomposition**:
Original: "The House Leader refusing to seat the newly-elected AZ-07 special election winner because she'd vote to release the Epstein files"
Atomic claims:
1. There is a House Leader (entity exists)
2. There was an AZ-07 special election (event occurred)
3. Someone won that election (result exists)
4. The winner has not been seated (current state)
5. A refusal action occurred (specific action claim)
6. Causal relationship with Epstein files (causation claim)
### 1.2 Classify Each Component
| Type | Description | Verifiability |
|------|-------------|---------------|
| ENTITY | Person, organization, place | Usually verifiable |
| EVENT | Something that allegedly happened | Often verifiable |
| STATE | Current condition or status | Usually verifiable |
| PROCESS | Official procedure or mechanism | Verifiable |
| CAUSATION | Claimed reason or motivation | Rarely verifiable |
| NARRATIVE | Interpretive framing | Not directly verifiable |
### 1.3 Identify Missing Information
Note what's conspicuously absent:
- Unnamed entities ("the winner" instead of a name)
- Unspecified dates
- Missing procedural context
- Absent opposing perspectives
## Phase 2: Entity Resolution
### 2.1 Resolve Vague References
Convert vague references to specific, searchable terms:
- "House Leader" → Current House Speaker/Majority Leader name
- "newly-elected winner" → Candidate names from election results
- "Epstein files" → Specific documents/investigations
### 2.2 Establish Timeline
For each event:
- When did it allegedly occur?
- What is normal timeline for this type of event?
- Are there procedural deadlines involved?
### 2.3 Identify Key Actors
- Primary actors (those taking alleged actions)
- Secondary actors (those affected)
- Official bodies with relevant authority
- Potential sources of verification
## Phase 3: Systematic Verification
### 3.1 Verify Foundational Facts First
Start with most basic, verifiable claims:
1. Did the event occur?
2. Do the entities exist?
3. Are basic facts correct?
**Search Strategy**:
- Official sources first (.gov, electoral bodies)
- Cross-reference multiple news sources
- Look for primary documents
### 3.2 Investigate Procedural Context
For any claimed action/inaction:
1. What is normal procedure?
2. What are requirements?
3. What is typical timeline?
4. What are legitimate reasons for delays?
### 3.3 Examine Causation Claims
For any "because" or causal claim:
**Direct Evidence**:
- Quoted statements from alleged actor
- Official statements or press releases
- Video/audio of relevant statements
**Indirect Evidence**:
- Other explanations for observed facts
- Standard reasons for similar situations
- Procedural explanations
**Context**:
- Previous positions by involved parties
- Historical precedents
- Timeline compatibility
## Phase 4: Source Evaluation
### 4.1 Source Priority Order
1. Official government records/databases
2. Direct statements from involved parties
3. Court documents or legal filings
4. Contemporary news reports (multiple outlets)
5. Analysis or opinion pieces (noted as such)
### 4.2 Credibility Markers
For each source, note:
- Type (official, news, advocacy, social media)
- Date relative to events
- Whether claims are attributed
- Presence of supporting documentation
- Corrections or updates issued
### 4.3 Bias Indicators
Document without dismissing:
- Source's typical political alignment
- Stakeholder relationships
- Pattern of coverage
- Language choices (neutral vs charged)
## Phase 5: Narrative Pattern Recognition
### 5.1 Identify Narrative Constructions
Patterns indicating narrative rather than fact:
- Causal chains without evidence ("X because Y because Z")
- Mind-reading claims ("thinks that," "wants to")
- Selective fact inclusion
- Temporal conflation (mixing time periods)
- False dichotomies
### 5.2 Find Counter-Narratives
For each narrative:
- What facts support it?
- What facts complicate it?
- What alternative narratives explain same facts?
- What facts are excluded?
### 5.3 Missing Context
What would change interpretation:
- Standard procedures being followed
- Similar historical cases
- Full quotes vs partial quotes
- Events immediately before/after
## Phase 6: Synthesis and Reporting
### 6.1 Report Structure
```
VERIFIED FACTS:
- [Fact] (Source: [citation])
DISPUTED/UNCLEAR:
- [Claim]:
- Supporting: [source]
- Contradicting: [source]
- Unable to verify: [what's missing]
CONTEXT NEEDED:
- [Procedural context]
- [Historical precedent]
- [Timeline considerations]
NARRATIVE ELEMENTS:
- [Claim]
- Facts that support: [list]
- Facts that complicate: [list]
- Alternative explanations: [list]
```
### 6.2 Confidence Levels
| Level | Meaning |
|-------|---------|
| **Certain** | Multiple primary sources confirm |
| **Probable** | Multiple credible sources align, no contradictions |
| **Possible** | Some evidence supports, gaps remain |
| **Unclear** | Contradictory evidence or insufficient info |
| **False** | Contradicted by authoritative sources |
## Phase 7: Meta-Analysis
### 7.1 Information Gaps
Document what couldn't be determined:
- Information that should exist but wasn't found
- Questions that remain unanswered
- Time constraints on verification
### 7.2 Manipulation Indicators
Patterns suggesting intentional misrepresentation:
- Key facts consistently omitted
- Misquoted or out-of-context statements
- Conflation of different events/people
- Old events presented as new
### 7.3 Further Investigation
If initial investigation reveals deeper issues:
- What additional tools/access would help?
- What questions should be asked of officials?
- What documents should be requested?
## Search Query Construction
- Start broad, then narrow
- Use multiple phrasings for same concept
- Include date ranges when relevant
- Search for both supporting and contradicting evidence
- Use exact phrases for quotes, broad terms for concepts
## Output Principles
1. Lead with verified facts
2. Clearly separate facts from analysis
3. Include all relevant context
4. Present multiple valid interpretations where applicable
5. Never assert causation without evidence
6. Acknowledge investigation limitations
## Output Persistence
### Output Discovery
1. Check for `context/output-config.md` in the project
2. If found, look for this skill's entry
3. If not found, ask user: "Where should I save investigation reports?"
4. Suggest: `research/investigations/` or `explorations/research/`
### Primary Output
- **Decomposed claims** - Atomic components with classifications
- **Verification results** - Confidence levels per component
- **Context documentation** - Procedural and historical context
- **Synthesis report** - Using standard report structure
### File Naming
Pattern: `{topic}-investigation-{date}.md`
## Verification (Oracle)
### What This Skill Can Verify
- **Decomposition complete** - All atomic claims identified? (High confidence)
- **Entity resolution** - Vague references resolved? (High confidence)
- **Source evaluation** - Credibility markers documented? (High confidence)
### What Requires Human Judgment
- **Source reliability** - Contextual trust assessment
- **Narrative interpretation** - Which framing is most accurate?
- **MaRelated 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.