← Plugin catalog
Finance

Investment Banking

OpenAI v0.1.29

M&A, valuation, and financing

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Interactive
  • Read
  • Write

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Prepare an Intel strategic alternatives memo: asset sales, foundry partnerships, capital needs, buyers, and diligence gaps.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 22, 2026.

View package source →

Description

From the marketplace listing

Investment banking workflows for M&A, coverage, sponsors, ECM/DCM, LevFin, restructuring, capital advisory, valuation, buyer and investor targeting, diligence, pitch materials, and process execution.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package563 files · 1.2 MBBrowse files →
Skill instructions
buyer-investor-list14.9 KB

View saved version →

---
name: buyer-investor-list
description: build prioritized buyer, investor, lender, or sponsor universes for ib processes. use when the user asks for target lists, outreach waves, rationale, or tracker-ready parties. do not use to run the live process; use deal-process-tracker.
---

# Buyer Investor List

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `relationship_counterparty_context`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Relationship & Counterparty Context`
- `Market Data & Public Sources`
- `Process Updates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a polished standalone HTML buyer-universe report, workbook, native deck/document, generated folder first-read file, or justified chat-only answer. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing standalone HTML report, workbook, native deck/document, or clear first-read package.

## Trigger Boundary

Use for prioritized buyer, sponsor, lender, financing source, or investor universes where the user needs who to contact, why they care, whether they can transact, what risk they introduce, who should approach them, and when they belong in the process.

Role: produce a senior banker process strategy artifact, not a directory export. Optimize for price, certainty, speed, confidentiality, strategic fit, financing capacity, cultural fit, restructuring feasibility, or competitive tension based on the user's objective.

Non-role: do not run the live process, mark outreach complete, send materials, grant access, or replace the process tracker. Use `deal-process-tracker` once the universe becomes active outreach.

## Fast Workflow

1. Classify the mandate: sell-side M&A, sponsor targeting, lender/financing source, growth/minority/private placement, restructuring/distressed capital, or pu

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

capital-markets-issuance23.2 KB

View saved version →

---
name: capital-markets-issuance
description: frame issuer financing and capital-markets execution options. use when the user asks about ecm, dcm, private placements, market window, investor targeting, or use of proceeds. do not use for borrower credit approval.
---

# Capital Markets Issuance

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Models, Workbooks & Templates`
- `Relationship & Counterparty Context`
- `Deal Materials`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved format, depth, audience, or transaction-decision preferences. When the user explicitly requests HTML for an issuance recommendation, that resolves the presentation surface to a polished standalone HTML financing report; ask only remaining material choices. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a polished standalone HTML financing report, workbook, native deck/document, generated folder first-read file, or justified chat-only answer. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, standalone HTML financing report, native deck/document, or clear first-read package.

## Purpose
Act like a senior investment-banking capital markets partner advising an issuer, sponsor, board, treasurer, or cfo on whether and how to raise capital. Produce decision-grade issuance views, not generic market summaries. Every output should answer: **what should the issuer do, why now, what instrument and size, at what likely terms, with what risks, and what next steps?** Address investor strategy when it is material to execution and supported by available evidence.

## Routing contract

Default lead role: **issuer-side capital markets advisor**.

Own:
- financing strategy, instrument choice, market window, launch timing, sizing, pricing ranges, investor targe

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 15 — file references are metadata, not package contents.

cim-builder20.5 KB

View saved version →

---
name: cim-builder
description: Draft or refresh buyer-facing CIMs, teasers, CIM storyboards, lender presentations, and management presentations. Do not use for independent CIM diligence; use cim-teardown.
---

# CIM Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `process_updates`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Process Updates`
- `Relationship & Counterparty Context`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a CIM, teaser, or CIM storyboard with an unresolved surface, offer `Polished HTML CIM / storyboard (Recommended)`, `Word document (.docx)`, and `PowerPoint storyboard or deck (.pptx)`. A request for a CIM or page-flow storyboard does not by itself imply slides: select polished standalone HTML by default when intake is not required or when a non-interactive run must apply a default. Select PPTX without a format question when the user explicitly requests slides, a deck, a management presentation, a lender presentation, or `.pptx`. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.
## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the standalone HTML CIM/storyboard, banker-facing workbook, requested native deck/document, or clear first-read package.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The normal hero deliverable for a CIM, teaser, or CIM storyboard is a polished standalone HTML document. Use a native deck/document when requested or selected, a workbook for source/control work, a generated folder first-read file where justified, or chat only for narrow answers. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable and companion deliverables; mention support artifacts only when useful for the user's next action or requested, and do not link to manifests or handoff payloads in an ordinary delivery response.

## Core posture

Act like a senior sell-side investment banker / managing director building materials that must survive client review, buyer diligence, firm compliance, and process execution. Do not behave like a generic d

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 16 — file references are metadata, not package contents.

cim-teardown19.1 KB

View saved version →

---
name: cim-teardown
description: analyze seller materials into claims, diligence gaps, red flags, and model handoffs. use when the user asks to tear down a cim or banker deck. do not use to write the cim; use cim-builder.
---

# CIM-Teardown

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Models, Workbooks & Templates`
- `Process Updates`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a polished standalone HTML diligence report, workbook, native deck/document, generated folder first-read file, or justified chat-only answer. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing standalone HTML diligence report, workbook, native deck/document, or clear first-read package.

## Trigger Boundary
Use this skill when the user wants to test seller materials, including:
- a CIM, teaser, or investor deck teardown
- a claims ledger from seller materials
- evidence requests, seller asks, or a data-room gap list
- ranked diligence questions or a diligence workplan
- a red-flag register
- quick underwriting implications from seller claims
- a decision-oriented diligence memo for PE, growth, CorpDev, or confirmatory diligence

Do not use this skill for:
- writing, polishing, or designing a CIM
- building a full DCF, LBO, merger model, or valuation workbook
- generic company summaries with no diligence or falsification ask
- pure legal opinions or legal advice
- casual article or deck summarization

## Role / Non-Role
Act as the diligence lead turning seller materials into a falsification-first, decision-grade pack that tells the team whether to keep spending time.

Default posture:
- the CIM is the claim source, not proof
- decision-grade top layer first, broad 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 40 — file references are metadata, not package contents.

company-tearsheet14.4 KB

View saved version →

---
name: company-tearsheet
description: Create source-backed banker-facing company, target, borrower, issuer, or counterparty tearsheets. Use for baseline profiles, coverage screens, deal-screen inputs, and meeting context. Do not use for full memos, models, decks, or diligence reports.
---

# Company Tearsheet

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the catalogued source categories needed for the current tearsheet. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the tearsheet can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update `category-state.json`.

The runtime source categories below cover the catalogued Investment Banking sources. Use `references/source-and-evidence.md` for the broader evidence hierarchy and freshness rules.

### Workflow Sources

When this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names.

- `deal_materials`: user-provided files, deal documents, VDR exports, management materials, and diligence sources needed for the company baseline.
- `process_updates`: trackers and internal updates only when active process status materially changes the tearsheet framing.
- `relationship_counterparty_context`: relationship, sponsor, buyer, lender, and counterparty context when it materially changes the coverage or transaction read.
- `market_data_public_sources`: filings, ratings, market data, provider exports, and transaction benchmarks needed for reported facts, valuation context, and freshness checks.
- `models_workbooks_templates`: models, workbook extracts, and approved templates only when they materially improve the baseline or downstream handoff.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Relationship & Counterparty Context`
- `Deal Materials`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. When the user explicitly requests HTML for a tearsheet, that resolves the presentation surface to a polished standalone HTML banker tearsheet; ask only remaining material choices. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a polished standalone HTML report, workbook, native deck/document, generated folder first-read file, or justifi

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.

comps-valuation11.7 KB

View saved version →

---
name: comps-valuation
description: Produce source-backed trading-comps valuation for Investment Banking in report or workbook mode. Use for peer selection, trading multiples, implied valuation, Excel or Sheets comps models, EV bridges, refreshes, pressure tests, and workbook QA. Do not use for DCF, LBO, merger, three-statement, or non-banker investment decisions.
---

# Comps Valuation

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `market_data_public_sources` and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Models, Workbooks & Templates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. Downstream support steps inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md`. Preserve validated handoffs, source IDs, routing metadata, and the hero-deliverable hierarchy. Keep JSON, CSV, Markdown, logs, manifests, and handoff payloads secondary unless explicitly requested. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts when useful.

## Plugin Workflow Routing

For broad transaction workflows, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Keep `comps-valuation` as the comps owner in either mode while preserving routing metadata and the artifact hierarchy of any larger banker-facing package.

## Artifact Contract

Default to `extended_analysis` for a substantive comps request; read `../../references/output-depth-policy.md` before shortening. A report-mode hero is normally a polished standalone HTML valuation report with readable evidence support; a workbook-mode hero is an XLSX workbook with visible source, QA, and valuation support. Use chat-only output only when the user explicitly requests a quick or narrow answer.

Follow `../../references/deliverable-format-policy.md` before creating files. Always identify the hero deliverable first and keep manifests, model-citation ledgers, handoff payloads, CSV imports, and run logs as support artifacts unless explicitly requested.

## Mode Selection

Select the mode from the prompt and available context; do not ask merely because both modes exist.

- `report` mode: peer-set rationale, trading comps read-through, implied valuation, concise peer review, valuation memo/table, or substantial standalone HTML report where no editable or refreshable workbook is requested.
- `workbook` mode: Excel, Google Sheets, XLSX, exported table, refreshable/model-ready comps, linked source tabs, EV bridge formulas, sensitivity tables, update/extend of an existing workbook, or formula/model pressure test.
- If an existing work

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 19 — file references are metadata, not package contents.

covenant-package-analyzer18 KB

View saved version →

---
name: covenant-package-analyzer
description: Analyze credit documents for covenant definitions, baskets, leakage, headroom mechanics, amendments, and waivers. Use for finance-side covenant reviews, not legal advice.
---

# Covenant Package Analyzer

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials` and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Market Data & Public Sources`
- `Process Updates`
- `Models, Workbooks & Templates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a covenant package review, amendment analysis, or waiver memo with an unresolved surface, offer `Polished HTML covenant review memo (Recommended)`, `Excel covenant headroom workbook`, and `Word memo (.docx)`. Default to polished standalone HTML when intake is not required or a non-interactive run must apply a default. Select workbook-first output without a format question when the user requests calculations, covenant headroom, basket capacity, or scenarios requiring tabular inputs and formulas. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The normal hero deliverable for a covenant review, amendment analysis, or waiver memo is a polished standalone HTML finance-side credit memo. Use a workbook as the hero deliverable for computed headroom, basket capacity, or scenario analysis, with a concise standalone HTML explanation as an appropriate companion. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable and any meaningful companion; do not link to render contracts, manifests, or handoff payloads in ordinary delivery responses.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the standalone HTML covenant memo, banker-facing headroom workbook, requested native document, or clear first-read package.

## Trigger Boundary

Use this skill for finance-side covenant analysis of credit agreements, indentures, note purchase agreements, term sheets, commitment papers, amendments, waivers, side letters, covenant certificates, and related debt documents.

Lead when the user asks what the borrower can do, what lenders can st

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 12 — file references are metadata, not package contents.

dcf-model-builder11 KB

View saved version →

---
name: dcf-model-builder
description: Use when building code-backed DCF exports, WACC/terminal value work, EV-to-equity bridges, sensitivities, or price targets; not comps-only.
---

# DCF Model Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Models, Workbooks & Templates`
- `Deal Materials`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.
## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook or an explicitly requested standalone HTML valuation summary, native deck/document, or clear first-read package.

Use for DCF, intrinsic value, FCFF/FCFE, WACC, terminal value, EV-to-equity, per-share value, and price-target work. Do not use for comps-only, audits, LBO, merger, memo, or deck-QC work.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive DCF work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML valuation summary only when the user explicitly requests HTML or a narrative companion; the workbook remains the model source of truth. CSV, JSON, Markdown, run logs, manifests, model-citation ledgers, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Workflow
1. Classify: template, partial-context screen, full-plan run, deterministic export, formula workbook, or handoff.
2. Read only needed references; usually `plan-schema.md`, `output-spec.md`, and integrations.
3. Create or locate `plan.json`; preserve user assumptions and source labels.
4. Validate, run the requested export, read the run log, and build the first-read workbook view around valuation range, market read-through, drivers, source posture, and open items.
5. Keep calculation integrity and decision readiness separate: formula/control tie-outs may be `OK` while source readiness remains `OPEN` or `screen-grade`.
6. Render and visually inspect the workbook summary, valuation, assumptions/sources, sensitivities, and checks tabs before reporting artifacts.
7. Hard failures mean `not-decision-ready`. Estimate- or placeholder-driven value means open with `Screen-grade only; forecast, WACC, and terminal assumptions require review.`

## Sub-agent decomposition

For complex medium/large requests, use sub-agents where

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 27 — file references are metadata, not package contents.

deal-process-tracker14.9 KB

View saved version →

---
name: deal-process-tracker
description: Build, update, or reconstruct IB deal-process trackers in a banker-facing workbook. Use for buyer progression, outreach, NDAs, access, diligence, bids, deadlines, process status, or proxy-disclosed sale-process chronology. Do not use to create buyer universes from scratch or write narrative HTML reports.
---

# Deal Process Tracker

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `process_updates`, `relationship_counterparty_context`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Process Updates`
- `Deal Materials`
- `Relationship & Counterparty Context`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For a substantive process build, update, or reconstruction, the hero deliverable is a polished XLSX tracker with an executive `Dashboard` first tab. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, which is the workbook here, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook. Route a user request for a narrative HTML process report or board-style memo to `memo-builder`, using the tracker workbook or extracted process facts as source material; route a requested presentation to `pitch-deck-builder`.

## Trigger Boundary

Use for building, updating, or reconstructing IB deal-process trackers: buyer funnel, outreach, NDAs, materials access, diligence, process letters, IOIs/LOIs, bids, owners, dates, status, open issues, senior escalation, or public-filing chronology of a completed or signed sale process.

Role: maintain the process-execution spine or reconstruct disclosed process history, turning fragmented process facts into a workbook with source-backed status, MD judgment, risk, decision points, and change history where applicable.

Non-role: do not create the initial buyer universe from scratch, send outreach, grant materials access, provide legal advice, or silently overwrite historical tracker data. Use `buyer-investor-list` fo

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 8 — file references are metadata, not package contents.

distressed-recovery-waterfall23.5 KB

View saved version →

---
name: distressed-recovery-waterfall
description: Analyze distressed capital structures and recovery waterfalls. Use when the user asks about claims, lien priority, fulcrum security, plan value, liquidation value, sale paths, or restructuring recoveries. Do not use for standard LBO modeling.
---

# Distressed Recovery Waterfall

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Market Data & Public Sources`
- `Models, Workbooks & Templates`
- `Process Updates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a debtor-side sale-path, restructuring-alternatives, board-recommendation, or recovery-advice memo with an unresolved surface, offer `Polished HTML restructuring memo (Recommended)`, `Excel recovery waterfall workbook`, and `Word memo (.docx)`. Default to polished standalone HTML when intake is not required or a non-interactive narrative run must apply a default. Select workbook-first output without a format question when the request is principally to build, calculate, or sensitize recoveries, claims waterfalls, or value-break scenarios. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.
## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the standalone HTML restructuring memo, banker-facing recovery workbook, requested native document, or clear first-read package.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The normal hero deliverable for debtor-side sale-path, restructuring-alternatives, or board-recommendation analysis is a polished standalone HTML restructuring memo. For model-heavy recovery waterfall, claims allocation, or value-break sensitivity work, use the workbook as the hero deliverable and a concise standalone HTML explanation only when useful. CSV, JSON, Markdown, run logs, manifests, model-citation ledgers, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable and meaningful companion deliverables; do not link to manifests, renderer contracts, audit payloads, or handoff files in ordinary delivery responses.

## Standard

Operate like a senior restructuring investment banker prepa

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.

financials-normalizer19.9 KB

View saved version →

---
name: financials-normalizer
description: convert messy deal financials into model-ready statements, kpi schedules, source maps, and qa flags. use when an ib workflow needs spreading, normalization, or reconciliation. do not use for generic spreadsheet cleanup; use excel-data-cleaner.
---

# Financials Normalizer

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Models, Workbooks & Templates`
- `Deal Materials`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook or an explicitly requested standalone HTML normalization summary, native deck/document, or clear first-read package.

## Purpose
Turn messy source financials into auditable, model-ready normalized financial statements, KPI schedules, mappings, source citations, assumptions, conflicts, and QA flags for downstream finance skills.

This is a shared-core skill. Use it before valuation, LBO, transaction modeling, credit underwriting, memo, and deck workflows whenever the source financials are raw, fragmented, inconsistent, stale, or not tied out.

## Output Depth

Default to `extended_analysis`: produce or describe the full normalized package, source index, mapping logic, conflicts, assumptions, QA flags, source/evidence posture, and downstream readiness whenever financials will feed a model, memo, credit view, deck, or valuation. Use a shorter chat summary only when the user explicitly asks for it, the source context is too thin and the right answer is a source checklist/schema, or the main deliverable is already a workbook/package and chat is only a cover note. Read `../../references/output-depth-policy.md` before shortening.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive normalization work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML normalization summary only when the user explicitly requests HTML or a narrative companion; the workbook and supporting ledgers remain the normalized source of

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 12 — file references are metadata, not package contents.

ib-deck-qc19.5 KB

View saved version →

---
name: ib-deck-qc
description: quality-control investment-banking decks and reports before circulation. use when the user asks to check numbers, units, sources, charts, footnotes, formatting, or page takeaways. do not use to build the deck from scratch.
---

# IB Deck QC

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Models, Workbooks & Templates`
- `Market Data & Public Sources`
- `Process Updates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, HTML report/dashboard, native deck/document, or clear first-read package.

## Purpose

Use this skill as the banker/client-circulation gate for Investment Banking deliverables. The default job is to identify issues, prioritize fixes, and produce a polished standalone HTML QC report, annotated native deck workflow, or native-deck remediation path for pitch books, CIMs, teasers, valuation decks, financing decks, strategic alternatives materials, process materials, and committee readouts. Do not rewrite, rebuild, or redesign the deliverable unless the user explicitly asks for remediation.

This skill replaces the generic deck/report review dependency inside the Investment Banking plugin. Route final IB materials here, not to a generic deck/report review skill.

## Banker circulation ownership

This skill owns the final IB circulation decision:
- whether a deck, CIM, teaser, buyer list, financing pitch, valuation deck, or process material is ready for analyst fixes, VP/director review, MD review, client circulation, buyer/lender circulation, or is not circulable;
- whether numbers, units, dates, footnotes, sources, page titles, charts, and narrative claims tie across the deck, model, source files, and supporting materials;
- whether valuation, financing, leverage, covenant, returns, accretion/dilution, buyer rationale, process, and market pages carry the caveats needed for banker/client use;
- whether the page-level "so what" is clear enough for a banker to present without re-explaining the analysis.

Preserve the strongest generic QC controls: repeated-number tie-outs, source and footnote coverage, visual review, chart-to-narrative consistency, issue taxonomy, remediation sequence, posture labels, and explicit missing-support-file flags.

## Operating principles

1. Treat every number, unit, footnote, chart, and conclusion as something that must tie to an identified source or model output.
2. Separate deterministic findi

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

investment-banking15.9 KB

View saved version →

---
name: investment-banking
description: Route Investment Banking workflows for banker-owned transaction, capital markets, valuation, diligence, buyer/investor targeting, pitch, process, and restructuring work. Use when the user is preparing, reviewing, or executing M&A, financing, sponsor, issuer, lender, restructuring, coverage, or deal-advisory work, including CIMs, teasers, pitch materials, buyer lists, process trackers, merger models, capital markets analysis, and banker-facing valuation or diligence outputs. Do not use for public-equity investment decisions, personal financial advice, legal advice, FP&A, or generic writing tasks with no transaction or banker-workflow context.
---

# Investment Banking Router

## Skill Purpose

Route broad or focused Investment Banking intent to one or more explicit-only constituent skills. Treat explicit `@investment-banking`, `@Investment Banking`, or direct plugin invocation as strong intent to use this plugin, then apply the invocation gate below before substantive work. When the gate passes, choose the narrowest relevant lead skill from the map below, read each exact installed `skills/<skill-id>/SKILL.md` file before using it, and preserve any support-skill sequence from the routing playbook. Prefer a relevant Investment Banking sibling when the request overlaps generic finance, valuation, document, deck, model, diligence, or transaction-advisory work. Do not answer from the router alone when a focused owner exists.

## Plugin Purpose

Investment Banking provides banker-readable workflows for M&A, coverage, sponsor and strategic alternatives, ECM/DCM/LevFin, restructuring, valuation, CIM/VDR/Datasite diligence, buyer and investor targeting, process execution, pitch materials, model work, committee materials, and deal-team QC. It uses workflow-scoped source setup: connect or request only the source categories a selected banker workflow actually needs, while supporting pasted context, uploaded files, exports, public evidence, and existing models as fallback inputs.

## Bundled Path Resolution

Resolve router-owned bundled Markdown paths relative to the directory containing this `SKILL.md` before the first read; do not probe the caller's current working directory. From this router directory, shared references use `../../references/...`, sibling visible skills use `../...`, and bundled internal support uses `internal-support/...`.

Shell commands explicitly labeled plugin-root-relative are the exception: set the shell working directory to the plugin root (`../..` from this router directory) before running them.

## Invocation Gate

Read `../../references/invocation-policy.md` before choosing any specialist.
If the prompt has neither an explicit Investment Banking invocation nor banker-owned transaction, valuation, diligence, pitch, process, capital markets, restructuring, coverage, sponsor, issuer, lender, or deal-advisory context, do not route into this plugin.

# Skills

## cim-teardown

Use when controlling deal materials, CIMs, teasers, management presentations, VDR/Datasite exports, seller claims, diligence documents, or source packets need teardown before a banker relies on them.

## cim-builder

Use when the user needs a banker-readable CIM, teaser, buyer-facing narrative, management-presentation story, or source-aware marketing-material draft.

## buyer-investor-list

Use for buyer, sponsor, lender, strategic acquirer, investor, counterparty, or outreach-wave universe work that needs ranked targets and relationship/context rationale.

## deal-process-tracker

Use when the main artifact is a tracker for VDR access, NDA status, bidder status, process milestones, deadlines, bid logs, diligence requests, or next actions.

## capital-markets-issuance

Use for ECM, DCM, LevFin, private placement, hybrid, convert, refinancing, liquidity, market-window, proceeds, dilution, or financing alternatives advice.

## private-credit-underwriting

Use for lender-facing or borrower credit underwr

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 53 — file references are metadata, not package contents.

lbo-model-build11.8 KB

View saved version →

---
name: lbo-model-build
description: Build sponsor LBO models for sources and uses, debt, sweep, liquidity, returns, and downside underwriting. Use for take-privates, acquisition financing, or leverage screens; not DCF-only work.
---

# LBO Model Build

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Models, Workbooks & Templates`
- `Market Data & Public Sources`
- `Relationship & Counterparty Context`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For an initial sponsor LBO model, take-private screen, or acquisition-financing model with an unresolved surface, offer `Excel sponsor LBO workbook (Recommended)`, `Polished HTML underwriting summary`, and `Inline screening view`. Default to the banker-readable workbook when intake is not required or a non-interactive model-build run must apply a default. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.
## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, an explicitly requested standalone HTML underwriting summary, native deck/document, or clear first-read package.

Use for sponsor underwriting, acquisition financing, take-private screens, carve-outs, debt capacity, covenant headroom, liquidity survival, reverse stress, and XLSX exports. Do not use for DCF-only work, pure explainers, legal covenant interpretation, independent workbook audit, or final deck QC.

Rules: identify the decision lens; use available context before asking; keep EBITDA bases separate; do not present covenant EBITDA without the governing definition; label material inputs as `sourced_fact`, `management_assumption`, `seller_claim`, `sponsor_assumption`, `lender_case`, `analog_proxy`, `fallback_assumption`, or `unsupported`; default to `deterministic_export`. When final funded debt, commitment papers, or closing funds flow is unavailable, call the modeled financing an `illustrative financing case` or `public-source screening case`, cap posture at `screen-grade`, and make financing uncertainty visible in the first-read view.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive LBO work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML underwriting summary only when the user explicitly requests HTML or a narrative companion; the workbook remains the model source of truth. CSV, JSON, Markdown, run logs, manifests, model-citation ledgers, and handoff payloads are support artifacts unless the user

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 44 — file references are metadata, not package contents.

meeting-prep18.5 KB

View saved version →

---
name: meeting-prep
description: prepare ib meeting briefs, question lists, and debrief follow-ups. use when the user asks for call prep, buyer or lender meeting materials, diligence questions, or action tracking. do not use for full memo drafting.
---

# Meeting Prep

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the catalogued source categories needed for the current meeting. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the meeting brief can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update `category-state.json`.

The runtime source categories below cover the catalogued Investment Banking sources. Use `references/context-and-sources.md` for the broader evidence hierarchy, including optional meeting-logistics connectors.

### Workflow Sources

When this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names.

- `deal_materials`: VDR exports, diligence documents, process letters, and source materials needed for an active transaction or diligence meeting.
- `process_updates`: trackers, meeting notes, and internal updates needed for status, action, or debrief context.
- `relationship_counterparty_context`: relationship, buyer, lender, sponsor, and counterparty context when it changes the meeting plan.
- `market_data_public_sources`: public filings, market data, ratings, and transaction benchmarks only when they materially change the coverage angle or meeting questions.
- `models_workbooks_templates`: models, workbooks, and templates only when they materially change the meeting baseline, analysis, or follow-up.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Process Updates`
- `Deal Materials`
- `Relationship & Counterparty Context`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. When the user explicitly requests HTML for a meeting brief, that resolves the presentation surface to a polished standalone HTML briefing note; ask only remaining material choices. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a polished standalone HTML meeting brief, workbook, native deck/document, generated folder first-read file, or justified chat-only answer. CSV, JSON, Ma

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

memo-builder19.2 KB

View saved version →

---
name: memo-builder
description: draft or review investment-banking memos from existing analysis. use when the user wants a client, committee, board, financing, process, or diligence note. do not use to build source models, decks, trackers, or tearsheets.
---

# Memo Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `process_updates`, `relationship_counterparty_context`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Process Updates`
- `Market Data & Public Sources`
- `Models, Workbooks & Templates`
- `Relationship & Counterparty Context`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantial memo work, the selected or high-confidence inferred surface controls the hero deliverable: formal banker, committee, board, client, or lender memos usually use a real Word document; source-heavy web-style reports usually use polished standalone HTML; quick narrow notes may stay inline. If the surface is semi-ambiguous, use `../../references/deliverable-intake-policy.md` before drafting and let the chosen or timeout-resolved option control the manifest primary. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing selected memo surface, workbook, native deck/document, or clear first-read package.

## Trigger Boundary

Use this skill when the user wants model outputs, CIM claims, diligence findings, buyer feedback, meeting notes, process status, or other Investment Banking analysis converted into a decision-ready memo for a client, MD, committee, board, lender, sponsor, issuer, or deal team.

Use it for client recommendations, committee approval notes, board or special committee notes, ECM/DCM/LevFin/private-placement framing, lender or credit committee support, transaction updates, process summaries, diligence synthesis, management-call readouts, one-pa

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 6 — file references are metadata, not package contents.

merger-model-builder14 KB

View saved version →

---
name: merger-model-builder
description: Build merger and accretion/dilution models for consideration, pro forma ownership, synergies, purchase accounting, financing mix, or EPS impact. Use for strategic M&A modeling; not standalone DCF or LBO work.
---

# Merger Model Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Models, Workbooks & Templates`
- `Deal Materials`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a merger model, accretion/dilution screen, or pro forma ownership model with an unresolved surface, offer `Excel merger / accretion workbook (Recommended)`, `Polished HTML transaction summary`, and `Inline screening view`. Default to the banker-readable workbook when intake is not required or a non-interactive model-build run must apply a default. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, an explicitly requested standalone HTML transaction summary, native deck/document, or clear first-read package.

Produce M&A model artifacts that answer whether the consideration structure, ownership transfer, synergies and accounting/financing effects support the deal rationale. For substantive merger-model work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Use the full deterministic or formula engine when the input set supports its accounting scope; do not manufacture PPA or GAAP inputs merely to make a public-source adjusted-EPS screen fit a full-schema engine.

## Scope

Own sources/uses, consideration mix, PPA, financing, synergies, PF earnings, shares, ownership, EPS accretion/dilution, sensitivities, checks, and posture. Route sourcing, normalization, financing/covenant work, memo/deck polish, and independent workbook audit to the adjacent finance/IB skills.

## Rules

Use available prompt/files/connectors first; use placeholders only when the user wants a model despite gaps. Never overwrite user source files. Generated outputs go to a new or user-specified output directory.

Every material input needs a native evidence label from `references/plan-schema.md`. For partial context, the first user-facing output starts with:

> **SCREEN-GRADE: adjusted EPS analysis based on disclosed projections and modeled assumptions; GAAP accretion/dilution is not presented without complete PPA and post-close actualization support.**

Use this warning when ownership, disclosed projections, or synergy analysis can be completed but PPA, 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 28 — file references are metadata, not package contents.

model-audit-tieout13.6 KB

View saved version →

---
name: model-audit-tieout
description: audit existing financial models and workbook outputs. use when the user asks to check formulas, sources, assumptions, sensitivities, links, or model readiness. do not use to build a new model from scratch.
---

# Model Audit Tie-out

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Models, Workbooks & Templates`
- `Deal Materials`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a review of an attached workbook, preserve `.xlsx` as the default presentation surface by producing a separate audit workbook; do not edit the source model unless the user explicitly asks for remediation. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For a substantive review of an existing financial model, the normal hero deliverable is a polished banker-readable workbook audit pack. Use a standalone HTML audit summary only when the user explicitly requests HTML or the resolved format choice requires a narrative companion. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so a standalone model-review request results in a banker-facing audit workbook, while a committee memo or deck workflow can consume the audit findings without displacing its own hero deliverable.

## Trigger Boundary

Use this skill to audit an existing financial model, workbook, forecast, valuation file, sensitivity deck, or model-derived output. It is the quality-control layer for formula integrity, workbook structure, source support, assumptions, sensitivities, links, and decision readiness.

Use it when the user asks to check:
- formulas, hardcodes, broken links, circularity, hidden sheets, or workbook hygiene.
- whether model outputs tie to sources, decks, memos, assumptions, or cited documents.
- whether scenarios, downside cases, sensitivities, or model outputs are decision-useful.
- whether a model is ready for IC, credit committee, client delivery, board review, or diligence.

Do not use it to build a new model from scratch. Route new-build work to the relevant builder skill, and only edit or remediate a workbook when the user explicitly asks for changes.

## Role And Non-Role

Role: map the model, diag

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

pitch-deck-builder16.1 KB

View saved version →

---
name: pitch-deck-builder
description: build investment-banking pitch deck outlines, page plans, and draft slide content. use when the user asks to create or refresh a banking pitch or client discussion deck. do not mark final client-ready; route final circulation qc to ib-deck-qc.
---

# Pitch Deck Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `process_updates`, `relationship_counterparty_context`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Deal Materials`
- `Market Data & Public Sources`
- `Relationship & Counterparty Context`
- `Process Updates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The hero deliverable must be a workbook, HTML report/dashboard, native deck/document, generated folder first-read file, or justified chat-only answer. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, HTML report/dashboard, native deck/document, or clear first-read package.

## Trigger Boundary

Use for investment banking buyer pitches, sell-side and M&A pitches, financing pitches, strategic alternatives decks, company profile decks, market maps, sector updates, capital structure discussions, and board/client meeting decks.

Role: orchestrate the pitch storyline, page architecture, source posture, draft slide content, and structured handoffs.

Non-role: do not replace full valuation/modeling/diligence skills, do not make legal/tax/accounting/securities-law conclusions, and do not mark a deck final client-ready. Route circulation review to `ib-deck-qc`.

Success condition: produce a concise, decision-led banker deck in which each core page advances the audience's decision, supported facts and banker judgment are clearly distinguished, and visual QA is performed on the final exported artifact.

## Fast Workflow

1. Classify the deck type, audience, objectiv

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 22 — file references are metadata, not package contents.

private-credit-underwriting21.5 KB

View saved version →

---
name: private-credit-underwriting
description: Build borrower-level private credit underwriting views for lender cases, credit memos, debt sizing, downside, liquidity, collateral, recovery, and proceed/decline decisions. Use for lender-side credit decisions, not issuer financing strategy.
---

# Private Credit Underwriting

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

### Source Resolution

Load `../../references/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `deal_materials`, `market_data_public_sources`, and `models_workbooks_templates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Market Data & Public Sources`
- `Deal Materials`
- `Models, Workbooks & Templates`
- `Relationship & Counterparty Context`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a private-credit initial screen, lender underwriting memo, or acquisition-financing credit review with an unresolved surface, offer `Polished HTML lender underwriting memo (Recommended)`, `Excel debt-capacity / lender-case workbook`, and `Word credit memo (.docx)`. Default to polished standalone HTML when intake is not required or a non-interactive run must apply a default. Select workbook-first output without a format question when the user requests reusable debt sizing, liquidity, covenant, or downside calculations. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. The normal hero deliverable for an initial screen or lender underwriting memo is a polished standalone HTML lender memo. Use an XLSX workbook as the hero deliverable for reusable debt-capacity, lender-case, liquidity, covenant, or downside calculations, with a concise standalone HTML explanation as an appropriate companion. Native documents, generated folder first-read files, and justified chat-only answers remain available when requested or appropriate. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, standalone HTML lender memo, native deck/document, or clear first-read package.

## Trigger Boundary

Use this skill for borrower-level private credit decisionin

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 13 — file references are metadata, not package contents.

scenario-sensitivity-generator14.8 KB

View saved version →

---
name: scenario-sensitivity-generator
description: create scenario, sensitivity, stress-test, and breakeven frameworks for ib analyses. use when the user asks to pressure-test model drivers, cases, downside paths, or decision thresholds. do not build base models.
---

# Scenario & Sensitivity Generator

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Models, Workbooks & Templates`
- `Market Data & Public Sources`
- `Deal Materials`
- `Process Updates`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a scenario or sensitivity analysis with an unresolved surface, offer `Excel sensitivity workbook (Recommended)`, `Polished HTML sensitivity summary`, and `Inline screening view`. Default to the banker-readable workbook when intake is not required or a non-interactive analysis run must apply a default. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive sensitivity work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML sensitivity summary only when the user explicitly requests HTML or a narrative companion; keep the workbook as the calculation source of truth when one exists. CSV, JSON, Markdown, run logs, manifests, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, an explicitly requested standalone HTML sensitivity summary, native deck/document, or clear first-read package.

## Purpose

Turn an existing IB transaction model or analysis into a banker-ready sensitivity pack. Preserve the base model, change only explicit drivers, quantify what moved, identify what breaks first, and translate the output into deal actions.

This is not an FP&A scenario-planning skill. It is for transaction sensitivities: valuation, debt capacity, covenant headroom, financing terms, merger-model outputs, downside/breakage, sponsor returns, restructuring recoveries, and target backsolves.

## Use This Skill When

- The user has an existing DCF, comps, LBO, merger model, financing case, covenant model, credit case, or recovery waterfall and wants to stress outputs.
- The decision depends on price, valuation range, leverage, covenant cushion, liquidity, financing cost, dilution,

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 15 — file references are metadata, not package contents.

three-statement-model-builder11.6 KB

View saved version →

---
name: three-statement-model-builder
description: Use when building integrated three-statement operating model exports with linked IS, BS, CF, drivers, checks, scenarios, or formula templates.
---

# Three Statement Model Builder

## Skill Configuration

### Common Skill Instructions

MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../investment-banking/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../references/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`.

## Relevant Dependency Categories

These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation.

- `Models, Workbooks & Templates`
- `Deal Materials`
- `Market Data & Public Sources`

## Deliverable Intake

When this skill owns a new substantive user-facing artifact, before source gathering, analysis, modeling, or rendering load `../../references/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. When invoked as a downstream support step within an already scoped workflow, inherit resolved preferences and do not re-prompt.
## Plugin Workflow Routing

For broad transaction workflow prompts, read `../../references/plugin-routing-playbook.md` before selecting or sequencing skills. Use this skill as lead only in the workflows named there; when acting as support, preserve validated handoff fields, source IDs, routing metadata, and the artifact hierarchy so the hero deliverable remains the banker-facing workbook, an explicitly requested standalone HTML companion, native deck/document, or clear first-read package.

Use for linked IS, BS, CF, working capital, PP&E/D&A, debt, cash sweep, liquidity, covenants, scenarios, sensitivities, and checks. Do not use for audit, LBO, DCF/comps/merger, memo, or deck work.

## Artifact Hierarchy

Follow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive three-statement modeling work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML operating-model summary only when the user explicitly requests HTML or a narrative companion; the workbook remains the model source of truth. CSV, JSON, Markdown, run logs, manifests, model-citation ledgers, and handoff payloads are support artifacts unless the user explicitly asks for them. Final responses should lead with the hero deliverable, then companion deliverables, then support artifacts in one short sentence if useful.

## Workflow
1. Classify: template, partial-context screen, full financial package, deterministic export, formula workbook, or handoff.
2. Read only needed references; usually `plan-schema.md`, `output-spec.md`, and integrations.
3. Create or locate `plan.json`; preserve raw files, formulas, assumptions, and labels.
4. Validate, run the requested export, read the run log, and build the first-read workbook view around operating drivers, cash conversion, liquidity, downside pressure, source posture, and open diligence.
5. Keep calculation integrity and decision readiness separate: balance-sheet, cash and formula checks may be `OK` while source readiness remains `OPEN` or `screen-grade`.
6. Render and visually inspect the workbook summary, driver/assumptions, scenario, statements, sources and checks tabs before reporting artifacts.
7. Hard failures mean `not-decision-ready`. Placeholder- or analyst-assumption-driven conclusions mean open with `Screen-grade only; operating, liqu

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 25 — file references are metadata, not package contents.

user-context5.85 KB

View saved version →

---
name: user-context
description: Initialize, inspect, save, update, forget, export, or explicitly reset the Investment Banking plugin's local user context, source setup, or optional automation setup. Use only when the user explicitly asks to manage Investment Banking saved preferences, source pointers, context storage, or recurring automation.
---

# Investment Banking User Context

This skill owns the Investment Banking plugin's local user-context storage foundation and explicit-only onboarding contract. It is intentionally narrow: it can initialize, inspect, save, update, forget, export, or explicitly reset local context, interpret the next onboarding action, guide the four-step intro/defaults -> connectors/plugins -> automation -> hero-workflow flow, and configure user-approved automations. Ordinary Investment Banking workflows do not invoke this skill by default; saved context and source setup are optional accelerators, not a pre-answer gate.

## State Files

Store Investment Banking state under:

```text
$CODEX_HOME/state/plugins/openai-monorepo/investment-banking/
```

The storage foundation owns only:

```text
user-context.md
onboarding-state.json
```

Do not create `category-state.json`.

## Initialize

When the user explicitly asks to initialize Investment Banking user context, run `python3 skills/user-context/scripts/init_user_context_state.py` with the shell working directory set to this plugin's root. Set the working directory before the first attempt; do not probe alternate relative paths.

The initializer creates missing state files from bundled templates and preserves existing files unless the user explicitly requests overwrite behavior.

## Inspect

When the user explicitly asks to inspect saved Investment Banking context, run `python3 skills/user-context/scripts/user_context_preflight.py` with the shell working directory set to this plugin's root. Set the working directory before the first attempt; do not probe alternate relative paths.

Use the returned read-only JSON envelope to summarize initialization status, onboarding status, the deterministic `next_action`, the lightweight `onboarding_progress`, and empty memory categories. Treat `user-context.md` as user-editable durable context and `onboarding-state.json` as operational scaffolding.

## Save Update Or Forget

When the user explicitly asks to remember, save, update, forget, export, or apply durable Investment Banking preferences or source pointers, follow `skills/user-context/references/plugin-memory.md` from the plugin root. Store reusable user-approved context in `user-context.md`; keep live mandate details and operational connector state out. Initialize missing state only when a save needs persistence.

## Onboarding

When the user explicitly asks to set up, resume, defer, quiet, or complete Investment Banking onboarding, follow `skills/user-context/references/onboarding.md` from the plugin root. Use the inspection helper's `next_action` as the current step and render its `copy_ref` template substantially verbatim. Keep the visible flow to four steps: intro and lightweight defaults, connectors and plugins, one optional automation, then a three-option hero-workflow chooser. Capture broader durable preferences only when the user explicitly asks or supplies them naturally.

## Source Category Vocabulary

`skills/user-context/plugin-author-config/source-category-config.json` reserves static Investment Banking source category ids, labels, and preference hints for explicit setup/status work. The inspection helper exposes those categories as `source_category_plan` and echoes any setup-owned routes already saved under `onboarding-state.json` `connector_confirmation`. Ordinary workflow skills use the router's cross-skill runtime contract and `.app.json` categories instead of reading this helper first. Use `skills/user-context/references/source-category-runtime.md` from the plugin root for the source-setup boundary. Inspection does not prove source readine

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 14 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Proprietary
Package author
OpenAI
Keywords
See keywords

Declared capabilities

  • Interactive
  • Read
  • Write

Package observed Nov 22, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 18:00 UTC
Collection status
Collected

Plugin_68c39ea2b3888191827c933053f3a1d1

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.