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

Returns Sensitivity

ASecurity

Isolates the two or three variables a return genuinely depends on, presents the return surface across them, and states the entry price at which the base case stops clearing the hurdle -- when you need a walk-away price rather than a range of hopes.

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

Works with

terminalcliapi

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill returns-sensitivity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Returns Sensitivity?

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

Security grade badge for Returns Sensitivity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-returns-sensitivity/badge)](https://www.skillsdirectory.com/skills/andreworia-returns-sensitivity)

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

Download with Pro
Files
SKILL.md
---
name: Returns Sensitivity
description: Isolates the two or three variables a return genuinely depends on, presents the return surface across them, and states the entry price at which the base case stops clearing the hurdle -- when you need a walk-away price rather than a range of hopes.
---

# Returns Sensitivity

## When to use

Use this skill once a base case exists and the question turns to how much of the return is assumption. It is the discipline that runs before a final bid, and again whenever someone proposes stretching for the asset. Its output is a single number the deal team commits to in advance: the price above which the base case no longer clears the fund's own hurdle.

## What it does

Produces a sensitivity note: a one-at-a-time elasticity test that separates the variables that move the return from the ones that decorate it, a return surface across the two that survive, a note of which of them the sponsor actually controls, and a stated walk-away price in both multiple and enterprise value.

## Method

### Step 1 -- Strip the collinear variables before flexing anything

Revenue growth, margin and exit-year EBITDA are one variable arriving three ways: flex the terminal one only, or the surface double-counts and no one can read it. Entry leverage is not a function of price -- lenders size off EBITDA, not off what you agreed to pay -- so hold debt fixed in dollars while entry multiple moves.

### Step 2 -- Run the elasticity test with comparable increments

Move each candidate one realistic increment either way, everything else at base: a turn of exit multiple, ten per cent of exit-year EBITDA, half a turn of entry, a hundred basis points of rate, fifteen million of cumulative cash generation. Increments must be equally likely, or the ranking is an artefact of how far you pushed each one. Keep what moves the IRR by more than a point or two; say which you discarded and why.

### Step 3 -- Build the surface across the survivors

Cross the two dominant variables on a three-by-three or five-by-five grid with the base case at the centre, and report the IRR in every cell -- in prose, one line per row, never as a table. Then count the cells that clear the hurdle. That count is the finding; the individual cells are the evidence for it.

### Step 4 -- Mark what the sponsor controls

Of the dominant variables, one is usually the entry price and the others are usually not: the exit multiple belongs to the market, exit EBITDA to management and the market together, entry price to you alone. If every cell that clears the hurdle requires multiple expansion or a beat on plan, the return is not sensitive to those things, it is dependent on them. Use that word in the memo.

### Step 5 -- Solve for the walk-away price

Hold everything else at base and solve for the entry multiple at which the base case returns exactly the hurdle. Keep the exit convention you committed to: if the base case exits flat to entry, a lower entry price lowers the exit assumption too, and the walk-away lands further below the ask than people expect. A walk-away computed with the exit multiple pinned at the ask is not a walk-away -- it is a multiple-expansion assumption wearing a disguise. State the answer as a multiple and an enterprise value, before the bid is due, and record it.

## Inputs

- The base-case model: entry, capital structure, operating plan, exit
- Fund hurdle rate and the hold period the hurdle is measured over
- Cumulative cash generation over the hold, by year
- Exit multiple evidence: comparable trading and transaction ranges
- The asking price or guided range from the process

## Output format

1. Variables tested, and the collinear ones removed
2. Elasticity results: IRR points gained and lost per increment
3. The two or three that survive, ranked
4. Return surface across them, in prose, one line per row
5. Which variables the sponsor controls
6. Walk-away price: multiple, enterprise value, and gap to the ask

Total length: 500-800 words. The walk-away price appears in the first paragraph and the last.

## Example

**Sensitivity note (fictional -- Ardleigh Clinical Labs, outsourced diagnostics):**

Entry at 11.0x QoE EBITDA of $25.0M is EV of $275.0M; with $125.0M of debt and $9.0M of fees, equity at risk is $159.0M. The base case reaches $40.0M of EBITDA in year 5, pays down $55.0M, and exits flat at 11.0x: exit equity of $370.0M, 2.33x and 18.4% against a 20% hurdle. Elasticity: a turn of exit multiple is worth +2.5 / -2.7 IRR points, ten per cent of exit EBITDA +2.7 / -3.0, half a turn of entry +0.6 / -0.5, fifteen million of cash generation +0.9 / -1.0, and a hundred basis points of rate about a third of a point. Two variables carry the deal; rate and cash generation are noise beside them.

The surface, exit multiple across 10.0x, 11.0x and 12.0x: at $36.0M of exit EBITDA, 12.8%, 15.4% and 17.9%; at $40.0M, 15.7%, 18.4% and 20.9%; at $44.0M, 18.4%, 21.1% and 23.6%. Three cells of nine clear the hurdle, and each of the three requires either a turn of expansion or a ten per cent beat on the plan -- neither of which the sponsor controls. Solving for 20.0% with the exit held flat to entry gives 9.85x, or $246.3M of enterprise value: $28.8M below the ask, returning 2.49x on $130.3M of equity. Pinning the exit at 11.0x while flexing entry would report 10.6x instead -- $265.0M, $18.7M higher -- and that difference is four-tenths of a turn of expansion nobody has agreed to. The walk-away is 9.85x.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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', ...

693161 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 →