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

Sensitivity Analysis

ASecurity

Builds two-variable data tables around a base case to show which drivers move value the most, expressed as swing in value, IRR, or EPS.

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

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Sensitivity Analysis?

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

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

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

Download with Pro
Files
SKILL.md
---
name: sensitivity-analysis
description: Builds two-variable data tables around a base case to show which drivers move value the most, expressed as swing in value, IRR, or EPS.
---

# Sensitivity Analysis Agent

## When to use
Use this agent when you need to see what moves value the most: after a base-case model is built and you want to know which assumptions to defend hardest, or before a committee that will ask how robust the number is. Unlike scenario analysis, this isolates variables one or two at a time rather than telling coherent stories. Reach for it once the base case is stable enough to flex.

## What it does
Produces sensitivity ranges across the key value drivers, typically as a two-variable data table around the base case, showing the swing in the output metric and identifying the highest-leverage driver.

## Method
1. Fix the base case and the single output metric that matters.
   - Common metrics are enterprise value, IRR, MOIC, or accretion/dilution EPS.
   - Lock the base case first so every flex is measured against one clean reference point.

2. List the candidate drivers and rank them by expected leverage.
   - Typical candidates: growth rate, margin, exit multiple, entry multiple, WACC or discount rate, leverage, and financing cost.
   - Rank by how much each plausibly moves the output, not just how uncertain it is.

3. Pick the two most material drivers for the primary two-variable data table.
   - Everything else can be shown as one-way sensitivities.
   - Pitfall: pairing two drivers that are really the same bet, which wastes a dimension.

4. Set a sensible step range around the base for each.
   - For example plus or minus fifty and one hundred basis points, or half a turn and a full turn of multiple.
   - Keep steps symmetric so the swing is easy to read.

5. Build the two-variable data table.
   - One driver across the columns, the other down the rows, with the output metric at each intersection and the base case in the center cell.

6. Read the swing.
   - Compare the corners and the center to see how far the metric moves for a given move in each driver.
   - The wider the spread along an axis, the more that driver matters.

7. Identify the highest-leverage driver and any threshold.
   - Name the driver whose range produces the widest swing, and flag where the deal stops clearing its hurdle.

8. Add one-way sensitivities for secondary drivers.
   - Summarize which assumptions the recommendation is most exposed to and which barely move the answer.

## Inputs
- The base-case model or its key outputs and assumptions
- The output metric to sensitize (enterprise value, IRR, MOIC, EPS)
- The candidate drivers and a reasonable range for each
- The step size to flex each driver by
- Any hurdle rate or threshold the output must clear
- Any drivers that are contractually fixed and should not be flexed

## Output format
Claude returns:
- The base-case output value as the reference point.
- A prose description of the two-variable data table: which driver is on each axis, the range and step of each, and the output value at the base case, at the corners, and at any threshold crossing.
- A swing read: the change in the output across each driver's range, and the named highest-leverage driver.
- One-way sensitivities for the secondary drivers, ranked by materiality.
The data table is described in words, never rendered as a markdown table.

## Example
For a sponsor's LBO of Northwind Logistics, the base case gives a five-year IRR of twenty-two percent. The two-variable data table sensitizes exit EV/EBITDA multiple across the columns, from 7.0x to 9.0x in half-turn steps, and revenue CAGR down the rows, from four percent to eight percent in one-point steps, with the base case at 8.0x and six percent in the center. IRR ranges from about fourteen percent in the bottom-left corner (7.0x exit, four percent growth) to about thirty percent in the top-right (9.0x exit, eight percent growth). The exit multiple is the highest-leverage driver: a full turn moves IRR by roughly six points, versus about four points for two points of CAGR. IRR drops below the twenty percent hurdle once the exit multiple falls under 7.5x at base-case growth, which is the number to defend hardest in committee. One-way sensitivities show entry leverage and financing cost as the next most material drivers, while working-capital timing barely moves the return.

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 →