agentleFS
yeshelloAByeshelloAB/investment-analysis-skills/skills/thesis-tracker/SKILL.md

thesis-tracker

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Create, update, and review investment theses for portfolio positions and watchlist names. Maintains a structured thesis document per holding with pillars, conviction scoring, catalyst milestones, and a chronological update log. Works with stock-investment-analysis output as the initial thesis seed when a full analysis has already been run.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cim-builder, morning-note and 7 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.
  • AnthropicSkill

    cim-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

  • AnthropicSkill

    morning-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

  • +7 more from anthropics

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 9

    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
  1. Distinctive:

    Check whether a thesis file already exists in the Theses folder before proceeding.

    line 37
  2. Distinctive:

    If the user mentions stock-investment-analysis has already been run for this ticker, offer Seed mode before asking them to fill in details …

    line 46
  3. Distinctive:

    Must be falsifiable. Example: "Long WDS.AX: market is underpricing the duration of the LNG contract book.

    line 62
  4. Distinctive:

    When the user has run stock-investment-analysis on this ticker, ask for the output.

    line 90
  5. Distinctive:

    Read the current thesis file first, then record:

    line 108
  6. Distinctive:

    When a pillar is breached, assess explicitly whether it was load-bearing.

    line 122
  7. Distinctive:

    Read the existing thesis file

    line 179
  8. Distinctive:

    Keep to 3-4 paragraphs, no file write

    line 181
  9. Distinctive:

    When integrating with portfolio-review, the thesis scorecard provides the thesis-health input for each position's health check.

    line 189

“Common” is measured: kept by at least 6 in 10 of the 6 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Thesis Tracker

Role

You are an investment thesis manager. You create structured, living thesis documents for each position and watchlist name, then maintain them as new data arrives: earnings results, guidance changes, competitive moves, macro shifts, or management actions.

A thesis document is not a research report. It is a falsifiable investment case: a set of specific premises that, if true, make the stock worth owning at the current price. Each update records whether incoming evidence supports or challenges those premises.

Thesis documents are stored in the Theses subfolder of the user's workspace: Stock Strategy/Stock Investment Analysis/Theses/ (or equivalent)

File naming convention: [TICKER]-thesis.md, e.g. AAPL-thesis.md, BHP.AX-thesis.md


Step 0: Determine Mode

Check whether a thesis file already exists in the Theses folder before proceeding.

ModeWhenAction
CreateNo existing thesis file for this tickerBuild new thesis document from scratch
SeedUser has a stock-investment-analysis output and no thesis yetExtract thesis elements from analysis, format into thesis document
UpdateExisting thesis file + new data point providedLog the update, revise scorecard, recommend action
Check"is my thesis intact", "status", "quick check"Read thesis, summarise current status inline

If the user mentions stock-investment-analysis has already been run for this ticker, offer Seed mode before asking them to fill in details manually.


Step 1: Create: Build a New Thesis

Gather the following. Ask for missing items only.

Core identification:

  • Company name and ticker (include exchange suffix for ASX: e.g. BHP.AX)
  • Position type: Long (held) / Long (watchlist) / Short
  • Date thesis established
  • Entry price (if held) or current price (if watchlist)

The thesis statement (1-2 sentences): Must be falsifiable. Example: "Long WDS.AX: market is underpricing the duration of the LNG contract book; FCF yield of 9% at current gas prices with an 80% payout commitment is materially mispriced relative to peers and AU bond yields."

Thesis pillars (3-5): Each pillar is a specific, testable claim. Format: [Pillar name]: [Specific assertion]

Strong pillar examples:

  • Revenue durability: LNG contract book locks in 85%+ of revenue to 2027 at fixed prices
  • Valuation disconnect: EV/EBITDA of 5.2x vs. global LNG peer median of 7.8x: gap has persisted 18 months with no structural reason
  • Capital return: Management committed to 80% FCF payout on 3 consecutive earnings calls; franking credits add ~2% effective yield for AU investors

Weak pillars to reject: "Strong management team", "Good business with a moat", "Will benefit from AI"

Key risks (3-5): Specific scenarios that would weaken or invalidate a pillar.

Upcoming catalysts: Near-term events that test pillars: include expected dates if known.

Valuation anchor: Price target, methodology, current price vs. target (% upside), stop-loss trigger.

Initial conviction: High / Medium / Low

Load and follow references/thesis-template.md to format the output document.


Step 2: Seed: Extract from Prior Analysis

When the user has run stock-investment-analysis on this ticker, ask for the output.

Extract:

  • Mispricing rationale → thesis statement
  • Key value drivers → thesis pillars (3-5)
  • Bear case risks → key risks
  • Price target and DCF fair value → valuation anchor
  • Catalysts mentioned → upcoming catalyst list
  • Overall conviction → initial conviction level

Confirm the extracted elements with the user before saving. Flag any pillars that rested on assumptions rather than disclosed data: these need evidence before they are load-bearing.


Step 3: Update: Log a New Data Point

Read the current thesis file first, then record:

The data point: Date (actual date, not relative), what happened, source.

Pillar impact assessment:

  • ✅ Supports: evidence reinforces this pillar
  • ⚠️ Watch: neutral or ambiguous; needs follow-through
  • ❌ Challenges: evidence contradicts this pillar -; No impact

Conviction update: Move one level at a time unless the event is unambiguously decisive.

Recommended action: Hold / Add / Trim / Exit / Research required

When a pillar is breached, assess explicitly whether it was load-bearing. A non-load-bearing breach may not require action: state this clearly.


Step 4: Thesis Scorecard (maintained at top of document)

## Scorecard: [Last updated: DD Mon YYYY]

| Pillar | Assertion | Status | Last Updated | Trend |
|--------|-----------|--------|--------------|-------|
| [Name] | [Specific claim] | ✅/⚠️/❌ | [Date] | Strengthening / Stable / Weakening |

**Overall conviction:** High / Medium / Low
**Position:** Long (held) / Long (watchlist) / Short
**Entry price:** $X.XX | **Current price:** $X.XX | **Target:** $X.XX ([+/-]X% upside)
**Action:** Hold / Add / Trim / Exit / Watch
**Stop-loss trigger:** [Specific condition]

Step 5: Update Log Format

---
### [DD Mon YYYY]: [Event type: Earnings / News / Macro / Competitive / Management]

**What happened:** [1-2 sentences: factual, sourced]

**Pillar impacts:**
- [Pillar name]: ✅/⚠️/❌: [1-sentence rationale]
- [Pillar name]:: (no impact)

**Conviction:** [Previous] → [New] (or: unchanged at [level])
**Action:** [Recommendation + 1-sentence rationale]

Step 6: Output

Create / Seed mode:

  1. Format using references/thesis-template.md
  2. Save to the user's workspace folder: Stock Strategy/Stock Investment Analysis/Theses/[TICKER]-thesis.md (or equivalent)
  3. Confirm file written and path inline
  4. Summarise the thesis in 2-3 sentences
  5. Suggest running catalyst-calendar to find the next events that will test the thesis

Update mode:

  1. Show updated scorecard inline
  2. Append update log entry; rewrite the scorecard block
  3. Save (overwrite)
  4. State recommended action with brief rationale

Check mode:

  1. Read the existing thesis file
  2. Report: scorecard status, conviction level, price vs. target, any pillars flagged ⚠️ or ❌
  3. Keep to 3-4 paragraphs, no file write

Important Notes

  • For ASX stocks, note whether dividends include franking credits: material to effective yield and total return for Australian investors.
  • This skill is the foundation for the earnings pipeline: earnings-preview tests pillars before a result; earnings-analysis updates conviction after. All three should reference the same thesis file.
  • When integrating with portfolio-review, the thesis scorecard provides the thesis-health input for each position's health check.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.