scenario-sensitivity-generator

Generate transaction sensitivity overlays and workbook-ready outputs for investment banking models.

1|2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill scenario-sensitivity-generator-muzewinter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-sensitivity-generator
Source: https://github.com/MuzeWinter/CooperAPI-Plugin/tree/main/plugins/investment-banking/skills/scenario-sensitivity-generator
Command: npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill scenario-sensitivity-generator-muzewinter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns an existing investment banking model into a decision-focused sensitivity package, so teams can pressure-test valuation, leverage, covenants, financing, merger outcomes, downside risk, and target backsolves without rebuilding the base model.

Core Features & Use Cases

  • Banker-ready sensitivity packs: Produces workbook-first outputs with case summaries, sensitivity tables, breakpoints, trigger metrics, and deal action registers.
  • Transaction-specific analysis: Supports valuation, debt capacity, covenant headroom, financing terms, merger model, downside/breakage, returns, and target backsolve workflows.
  • Traceable scenario overlays: Tracks baseline values, scenario changes, embedded corrections, excluded unresolved items, and provenance for each driver adjustment.
  • Decision support: Highlights first breakage points, required assumptions, feasibility labels, and recommended deal actions for client, lender, sponsor, or committee review.

Quick Start

Ask the scenario-sensitivity-generator skill to convert an existing transaction model into a banker-ready sensitivity workbook with scenario overlays, breakpoints, and deal actions.

Frequently Asked Questions about scenario-sensitivity-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run sensitivity analysis on an existing investment banking model for covenant headroom and debt capacity?

Sensitivity analysis for covenant headroom and debt capacity requires applying transaction sensitivity overlays to your existing investment banking model to generate workbook-ready outputs with breakpoint analysis and trigger actions.

What is the best way to build banker-ready sensitivity tables for LBO returns and valuation scenarios?

Building banker-ready sensitivity tables for LBO returns and valuation scenarios involves generating workbook-first deliverables with case summaries, labeled driver changes, trigger metrics, and recommended deal actions for committee review.

How do I track provenance and baseline values when pressure-testing merger model outcomes?

Tracking provenance when pressure-testing merger model outcomes requires applying traceable scenario overlays that record baseline values, embedded corrections, excluded unresolved items, and scenario changes for each driver adjustment.

Can I generate target backsolve workflows and downside breakage analysis without rebuilding my base model?

Generating target backsolve workflows and downside breakage analysis without rebuilding your base model is possible by applying transaction sensitivity overlays that produce feasibility labels and highlight first breakage points.

Does this approach to scenario overlays support financing terms and sponsor returns analysis for committee review?

Scenario overlays for financing terms and sponsor returns analysis support committee review by producing decision-focused sensitivity packages with required assumptions, feasibility labels, and recommended deal actions.

What are the limitations of using sensitivity overlays for transaction models?

Sensitivity overlays for transaction models require labeled driver changes and exclude unresolved items from the baseline, meaning any analysis depends on the accuracy of your existing model inputs and provenance tracking.