{"id":15847,"plugin_id":"Plugin_68c39ea2b3888191827c933053f3a1d1","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:12:10.041Z","digest":"3d96b8dffaea7b7400a45c6a86748362e4640a4553be75da2f77c6c2c35ad978","against":null,"payload":{"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.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":347},{"relative_path":"assets/plan_template.json","size_in_bytes":3980},{"relative_path":"assets/plan_template_full","size_in_bytes":7770},{"relative_path":"assets/templates/banker_formula_workbook_template.xlsx","size_in_bytes":36206},{"relative_path":"references/banker-formula-workbook-contract.md","size_in_bytes":588},{"relative_path":"references/deep/banker-formula-workbook-contract","size_in_bytes":5662},{"relative_path":"references/deep/investment-banking-integrations","size_in_bytes":2657},{"relative_path":"references/deep/model-math","size_in_bytes":4516},{"relative_path":"references/deep/output-spec","size_in_bytes":9982},{"relative_path":"references/deep/plan-schema","size_in_bytes":8124},{"relative_path":"references/deep/qa-checks","size_in_bytes":4669},{"relative_path":"references/deep/workflow-and-mode-selection","size_in_bytes":2132},{"relative_path":"references/investment-banking-integrations.md","size_in_bytes":924},{"relative_path":"references/model-math.md","size_in_bytes":431},{"relative_path":"references/output-spec.md","size_in_bytes":1598},{"relative_path":"references/plan-schema.md","size_in_bytes":654},{"relative_path":"references/qa-checks.md","size_in_bytes":1025},{"relative_path":"references/workflow-and-mode-selection.md","size_in_bytes":96},{"relative_path":"scripts/build_banker_formula_workbook.py","size_in_bytes":299},{"relative_path":"scripts/requirements.txt","size_in_bytes":162},{"relative_path":"scripts/run_pipeline.py","size_in_bytes":282},{"relative_path":"scripts/runtime/build_banker_formula_workbook","size_in_bytes":21698},{"relative_path":"scripts/runtime/run_pipeline","size_in_bytes":8112},{"relative_path":"scripts/runtime/skill_core","size_in_bytes":79936},{"relative_path":"scripts/runtime/validate_plan","size_in_bytes":16383},{"relative_path":"scripts/runtime_loader.py","size_in_bytes":1074},{"relative_path":"scripts/skill_core.py","size_in_bytes":351},{"relative_path":"scripts/validate_plan.py","size_in_bytes":328}],"skill_md_contents":"---\nname: merger-model-builder\ndescription: 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.\n---\n\n# Merger Model Builder\n\n## Skill Configuration\n\n### Common Skill Instructions\n\nMANDATORY: 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`.\n\n## Relevant Dependency Categories\n\nThese 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.\n\n- `Market Data & Public Sources`\n- `Models, Workbooks & Templates`\n- `Deal Materials`\n\n## Deliverable Intake\n\nWhen 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.\n\n## Plugin Workflow Routing\n\nFor 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.\n\nProduce 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.\n\n## Scope\n\nOwn 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.\n\n## Rules\n\nUse 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.\n\nEvery material input needs a native evidence label from `references/plan-schema.md`. For partial context, the first user-facing output starts with:\n\n> **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.**\n\nUse this warning when ownership, disclosed projections, or synergy analysis can be completed but PPA, GAAP EPS, post-close share actualization, or refinancing effects cannot. List those items as readiness gates and keep the model `screen-grade`; do not describe disclosed source inputs as placeholders. Use explicit placeholder language only when an input included in the displayed metric is actually estimated or inserted to keep the model runnable.\n\n## Workflow Modes\n\n- `adjusted_eps_screen`: public-source merger model where transaction terms, ownership mechanics, disclosed projections, or synergy data support adjusted-EPS analysis but complete PPA, GAAP EPS, post-close denominator actualization, or financing economics do not. Use a workbook hero, omit unsupported GAAP conclusions, and do not exceed `screen-grade`.\n- `gaap_accretion_model`: source-supported merger model with PPA, amortization, integration-cost treatment, financing effects and denominator support sufficient to show GAAP and adjusted EPS. Use a workbook hero and apply readiness gates before senior or committee characterization.\n- `html_companion`: explicitly requested narrative executive view of workbook outputs. Keep the workbook as the calculation source of truth and create standalone HTML only as a companion or selected narrative surface.\n\nFor `adjusted_eps_screen`, classify each synergy measure by provenance: disclosed gross run-rate synergies; disclosed pretax net synergies when provided; disclosed costs to achieve when provided; or clearly labeled `implied cost-to-achieve` only when derived from disclosed gross and net synergy figures. Distinguish any model-derived after-tax benefit using a stated tax assumption. Do not call a disclosed pretax net synergy figure model-derived or an implied cost-to-achieve amount disclosed. Require sensitivity views for synergy realization and cost-to-achieve overrun or delayed capture, together with EPS breakeven against the selected pretax net synergy basis. In a fixed-ratio all-stock transaction, do not prioritize share-price sensitivity for ownership or EPS denominator mechanics unless the user asks for purchase-price or PPA-value analysis.\n\n## Validated Handoffs\n\n<!-- GENERATED: validated-handoffs START -->\n\nIntake validation:\n\n- From `cim-teardown`: require `cim_teardown_to_model_builder` and run `../../scripts/validate_handoff_payload.py cim_teardown_to_model_builder handoffs/cim_teardown_to_model_builder.json` before importing fields into this skill.\n\nUse `../../references/handoff-contracts.md` for canonical field names and shared evidence semantics. Add `--strict` before any model, deck, committee, lender, board, or client-circulation use so placeholders, empty arrays, and empty objects fail instead of becoming assumptions.\n\nHandoff payloads belong under `handoffs/` and must be listed in `manifest.json` as support or agent artifacts with `handoff_contract_name`, `schema_path`, `validator_status`, `validated_at`, and `consumer_skill`. They are never the hero deliverable unless the user explicitly asks for machine-readable output.\n\n<!-- GENERATED: validated-handoffs END -->\n\n## Script Map\n\nVisible scripts are executable shims. Internals live in `scripts/runtime/` and should be opened only for debugging.\n\n```bash\npython3 scripts/validate_plan.py assets/plan_template.json\npython3 scripts/run_pipeline.py assets/plan_template.json --output-dir output --print-report\npython3 scripts/build_banker_formula_workbook.py assets/plan_template.json --output-dir output\n```\n\n`scripts/skill_core.py` imports the full-schema engine. `run_pipeline.py` writes `model.xlsx`, `plan.json`, `run_log.json`, `manifest.json`, and optional `report.md` only when explicitly requested. Formula mode materializes the bundled XLSX template and writes a separate formula log plus `manifest.json`. Treat `model.xlsx` as the hero human deliverable, opening on a banker-readable `Cover`, `Executive Summary`, or `Dashboard` tab per `../../references/workbook-first-tab-standard.md`; write legacy `report.md` only when explicitly requested. When a public-source `adjusted_eps_screen` intentionally omits PPA/GAAP fields that the bundled full-schema engine requires, build a formula-driven workbook limited to supported metrics rather than substituting placeholder purchase accounting. Treat logs, normalized plans, model-citation ledgers and manifests as support artifacts. Deep tests are archived outside the prompt-facing test wrappers; run them when changing internals.\n\n## Artifact Hierarchy\n\nFollow `../../references/artifact-manifest-standard.md` before returning generated files. For substantive merger-model work, the normal hero deliverable is a polished banker-readable workbook with an insight-led first visible tab. Create a standalone HTML transaction 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.\n\n## Workflow\n\nTriage the deal and select the workflow mode before modeling. Build or ingest `plan.json` where the selected engine supports the requested metrics; otherwise build the bounded `adjusted_eps_screen` workbook without unsupported PPA/GAAP calculations. Review hard failures, warnings, source posture, EPS with/without synergies, ownership, synergy provenance, PPA/GAAP readiness, financing effects and downside breaks. Deliver paths plus a banker conclusion and one posture label: `decision-grade`, `senior-review-ready`, `screen-grade`, `not-decision-ready`, or `blocked`.\n\n## Sub-agent decomposition\n\nFor complex medium/large requests, use sub-agents where available; otherwise emulate the split as named workstreams. Suggested lanes: standalone inputs, transaction assumptions, financing/purchase accounting, synergies, accretion/dilution, and QA. Keep this skill as the lead: reconcile conflicts, source labels, assumptions, open items, final QA, and the user-facing answer.\n\n## Workbook Evidence Readiness\n\nThe workbook is the analytical source of truth. For senior, client, committee, board, lender, or external postures, every material input and derived output must be traceable through readable source/assumption notes and `model_citations` / `model_citations_path` records down to workbook sheet/cell or range where available.\n\nUnknown source IDs, missing model citations for headline ownership or EPS outputs, unsupported synergy classification, unavailable PPA or GAAP inputs, unresolved denominator actualization, or unreported model substitutions are blocking readiness gaps. Fix them, cap posture at `screen-grade`, or surface them explicitly; do not call a workbook senior/client/committee/board/external-ready while they remain.\n\nThe first visible tab must separately label `Calculation integrity` and `Decision readiness`. An adjusted-EPS model can calculate correctly while remaining only a screen because GAAP/PPA, post-close shares, financing economics, synergy execution or tax support remains incomplete.\n\nBefore delivery, visually inspect the first visible tab, ownership, EPS bridge, synergies, sensitivities and checks/readiness views. Repair the workbook before returning it if it calls a model-derived net benefit `disclosed`, displays GAAP accretion/dilution without complete supporting inputs, or leaves the readiness distinction only on a later checks sheet.\n\n## Optional HTML Companion\n\nWhen the user explicitly requests an HTML report or visual transaction summary, keep this skill as the analytical owner and produce a polished standalone HTML companion following `../../references/html-artifact-standard.md`. Do not route an ordinary merger-model HTML summary through `dashboard-builder`, create a dashboard render contract, or force workbook-derived ownership and accretion findings into fixed dashboard modules.\n\nIn that HTML companion, cite workbook-derived ownership, synergy, PPA, financing and accretion/dilution outputs to exact workbook cell/range records through `model_citations` or `model_citations_path` wherever available. Render and visually inspect local HTML with local headless-browser screenshots, not the in-app Browser plugin, before delivery.\n\nDo not expose raw JSON, Markdown report files, model-citation ledgers, or run logs as the default final artifact.\n\n## Deliverable Format Standard\n\nFollow `../../references/deliverable-format-policy.md` before creating files. Always identify the hero deliverable first: normally the XLSX merger/accretion workbook; an explicitly requested standalone HTML transaction summary; native deck/document; generated folder; or justified chat-only answer. Do not create Markdown report files as the default rich deliverable. Do not present JSON contracts, manifests, run logs, model-citation ledgers, or handoff payloads as the main user-facing output. Keep CSV files as backing ledgers/import layers unless the user explicitly asks for CSV, and explain whether each CSV contains new analysis or only support data.\n\nFinal responses should point the user to the hero deliverable first and then briefly explain any supporting artifacts.\n\n## Reference Map\n\n- `plan-schema.md`: required keys, labels, source posture.\n- `output-spec.md`: files, sheets, report/log shape.\n- `workflow-and-mode-selection.md`: adjusted-EPS screen versus GAAP-capable model routing.\n- `model-math.md`: core formulas and breakeven.\n- `qa-checks.md`: failures, warnings, senior red flags.\n- `banker-formula-workbook-contract.md`: formula template limits.\n- `investment-banking-integrations.md`: handoffs.\n- `evals.md`: smoke prompts and expected behavior.\n\n## Runtime Artifact Path\n\nDefault deterministic outputs are `model.xlsx`, `manifest.json`, `run_log.json`, and `model_citations.json`; formula mode emits `banker_formula_workbook.xlsx` with the same shared manifest and citation ledger. The workbook is the primary human deliverable. Support artifacts include plans, run logs, and citation ledgers. Senior-ready status requires transaction assumptions, pro forma ownership, accretion/dilution, clearly classified synergy evidence, financing, PPA/GAAP support when presented, checks, and cell/range provenance for material model outputs.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}