Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Thesis Development

ASecurity

Turns a vague sector interest into a written investment thesis with a falsifiable core claim, must-be-true conditions and kill criteria set in advance -- when you need a thesis diligence can disprove.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill thesis-development --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Thesis Development?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Thesis Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-thesis-development/badge)](https://www.skillsdirectory.com/skills/andreworia-thesis-development)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: Thesis Development
description: Turns a vague sector interest into a written investment thesis with a falsifiable core claim, must-be-true conditions and kill criteria set in advance -- when you need a thesis diligence can disprove.
---

# Thesis Development

## When to use

Use this skill before a market map exists and long before a target is named, when the partnership has an interest ("we like industrial services") but no written claim anyone can argue with. Use it also when a thesis has drifted into defending consecutive passes.

## What it does

Produces a short thesis document: sub-sector boundary, the core claim in falsifiable form, where in the EBITDA bridge the return is created, the why-now catalyst, must-be-true conditions with owners, kill criteria agreed in advance, and the entry multiple range supported. It is written to be attacked, not to survey a sector.

## Method

### Step 1 -- Draw the boundary before writing anything

State the sub-sector precisely enough that a company is either in or out: activity, customer, geography, size band. "Healthcare" is not a boundary; "UK outsourced clinical waste collection, GBP 3-15M EBITDA" is. If it cannot be written as an inclusion test, it is a preference, not a boundary.

### Step 2 -- Write the core claim in one falsifiable sentence

Use the form: because [structural condition], [a type of asset] will [measurable outcome] over [period]. Then name the observation that would make it false; if none exists, rewrite it. "The market is growing" fails; "operators below five sites cannot fund the licensing capex and will sell at 6.0-7.0x" passes.

### Step 3 -- Locate the return in the EBITDA bridge

Decompose the return into organic growth, margin expansion, buy-and-build arbitrage, deleveraging and exit multiple change, then state which component carries most of it. A thesis that depends on exit multiple expansion is a bet on the market -- hold the exit flat to entry and label expansion upside.

### Step 4 -- Establish why now, not why ever

Name the catalyst that makes this a 24-month window, not a permanent condition: a compliance date, a cost curve crossing, a cohort of sponsor-owned assets entering hold years 4-6. "Fragmented and growing" has been true for a decade and is not one.

### Step 5 -- Write the must-be-true conditions

Three to five conditions, MECE, each measurable and each falsifiable by a named workstream against a named source. Conditions that cannot be tested in a normal process are underwriting assumptions -- separate them: assumptions get priced, conditions get proved.

### Step 6 -- Pre-commit the kill criteria

For each condition, state the observation that kills the thesis, with a threshold and a date. Criteria written before diligence are worth far more than those written during it: once the team has seen the number it wanted, the threshold becomes negotiable.

### Step 7 -- Price the thesis

State the entry multiple range the thesis supports and the multiple at which it stops working -- the discipline anchor for every screening decision taken under it.

## Inputs

- The sector interest as currently stated, however loose
- Fund mandate: cheque size, EBITDA range, geography, hold, return threshold
- Prior deals reviewed in the sector, including each pass and why
- Observable transaction multiples, platform and bolt-on
- Evidence for the proposed catalyst

## Output format

- Sub-sector boundary (inclusion test, one paragraph)
- Core claim (one falsifiable sentence)
- Value creation location (bridge decomposition in prose, never a table)
- Why now (catalyst with date or trigger)
- Must-be-true conditions (3-5, each with owner and test)
- Kill criteria (one per condition, with threshold)
- Supported entry multiple range, and where the thesis fails

## Example

**Fictional worked example -- European industrial water-treatment servicing.**

Core claim: servicing of an installed base is consolidating, and a platform bought at 8.5x can buy sub-scale operators at 6.0x, so arbitrage carries the return, not growth. Platform EBITDA 12 at 8.5x is EV 102; four bolt-ons totalling EBITDA 18 at 6.0x cost 108; group EBITDA 30 on EV 210 is a blended entry of 7.0x, organic growth assumed at 3% and the exit held flat.

Kill criterion: if the last eight completed bolt-ons cleared above 7.5x, they would cost 135, group EV becomes 237 and blended entry 7.9x -- 0.6x against the platform price, which does not fund integration risk. The thesis is then dead, not re-argued.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →