LBO Model Builder
Build, validate, and professionally format leveraged buyout models in Excel templates.
The skill requires using the user’s template first, staged user confirmation, transparent formulas, and human review; repository context also provides read-only CI permissions, an Apache-2.0 license, and a risk disclaimer. Deductions apply because sensitive financial-data handling, least-privilege boundaries, data-flow disclosure, rollback, and external-side-effect controls are not specified, while command and file-operation dependencies lack security boundaries.
The Office JS and openpyxl paths, template-analysis process, formula rules, and validation checklist are broadly self-consistent. Deductions apply because availability of `/mnt/skills/public/xlsx/recalc.py` is not established in the skill, abnormal-input handling and failure feedback are thin, and no key-path test suite is provided; static review caps this at 10.
The target scenario, template-first behavior, Excel/standalone-xlsx environments, and major LBO modules are clearly described, with instructions to ask when requirements are unclear. Deductions apply because non-fit scenarios, formal input/output contracts, practical availability of the referenced standard template, Chinese-language support, and mainland-China environment fit are not addressed.
The document has clear layering, install prerequisites, formatting conventions, common errors, verification checks, and user checkpoints; repository context supplies Apache-2.0 licensing, official provenance, CI, and contribution/update guidance. Deductions apply because the skill itself lacks a version, changelog, named maintainer, FAQ, and explicit dependency-install instructions, and the referenced example template is not directly verified by the supplied files.
The skill covers Sources & Uses, operating projections, debt, returns, sensitivities, and formatting, so it plausibly completes template-based dynamic LBO workbook construction. Deductions apply because no representative output or execution evidence is supplied, and results still require staged user confirmation and professional review; static review caps this at 7.
The source provides concrete formula, cell-color, and validation requirements, while repository CI performs plugin validation and secret scanning, giving some auditability. Deductions apply because CI does not test LBO calculation correctness and there is no committed test workbook, execution log, or third-party reproduction evidence; static review caps this at 5.
- No scripts or Excel recalculation were executed; the checklist must not be treated as proof of financial correctness.
- The referenced standard template and recalc.py path are not confirmed by the supplied evidence and should be validated before deployment.
- The skill does not define storage, transmission, redaction, or access controls for sensitive transaction data; those controls should be added before using real deal materials.
- The instructions are primarily English, with no demonstrated Chinese-language or mainland-China environment support.
What does this skill do, and when should you use it?
This skill completes LBO models for private-equity transactions, deal materials, and investment-committee presentations. It first checks whether the user supplied a template and preserves that template’s structure. Without one, it asks whether to use the standard template containing Sources & Uses, Operating Model, Debt Schedule, and Returns Analysis. It also covers formula validation, section checkpoints, sensitivity analysis, and professional financial-model formatting.
Checks for an attached or supplied LBO template; maps sections, periods, input cells, and existing formulas; writes dynamic Excel formulas instead of hardcoded calculations; populates Sources & Uses, operating projections, debt schedules, returns analysis, and sensitivity tables; handles sign conventions, circularity, debt-paydown priority, and non-negative balances; uses Office JS inside Excel or Python/openpyxl for standalone work; runs recalc.py for formula validation and checks balances, formatting, error values, and logical reasonableness.
- A private-equity professional needs transaction assumptions entered into an existing LBO workbook.
- An investment-banking or deal team needs an IC-ready model covering financing, projections, and exit returns.
- A model reviewer needs to validate Sources & Uses, debt balances, interest, IRR, or MOIC calculations.
- A financial analyst needs a 5×5 or 7×7 LBO sensitivity table centered on the base case.
What are this skill's strengths and limitations?
- Emphasizes dynamic formulas, correct cell references, and consistent sign conventions.
- Addresses common LBO failure points including debt paydown, interest circularity, IRR/MOIC, balancing checks, and sensitivity tables.
- Defines font colors for inputs, formulas, same-sheet links, and cross-sheet links, plus a restrained blue-and-grey fill palette.
- Requires staged user confirmation and post-completion formula, formatting, and logic checks.
- It is template-oriented; the source does not establish that it can design any LBO layout from scratch.
- The source provides no test suite, sample validation output, or platform compatibility test results.
- Formula validation depends on `/mnt/skills/public/xlsx/recalc.py`, whose availability in every environment is not documented.
- The source does not specify the transaction data, assumptions, or external data sources required for a model.
How do you install this skill?
In Cowork, open Settings → Plugins → Add plugin, paste https://github.com/anthropics/financial-services, and select the relevant plugin. In Claude Code, the supported commands include: claude plugin marketplace add anthropics/financial-services and claude plugin install financial-analysis@claude-for-financial-services. The source does not document a standalone installation command for this individual skill.
How do you use this skill?
Trigger the skill with /lbo and provide the LBO template and transaction assumptions. When a template is supplied, the skill should copy and preserve its structure; otherwise it asks whether to use the standard template. Work is expected to proceed section by section—Sources & Uses, operating model, debt schedule, returns, and sensitivities—with user confirmation and verification at each major checkpoint.