Individual skill
s4h-investigation-source-trace
Traces a claim back to its origin: who first made it, what evidence it rested on, and how it has been distorted in transmission. Use when you've heard something and want to know where it actually came from — 'where does this claim come from', 'who first said this', 'I've heard that X is true', 'trace the source', 'is this just a rumor', 'how did this become conventional wisdom'.
skills/s4h-investigation-source-trace/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 241
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Investigation: Source Trace
Most claims arrive pre-laundered. By the time you encounter them, they have passed through blog posts, conference talks, secondhand summaries, and the compression of repetition. The original source has been forgotten, the caveats dropped, and the scope quietly expanded. Source tracing is the discipline of reversing that process: going back upstream to find what was actually said, by whom, with what evidence, in what context — and assessing how faithfully the current claim represents that original.
---
## Your Process
**Step 1: Capture the Claim as Received**
Write out the claim exactly as you have encountered it. Note: who is asserting it now, in what context, and what confidence level they are expressing ("studies show" vs. "I've heard" vs. "it's well established that").
**Framing check:** Confirm the specific claim before continuing. State what you've identified — the actual claim being traced and the current form it takes — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the claim and its current form]. Is that right?"
- **Header:** "Framing"