agentleFS
d-wweid-wwei/openclaw-financial-services/skills/fsi-er-thesis-tracker/SKILL.md

fsi-er-thesis-tracker

Skill16 starsChanged 9 months agoApache-2.0View on GitHub

Maintain and update investment theses for portfolio positions and watchlist names. Track key data points, catalysts, and thesis milestones over time. Use when updating a thesis with new information, reviewing position rationale, or checking if a thesis is still intact. Triggers on "update thesis for [company]", "is my thesis still intact", "thesis check", "add data point to [company]", or "review my positions".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

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

    If creating a new thesis:

    line 15
  2. Distinctive:

    If updating an existing thesis, ask the user for the new data point or development.

    line 25
  3. Distinctive:

    Date: When this happened

    line 31
  4. Distinctive:

    Action: No change / Increase position / Trim / Exit

    line 34
  5. Distinctive:

    If the user manages multiple positions, offer to do a full portfolio thesis review

    line 69

≈ “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.

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

Thesis Tracker

Workflow

Step 1: Define or Load Thesis

If creating a new thesis:

  • Company: Name and ticker
  • Position: Long or Short
  • Thesis statement: 1-2 sentence core thesis (e.g., "Long ACME — margin expansion from pricing power + operating leverage as mix shifts to software")
  • Key pillars: 3-5 supporting arguments
  • Key risks: 3-5 risks that would invalidate the thesis
  • Catalysts: Upcoming events that could prove/disprove the thesis (earnings, product launches, regulatory decisions)
  • Target price / valuation: What's it worth if the thesis plays out
  • Stop-loss trigger: What would make you exit

If updating an existing thesis, ask the user for the new data point or development.

Step 2: Update Log

For each new data point or development:

  • Date: When this happened
  • Data point: What changed (earnings beat, management departure, competitor move, etc.)
  • Thesis impact: Does this strengthen, weaken, or neutralize a specific pillar?
  • Action: No change / Increase position / Trim / Exit
  • Updated conviction: High / Medium / Low

Step 3: Thesis Scorecard

Maintain a running scorecard:

PillarOriginal ExpectationCurrent StatusTrend
Revenue growth >20%On trackQ3 was 22%Stable
Margin expansionBehindMargins flat YoYConcerning
New product launchPendingDelayed to Q2Watch

Step 4: Catalyst Calendar

Track upcoming catalysts:

DateEventExpected ImpactNotes

Step 5: Output

Thesis summary suitable for:

  • Morning meeting discussion
  • Portfolio review
  • Risk committee presentation

Format: Concise markdown or Word doc with the scorecard, recent updates, and current conviction level.

Important Notes

  • A thesis should be falsifiable — if nothing could disprove it, it's not a thesis
  • Track disconfirming evidence as rigorously as confirming evidence
  • Review theses at least quarterly, even when nothing dramatic has happened
  • If the user manages multiple positions, offer to do a full portfolio thesis review
  • Store thesis data in a structured format so it can be referenced across sessions

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.