thesis-tracker
Skill0 starsChanged 11 days agoApache-2.0View on GitHub
Write, update and test an investment thesis so it can be proven wrong. Use when opening a thesis on a company or asset, when new information arrives, or when asked whether a thesis still holds.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Shubhamkumartrichy/claude-trading-skills-indiatheir own version, first seen Nov 15, 2026
- JasmineNy/codex-skills-portfoliotheir own version, first seen Oct 20, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
- anthropics/financial-services-pluginstheir own version, first seen Oct 8, 2026
- anthropics/financial-servicestheir own version, first seen Jul 22, 2026
Used with
Projects with it also use cim-builder, morning-note and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillcim-builder
Structure and draft a Confidential Information Memorandum for sell-side M&A processes. Organizes company information into a professional, investor-ready document with consistent formatting and narrative flow. Use when preparing sell-side materials, drafting a CIM, or organizing company data for a sale process. Triggers on "CIM", "confidential information memorandum", "offering memorandum", "info memo", "draft CIM", or "sell-side materials".
Also in 3 projects that use this
AnthropicSkillmorning-note
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
Also in 3 projects that use this
- +8 more from anthropics
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- openai/plugins★ 7.8ksame name
- Shubhamkumartrichy/claude-trading-skills-india★ 64same name
- yeshelloAB/investment-analysis-skills★ 1same name
- edu6565/claude-skills★ 0same name
- JasmineNy/codex-skills-portfolio★ 0same name
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 repository3 other files it gives its agents.
- calibration-logSkill
- opportunity-screenSkill
- source-checkSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
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 28
intact: no kill criterion crossed, no pillar contradicted by a source.
- Distinctive: line 35
When new information arrives, log the date, what changed, the source, which pillar or criterion it touches, and whether it strengthens, …
- Distinctive: line 62
Never recommend buying, selling, sizing or holding.
- Distinctive: line 63
Every number carries a source and an as-of date.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Thesis tracker
A thesis is a claim you can lose. This skill keeps one honest: written down with its evidence, the conditions that would end it, and a record of what has happened since.
Workflow
1. Write the claim
One sentence, specific enough to be wrong. Name the asset, the mechanism and the horizon. "Company X earns more per share in two years because pricing outruns costs" is a thesis. "X is a great company" is not.
2. Give it pillars
Three to five supporting arguments. For each: the evidence, the source, the date it was true, and whether it is a fact, an inference or an opinion.
3. Write the kill criteria before anything else
Measurable conditions that would end the thesis: a metric, a threshold, a date. For example, "gross margin below 38% for two consecutive quarters". Write them while calm, before you have a position or a stake in being right. If you cannot state one, the thesis is not ready.
4. Write the case against
The strongest argument a careful skeptic would make, with evidence. Add the base rate for claims of this kind if you know it.
5. List what is coming
Dated events that could confirm or break the thesis: earnings, filings, regulatory decisions, token unlocks, debt maturities.
6. Set the status by rule
- intact: no kill criterion crossed, no pillar contradicted by a source.
- watch: a criterion is within about 5% of its line, a pillar is contradicted, or a criterion cannot be checked because its data is stale or missing.
- broken: a kill criterion has been crossed.
The status follows the criteria, not your mood. When a thesis is broken, say so and leave the decision to its owner. Do not argue it away.
7. Update with the disconfirming evidence first
When new information arrives, log the date, what changed, the source, which pillar or criterion it touches, and whether it strengthens, weakens or leaves the thesis alone. Give evidence against the thesis the same care as evidence for it.
Output
# Thesis: <asset>, <horizon>
**Claim:** <one sentence>
**Status:** intact | watch | broken (as of <date>)
## Pillars
| # | Pillar | Evidence | Source | As of | Fact / inference / opinion |
## Kill criteria
| # | Metric | Threshold | Check by | Latest value | Status |
## Case against
<the skeptic's argument, with sources>
## Coming up
| Date | Event | Could confirm / could break |
## Log
| Date | What changed | Source | Touches | Effect |Rules
- Never recommend buying, selling, sizing or holding. Report the state of the thesis and let the owner decide.
- Every number carries a source and an as-of date. No source, no number.
- Label each statement as fact, inference or opinion.
- An unchecked criterion is "cannot be checked", never "fine".
- Rates move in percentage points. Never report a percent change of a percentage.
- Review every thesis at least quarterly, even when nothing dramatic has happened.
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.

