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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclaim-investigationExecute the skills CLI command in your project's root directory to begin installation:
Fetches claim-investigation from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate claim-investigation. Access via /claim-investigation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jwynia/agent-skills
jwynia/agent-skills
jwynia/agent-skills
jwynia/agent-skills
jwynia/agent-skills
davila7/claude-code-templates
I recommend claim-investigation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
claim-investigation reduced setup friction for our internal harness; good balance of opinion and flexibility.
claim-investigation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for claim-investigation matched our evaluation — installs cleanly and behaves as described in the markdown.
claim-investigation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added claim-investigation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: claim-investigation is focused, and the summary matches what you get after install.
claim-investigation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in claim-investigation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
claim-investigation has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 55