thesis-tracker
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".
What this skill does
# 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: | Pillar | Original Expectation | Current Status | Trend | |--------|---------------------|----------------|-------| | Revenue growth >20% | On track | Q3 was 22% | Stable | | Margin expansion | Behind | Margins flat YoY | Concerning | | New product launch | Pending | Delayed to Q2 | Watch | ### Step 4: Catalyst Calendar Track upcoming catalysts: | Date | Event | Expected Impact | Notes | |------|-------|-----------------|-------| | | | | | ### 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
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.