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.
npx skills add https://github.com/jwynia/agent-skills --skill claim-investigation
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.
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.
Break the statement into individual verifiable claims. Each should be:
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:
| 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 |
Note what's conspicuously absent:
Convert vague references to specific, searchable terms:
For each event:
Start with most basic, verifiable claims:
Search Strategy:
For any claimed action/inaction:
For any "because" or causal claim:
Direct Evidence:
Indirect Evidence:
Context:
For each source, note:
Document without dismissing:
Patterns indicating narrative rather than fact:
For each narrative:
What would change interpretation:
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]
| 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 |
Document what couldn't be determined:
Patterns suggesting intentional misrepresentation:
If initial investigation reveals deeper issues:
context/output-config.md in the projectresearch/investigations/ or explorations/research/Pattern: {topic}-investigation-{date}.md
context/output-config.md{topic}-investigation-{date}.mdTrigger phrases: "full investigation", "trace all sources", "analyze the narrative"
| Task | Agent Type | When to Spawn |
|------|------------|---------------|
| Source research | general-purpose | When tracing claim origins |
| Timeline construction | general-purpose | When mapping event sequences |
Pattern: Finding one source that matches the claim and declaring it verified.
Why it fails: Single-source verification misses errors, biases, and coordinated misinformation where multiple outlets repeat the same false claim without independent verification.
Fix: Require at least 2-3 independent sources. Trace claims back to primary sources. Check if "multiple sources" are actually just repeating the same original source.
Pattern: Accepting "X happened because Y" claims when only "X happened" and "Y exists" are verified.
Why it fails: Correlation proves co-occurrence, not causation. Human pattern-matching fills in causal links that may not exist. Political narratives especially exploit this gap.
Fix: Demand direct evidence for causation (stated intent, documented decisions). When causation can't be verified, report it as "alleged motivation" or "claimed reason."
Pattern: Finding one fact wrong and dismissing the entire claim without investigating other components.
Why it fails: Complex claims often mix true and false elements. Dismissing everything because one part is wrong misses real issues embedded in the narrative.
Fix: Decompose fully, verify each component independently. Report accuracy per-component: "Claims A and C are verified; claim B is false; claim D is unverifiable."
Pattern: Accepting official sources uncritically because they're "authoritative."
Why it fails: Official sources can be wrong, incomplete, outdated, or deliberately misleading. Authority reduces probability of error but doesn't eliminate it.
Fix: Cross-reference official sources with other evidence. Note when official sources have incentives to misrepresent. Distinguish between "official position" and "verified fact."
Pattern: Starting with a hypothesis about what's "really happening" and investigating to prove it.
Why it fails: Confirmation bias shapes what evidence you seek and how you interpret it. You'll find "evidence" for any narrative if you look hard enough.
Fix: Start with the specific claims made. Investigate each on its own terms. Actively seek disconfirming evidence. Document alternative explanations that fit the same facts.
| Skill | What it provides |
|-------|------------------|
| research | Initial source discovery and query expansion |
| media-meta-analysis | Understanding of source biases and media patterns |
| Skill | What this provides |
|-------|-------------|
| fact-check | Verified facts for post-generation checking |
| sensitivity-check | Context for evaluating representation claims |
| Skill | Relationship |
|-------|--------------|
| research | Use research for broad information gathering, claim-investigation for specific claim verification |
| fact-check | Use claim-investigation for external claims, fact-check for AI-generated content verification |
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
Statistical analysis toolkit. Hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, APA reporting, for academic research.
Automated hypothesis generation and testing using large language models. Use this skill when generating scientific hypotheses from datasets, combining literature insights with empirical data, testing hypotheses against observational data, or conducting systematic hypothesis exploration for research discovery in domains like deception detection, AI content detection, mental health analysis, or other empirical research tasks.
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation.
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required sample sizes, or write up results - even if they never name a specific test. Covers t-tests, ANOVA, chi-square, correlation, regression, non-parametric and Bayesian methods. For low-level model APIs, see the statsmodels and pymc skills.
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
> Jurisdiction-aware wage/hour and employment Q&A — classification, overtime, meal/rest breaks, leave, final pay — answered for the specific state/country with the controlling rule researched and cited rather than stated from memory. Use when the user asks any employment law question, or says "what's the rule in [state]", "is this exempt", "do we have to pay overtime for", or "can we classify this as".
Take jwynia/claim-investigation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.