jimweller/fact-check
configs/claude-code/skills/fact-check/SKILL.md
Use when a factual claim lacks evidence, when called out for fabricating facts, or when a statement needs verification before being presented as true. Takes a claim as argument.
testing
Updated Apr 29, 2026
$ install --global
skillsauthnpx skillsauth add jimweller/dotfiles fact-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 11:46 AM40.0s1 file scanned
SKILL.md
- name:
- fact-check
- description:
- Use when a factual claim lacks evidence, when called out for fabricating facts, or when a statement needs verification before being presented as true. Takes a claim as argument.
<!-- markdownlint-disable-file MD041 -->
STARTER_CHARACTER = 🔬
Fact-Check
A claim was made without evidence. This skill forces verification before the claim can stand.
Input
The argument to this skill is the claim to verify. If no argument is provided, scan the last CLANKER response for all factual claims (statements presented as true, not hedged as speculation). Run the procedure on each one.
Procedure
- State the claim exactly. Quote it. No paraphrasing.
- Classify the claim.
- Empirically testable now: a command, file read, or API call can confirm or refute it in this turn. Go to step 3.
- Researchable: documentation, source code, or web search can provide evidence. Go to step 4.
- Unverifiable: no available tool or source can confirm it. Go to step 5.
- Test it. Run the command or read the file. Report the raw output. Compare to the claim. Verdict: confirmed, refuted, or partially true (state which parts hold and which fail).
- Research it. Use c7, g MCP servers, WebSearch, or Read to find authoritative sources. Cite the source (URL, file path, or command output). Verdict: confirmed, refuted, partially true, or insufficient evidence.
- Declare it unverifiable. State why no available tool can test it. Retract the claim or restate it as speculation with explicit qualification.
Output format
CLAIM: "<exact quote>"
TYPE: empirical | researchable | unverifiable
EVIDENCE: <raw output, citation, or "none available">
VERDICT: confirmed | refuted | partially true | unverifiable
CORRECTION: <if refuted or partially true, state the accurate version>
Rules
- Never skip straight to a verdict. Show the evidence first.
- Never confirm a claim using the same reasoning that produced it. Independent evidence only.
- If the claim came from a prior observation or memory entry, that is not independent evidence. Observations record what was said, not what is true.
- If the verdict is "refuted," retract the original claim in plain language after the output block.
- A fact conceded for comfort is a lie by omission. Do not soften a refutation.
Related Skills
jimweller/transcript-search
testing
VerifiedTrustedCommunity
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
1SKILL.mdUpdated Apr 22, 2026
jimweller/prd-review
data-ai
VerifiedTrustedCommunity
Review a PRD for defects via Claude opus subagent.
SKILL.mdUpdated Apr 29, 2026
jimweller/md-syntax
development
VerifiedTrustedCommunity
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
SKILL.mdUpdated Apr 29, 2026
jimweller/configs/claude-code/skills/md-style
development
VerifiedTrustedCommunity
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan
SKILL.mdUpdated Apr 29, 2026