hypothesis-tracking
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
Use this skill to manage durable research memory for a company. Hypotheses are a working memory layer, not final truth.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- blisspixel/primrword for word, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 1
- blisspixel/primr★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- primr-zeroSkill
- primrSkill
- primr-zeroSkill
- company-researchSkill
- qa-iterationSkill
- scrape-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Use this skill to manage durable research memory for a company.
- Distinctive: line 23
Update confidence only when new evidence exists.
- Distinctive: line 24
Keep evidence strings short, factual, and source-oriented.
- Distinctive: line 30
Prefer updating an existing hypothesis over creating duplicates.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hypothesis Tracking
Purpose
Use this skill to manage durable research memory for a company. Hypotheses are a working memory layer, not final truth.
Workflow
- Retrieve hypotheses before starting duplicate research.
- Present confidence clearly: untested, validated, invalidated, or confirmed.
- Update confidence only when new evidence exists.
- Keep evidence strings short, factual, and source-oriented.
Operating Rules
- Distinguish known facts from open hypotheses.
- Preserve the evidence trail when confidence changes.
- Prefer updating an existing hypothesis over creating duplicates.
- Expired or weak hypotheses should be re-validated before being presented as current.
Example
get_hypotheses(company="ExampleCo", topic="technology")
save_hypothesis(company="ExampleCo", hypothesis_id="h_001", confidence="validated", evidence="CTO interview confirms AWS usage")
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

