{"kind":"Skill","metadata":{"namespace":"community","name":"lbo-model","version":"0.1.0"},"spec":{"description":"This skill should be used when completing LBO (Leveraged Buyout) model templates in Excel for private equity transactions, deal materials, or investment committee presentations. The skill fills in formulas, validates calculations, and ensures professional formatting standards that adapt to any template structure.","files":{"SKILL.md":"---\nname: lbo-model\ndescription: This skill should be used when completing LBO (Leveraged Buyout) model templates in Excel for private equity transactions, deal materials, or investment committee presentations. The skill fills in formulas, validates calculations, and ensures professional formatting standards that adapt to any template structure.\n---\n\n---\n\n## TEMPLATE REQUIREMENT\n\n**This skill uses templates for LBO models. Always check for an attached template file first.**\n\nBefore starting any LBO model:\n1. **If a template file is attached/provided**: Use that template's structure exactly - copy it and populate with the user's data\n2. **If no template is attached**: Ask the user: *\"Do you have a specific LBO template you'd like me to use? If not, I can use the standard template which includes Sources \u0026 Uses, Operating Model, Debt Schedule, and Returns Analysis.\"*\n3. **If using the standard template**: Copy `examples/LBO_Model.xlsx` as your starting point and populate it with the user's assumptions\n\n**IMPORTANT**: When a file like `LBO_Model.xlsx` is attached, you MUST use it as your template - do not build from scratch. Even if the template seems complex or has more features than needed, copy it and adapt it to the user's requirements. Never decide to \"build from scratch\" when a template is provided.\n\n---\n\n## CRITICAL INSTRUCTIONS FOR CLAUDE - READ FIRST\n\n### Environment: Office JS vs Python\n\n**If running inside Excel (Office Add-in / Office JS environment):**\n- Use Office JS (`Excel.run(async (context) =\u003e {...})`) directly — do NOT use Python/openpyxl\n- Write formulas via `range.formulas = [[\"=B5*B6\"]]` — Office JS formulas recalculate natively in the live workbook\n- The same formulas-over-hardcodes rule applies: set `range.formulas`, never `range.values` for anything that should be a calculation\n- Use `range.format.font.color` / `range.format.fill.color` for the blue/black/purple/green convention\n- No separate recalc step needed — Excel handles calculation natively\n- **Merged cell pitfall:** Do NOT call `.merge()` then set `.values` on the merged range (throws `InvalidArgument` — range still reports original dimensions). Instead: write value to top-left cell alone (`ws.getRange(\"A7\").values = [[\"SOURCES \u0026 USES\"]]`), then merge + format the full range (`ws.getRange(\"A7:F7\").merge(); ws.getRange(\"A7:F7\").format.fill.color = \"#1F4E79\";`)\n\n**If generating a standalone .xlsx file (no live Excel session):**\n- Use Python/openpyxl as described below\n- Write formula strings (`ws[\"D20\"] = \"=B5*B6\"`), then run `recalc.py` before delivery\n\nThe rest of this skill is written with openpyxl examples, but the same principles apply to Office JS — just translate the API calls.\n\n### Core Principles\n* **Every calculation must be an Excel formula** - NEVER compute values in Python and hardcode results into cells. When using openpyxl, write `cell.value = \"=B5*B6\"` (formula string), NOT `cell.value = 1250` (computed result). The model must be dynamic and update when inputs change.\n* **Use the template structure** - Follow the organization in `examples/LBO_Model.xlsx` or the user's provided template. Do not invent your own layout.\n* **Use proper cell references** - All formulas should reference the appropriate cells. Never type numbers that should come from other cells.\n* **Maintain sign convention consistency** - Follow whatever sign convention the template uses (some use negative for outflows, some use positive). Be consistent throughout.\n* **Work section by section, verify with user at each step** - Complete one section fully, show the user what was built, run the section's verification checks, and get confirmation BEFORE moving to the next section. Do NOT build the entire model end-to-end and then present it — later sections depend on earlier ones, so catching a mistake in Sources \u0026 Uses after the returns are already built means rework everywhere.\n\n### Formula Color Conventions\n* **Blue (0000FF)**: Hardcoded inputs - typed numbers that don't reference other cells\n* **Black (000000)**: Formulas with calculations - any formula using operators or functions (`=B4*B5`, `=SUM()`, `=-MAX(0,B4)`)\n* **Purple (800080)**: Links to cells on the **same tab** - direct references with no calculation (`=B9`, `=B45`)\n* **Green (008000)**: Links to cells on **different tabs** - cross-sheet references (`=Assumptions!B5`, `='Operating Model'!C10`)\n\n### Fill Color Palette — Professional Blues \u0026 Greys (Default unless user/template specifies otherwise)\n* **Keep it minimal** — only use blues and greys for cell fills. Do NOT introduce greens, yellows, reds, or multiple accents. A professional LBO model uses restraint.\n* **Default fill palette:**\n  * **Section headers** (Sources \u0026 Uses, Operating Model, etc.): Dark blue `#1F4E79` with white bold text\n  * **Column headers** (Year 1, Year 2, etc.): Light blue `#D9E1F2` with black bold text\n  * **Input cells**: Light grey `#F2F2F2` (or just white) — the blue *font* is the signal, fill is secondary\n  * **Formula/calculated cells**: White, no fill\n  * **Key outputs** (IRR, MOIC, Exit Equity): Medium blue `#BDD7EE` with black bold text\n* **That's the whole palette.** 3 blues + 1 grey + white. If the template uses its own colors, follow the template instead.\n* Note: The blue/black/purple/green **font** colors above are for distinguishing inputs vs formulas vs links. Those are separate from the **fill** palette here — both work together.\n\n### Number Formatting Standards\n* **Currency**: `$#,##0;($#,##0);\"-\"` or `$#,##0.0` depending on template\n* **Percentages**: `0.0%` (one decimal)\n* **Multiples**: `0.0\"x\"` (one decimal)\n* **MOIC/Detailed Ratios**: `0.00\"x\"` (two decimals for precision)\n* **All numeric cells**: Right-aligned\n\n---\n\n### Clarify Requirements First\n\nBefore filling any formulas:\n\n* **Examine the template structure** - Identify all sections, understand the timeline (which columns are which periods), note any existing formulas\n* **Ask the user if anything is unclear** - If the template structure, calculation methods, or requirements are ambiguous, ask before proceeding\n* **Confirm key assumptions** - Any key inputs, calculation preferences, or specific requirements\n* **ONLY AFTER understanding the template**, proceed to fill in formulas\n\n---\n\n## TEMPLATE ANALYSIS PHASE - DO THIS FIRST\n\nBefore filling any formulas, examine the template thoroughly:\n\n1. **Map the structure** - Identify where each section lives and how they relate to each other. Note which sections feed into others.\n\n2. **Understand the timeline** - Which columns represent which periods? Is there a \"Closing\" or \"Pro Forma\" column? Where does the projection period start?\n\n3. **Identify input vs formula cells** - Templates often use color coding, borders, or shading to indicate which cells need inputs vs formulas. Respect these conventions.\n\n4. **Read existing labels carefully** - The row labels tell you exactly what calculation is expected. Don't assume - read what the template is asking for.\n\n5. **Check for existing formulas** - Some templates come partially filled. Don't overwrite working formulas unless specifically asked.\n\n6. **Note template-specific conventions** - Sign conventions, subtotal structures, how sections are organized, whether there are separate tabs for different components, etc.\n\n---\n\n## FILLING FORMULAS - GENERAL APPROACH\n\nFor each cell that needs a formula, follow this hierarchy:\n\n### Step 1: Check the Template\n* Does the cell already have a formula? If yes, verify it's correct and move on.\n* Is there a comment or note indicating the expected calculation?\n* Does the row/column label make the calculation obvious?\n* Do neighboring cells show a pattern you should follow?\n\n### Step 2: Check the User's Instructions\n* Did the user specify a particular calculation method?\n* Are there stated assumptions that affect this formula?\n* Any special requirements mentioned?\n\n### Step 3: Apply Standard Practice\n* If neither template nor user specifies, use standard LBO modeling conventions\n* Document any assumptions you make\n* If genuinely uncertain, ask the user\n\n---\n\n## COMMON PROBLEM AREAS\n\nThe following calculation patterns frequently cause issues across LBO models. Pay special attention when you encounter these:\n\n### Balancing Sections\n* When two sections must equal (e.g., Sources = Uses), one item is typically the \"plug\" (balancing figure)\n* Identify which item is the plug and calculate it as the difference\n\n### Tax Calculations\n* Tax formulas should only reference the relevant income line and tax rate\n* Should NOT reference unrelated sections (e.g., debt schedules)\n* Consider whether losses create tax shields or are simply ignored\n\n### Interest and Circular References\n* Interest calculations can create circularity if they reference balances affected by cash flows\n* Use **Beginning Balance** (not average or ending) to break circular references\n* Pattern: Interest → Cash Flow → Paydown → Ending Balance (if interest uses ending balance, this circles back)\n\n### Debt Paydown / Cash Sweeps\n* When multiple debt tranches exist, there's usually a priority order\n* Cash sweep should respect the priority waterfall\n* Balances cannot go negative - use MAX or MIN functions appropriately\n\n### Returns Calculations (IRR/MOIC)\n* Cash flows must have correct signs: Investment = negative, Proceeds = positive\n* If using XIRR, need corresponding dates\n* If using IRR, cash flows should be in consecutive periods\n* MOIC = Total Proceeds / Total Investment\n\n### Sensitivity Tables\n* **Use ODD dimensions** (5×5 or 7×7) — never 4×4 or 6×6. Odd dimensions guarantee a true center cell.\n* **Center cell = base case.** Build the row and column axis values symmetrically around the model's actual assumptions (e.g., if base entry multiple = 10.0x, axis = `[8.0x, 9.0x, 10.0x, 11.0x, 12.0x]`). The center cell's IRR/MOIC MUST then equal the model's actual IRR/MOIC output — this is the proof the table is wired correctly.\n* **Highlight the center cell** — medium-blue fill (`#BDD7EE`) + bold font so the base case is visually anchored.\n* Excel's DATA TABLE function may not work with openpyxl — instead write explicit formulas that reference row/column headers\n* Each cell should show a DIFFERENT value — if all same, formulas aren't varying correctly\n* Use mixed references (e.g., `$A5` for row input, `B$4` for column input)\n\n---\n\n## VERIFICATION CHECKLIST - RUN AFTER COMPLETION\n\n### Run Formula Validation\n```bash\npython /mnt/skills/public/xlsx/recalc.py model.xlsx\n```\nMust return success with zero errors.\n\n### Section Balancing\n- [ ] Any sections that must balance (Sources/Uses, Assets/Liabilities) balance exactly\n- [ ] Plug items are calculated correctly as the balancing figure\n- [ ] Amounts that should match across sections are consistent\n\n### Income/Operating Projections\n- [ ] Revenue/top-line builds correctly from drivers or growth rates\n- [ ] All cost and expense items calculated appropriately\n- [ ] Subtotals and totals sum correctly\n- [ ] Margins and ratios are reasonable\n- [ ] Links to assumptions are correct\n\n### Balance Sheet (if applicable)\n- [ ] Assets = Liabilities + Equity (must balance)\n- [ ] All items link to appropriate schedules or roll-forwards\n- [ ] Beginning balances = prior period ending balances\n- [ ] Check row included and shows zero\n\n### Cash Flow (if applicable)\n- [ ] Starts with correct income figure\n- [ ] Non-cash items added/subtracted appropriately\n- [ ] Working capital changes have correct signs\n- [ ] Ending Cash = Beginning Cash + Net Cash Flow\n- [ ] Cash balances are consistent across statements\n\n### Supporting Schedules\n- [ ] Roll-forward schedules balance (Beginning + Changes = Ending)\n- [ ] Schedules link correctly to main statements\n- [ ] Calculated items use appropriate drivers\n- [ ] All periods are calculated consistently\n\n### Debt/Financing Schedules (if applicable)\n- [ ] Beginning balances tie to sources or prior period\n- [ ] Interest calculated on appropriate balance (typically beginning)\n- [ ] Paydowns respect cash availability and priority\n- [ ] Ending balances cannot be negative\n- [ ] Totals sum tranches correctly\n\n### Returns/Output Analysis\n- [ ] Exit/terminal values calculated correctly\n- [ ] All relevant adjustments included\n- [ ] Cash flow signs are correct (negative for investment, positive for proceeds)\n- [ ] IRR/MOIC formulas reference complete ranges\n- [ ] Results are reasonable for the scenario\n\n### Sensitivity Tables (if applicable)\n- [ ] Grid dimensions are ODD (5×5 or 7×7) — there is a true center cell\n- [ ] Row and column axis values are symmetric around the base case (`[base-2Δ, base-Δ, base, base+Δ, base+2Δ]`)\n- [ ] Center cell output equals the model's actual IRR/MOIC — confirms the table is wired correctly\n- [ ] Center cell is highlighted (medium-blue fill `#BDD7EE`, bold font)\n- [ ] Row and column headers contain appropriate input values\n- [ ] Each data cell contains a formula (not hardcoded)\n- [ ] Each data cell shows a DIFFERENT value\n- [ ] Values move in expected directions (higher exit multiple → higher IRR, etc.)\n\n### Formatting\n- [ ] Hardcoded inputs are blue (0000FF)\n- [ ] Calculated formulas are black (000000)\n- [ ] Same-tab links are purple (800080)\n- [ ] Cross-tab links are green (008000)\n- [ ] All numbers are right-aligned\n- [ ] Appropriate number formats applied throughout\n- [ ] No cells show error values (#REF!, #DIV/0!, #VALUE!, #NAME?)\n\n### Logical Sanity Checks\n- [ ] Numbers are reasonable order of magnitude\n- [ ] Trends make sense (growth, decline, stabilization as expected)\n- [ ] No obviously wrong values (negative where should be positive, impossible percentages, etc.)\n- [ ] Key outputs are within reasonable ranges for the type of analysis\n\n---\n\n## COMMON ERRORS TO AVOID\n\n| Error | What Goes Wrong | How to Fix |\n|-------|-----------------|------------|\n| Hardcoding calculated values | Model doesn't update when inputs change | Always use formulas that reference source cells |\n| Wrong cell references after copying | Formulas point to wrong cells | Verify all links, use appropriate $ anchoring |\n| Circular reference errors | Model can't calculate | Use beginning balances for interest-type calcs, break the circle |\n| Sections don't balance | Totals that should match don't | Ensure one item is the plug (calculated as difference) |\n| Negative balances where impossible | Paying/using more than available | Use MAX(0, ...) or MIN functions appropriately |\n| IRR/return errors | Wrong signs or incomplete ranges | Check cash flow signs and ensure formula covers all periods |\n| Sensitivity table shows same value | Formula not varying with inputs | Check cell references - need mixed references ($A5, B$4) |\n| Roll-forwards don't tie | Beginning ≠ prior ending | Verify links between periods |\n| Inconsistent sign conventions | Additions become subtractions or vice versa | Follow template's convention consistently throughout |\n\n---\n\n## WORKING WITH THE USER — SECTION-BY-SECTION CHECKPOINTS\n\n* **If the template structure is unclear**, ask before proceeding\n* **If the user's requirements conflict with the template**, confirm their preference\n* **After completing each major section**, STOP and verify with the user before continuing:\n  - **After Sources \u0026 Uses** → show the balanced table, confirm the plug is correct, get sign-off before building the operating model\n  - **After Operating Model / Projections** → show the projected P\u0026L, confirm growth rates and margins look right, get sign-off before the debt schedule\n  - **After Debt Schedule** → show beginning/ending balances and interest, confirm the waterfall logic, get sign-off before returns\n  - **After Returns (IRR/MOIC)** → show the cash flow series and outputs, confirm signs and ranges, get sign-off before sensitivity tables\n  - **After Sensitivity Tables** → show that each cell varies, confirm the base case lands where expected\n* **If errors are found during verification**, fix them before moving to the next section\n* **Show your work** - explain key formulas or assumptions when helpful\n* **Never present a completed model without having checked in at each section** — it's faster to catch a wrong cell reference at the source than to trace it backwards from a broken IRR\n\n---\n\n**This skill produces investment banking-quality LBO models by filling templates with correct formulas, proper formatting, and validated calculations. The skill adapts to any template structure while ensuring financial accuracy and professional presentation standards.**\n"},"import":{"commit_sha":"9affc6e683bbaf66361058117027cf5a50bf1861","imported_at":"2026-05-18T20:09:40Z","license_text":"\n                                 Apache License\n                           Version 2.0, January 2004\n                        http://www.apache.org/licenses/\n\n   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n   1. Definitions.\n\n      \"License\" shall mean the terms and conditions for use, reproduction,\n      and distribution as defined by Sections 1 through 9 of this document.\n\n      \"Licensor\" shall mean the copyright owner or entity authorized by\n      the copyright owner that is granting the License.\n\n      \"Legal Entity\" shall mean the union of the acting entity and all\n      other entities that control, are controlled by, or are under common\n      control with that entity. For the purposes of this definition,\n      \"control\" means (i) the power, direct or indirect, to cause the\n      direction or management of such entity, whether by contract or\n      otherwise, or (ii) ownership of fifty percent (50%) or more of the\n      outstanding shares, or (iii) beneficial ownership of such entity.\n\n      \"You\" (or \"Your\") shall mean an individual or Legal Entity\n      exercising permissions granted by this License.\n\n      \"Source\" form shall mean the preferred form for making modifications,\n      including but not limited to software source code, documentation\n      source, and configuration files.\n\n      \"Object\" form shall mean any form resulting from mechanical\n      transformation or translation of a Source form, including but\n      not limited to compiled object code, generated documentation,\n      and conversions to other media types.\n\n      \"Work\" shall mean the work of authorship, whether in Source or\n      Object form, made available under the License, as indicated by a\n      copyright notice that is included in or attached to the work\n      (an example is provided in the Appendix below).\n\n      \"Derivative Works\" shall mean any work, whether in Source or Object\n      form, that is based on (or derived from) the Work and for which the\n      editorial revisions, annotations, elaborations, or other modifications\n      represent, as a whole, an original work of authorship. For the purposes\n      of this License, Derivative Works shall not include works that remain\n      separable from, or merely link (or bind by name) to the interfaces of,\n      the Work and Derivative Works thereof.\n\n      \"Contribution\" shall mean any work of authorship, including\n      the original version of the Work and any modifications or additions\n      to that Work or Derivative Works thereof, that is intentionally\n      submitted to Licensor for inclusion in the Work by the copyright owner\n      or by an individual or Legal Entity authorized to submit on behalf of\n      the copyright owner. For the purposes of this definition, \"submitted\"\n      means any form of electronic, verbal, or written communication sent\n      to the Licensor or its representatives, including but not limited to\n      communication on electronic mailing lists, source code control systems,\n      and issue tracking systems that are managed by, or on behalf of, the\n      Licensor for the purpose of discussing and improving the Work, but\n      excluding communication that is conspicuously marked or otherwise\n      designated in writing by the copyright owner as \"Not a Contribution.\"\n\n      \"Contributor\" shall mean Licensor and any individual or Legal Entity\n      on behalf of whom a Contribution has been received by Licensor and\n      subsequently incorporated within the Work.\n\n   2. Grant of Copyright License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      copyright license to reproduce, prepare Derivative Works of,\n      publicly display, publicly perform, sublicense, and distribute the\n      Work and such Derivative Works in Source or Object form.\n\n   3. Grant of Patent License. Subject to the terms and conditions of\n      this License, each Contributor hereby grants to You a perpetual,\n      worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n      (except as stated in this section) patent license to make, have made,\n      use, offer to sell, sell, import, and otherwise transfer the Work,\n      where such license applies only to those patent claims licensable\n      by such Contributor that are necessarily infringed by their\n      Contribution(s) alone or by combination of their Contribution(s)\n      with the Work to which such Contribution(s) was submitted. If You\n      institute patent litigation against any entity (including a\n      cross-claim or counterclaim in a lawsuit) alleging that the Work\n      or a Contribution incorporated within the Work constitutes direct\n      or contributory patent infringement, then any patent licenses\n      granted to You under this License for that Work shall terminate\n      as of the date such litigation is filed.\n\n   4. Redistribution. You may reproduce and distribute copies of the\n      Work or Derivative Works thereof in any medium, with or without\n      modifications, and in Source or Object form, provided that You\n      meet the following conditions:\n\n      (a) You must give any other recipients of the Work or\n          Derivative Works a copy of this License; and\n\n      (b) You must cause any modified files to carry prominent notices\n          stating that You changed the files; and\n\n      (c) You must retain, in the Source form of any Derivative Works\n          that You distribute, all copyright, patent, trademark, and\n          attribution notices from the Source form of the Work,\n          excluding those notices that do not pertain to any part of\n          the Derivative Works; and\n\n      (d) If the Work includes a \"NOTICE\" text file as part of its\n          distribution, then any Derivative Works that You distribute must\n          include a readable copy of the attribution notices contained\n          within such NOTICE file, excluding those notices that do not\n          pertain to any part of the Derivative Works, in at least one\n          of the following places: within a NOTICE text file distributed\n          as part of the Derivative Works; within the Source form or\n          documentation, if provided along with the Derivative Works; or,\n          within a display generated by the Derivative Works, if and\n          wherever such third-party notices normally appear. The contents\n          of the NOTICE file are for informational purposes only and\n          do not modify the License. You may add Your own attribution\n          notices within Derivative Works that You distribute, alongside\n          or as an addendum to the NOTICE text from the Work, provided\n          that such additional attribution notices cannot be construed\n          as modifying the License.\n\n      You may add Your own copyright statement to Your modifications and\n      may provide additional or different license terms and conditions\n      for use, reproduction, or distribution of Your modifications, or\n      for any such Derivative Works as a whole, provided Your use,\n      reproduction, and distribution of the Work otherwise complies with\n      the conditions stated in this License.\n\n   5. Submission of Contributions. Unless You explicitly state otherwise,\n      any Contribution intentionally submitted for inclusion in the Work\n      by You to the Licensor shall be under the terms and conditions of\n      this License, without any additional terms or conditions.\n      Notwithstanding the above, nothing herein shall supersede or modify\n      the terms of any separate license agreement you may have executed\n      with Licensor regarding such Contributions.\n\n   6. Trademarks. This License does not grant permission to use the trade\n      names, trademarks, service marks, or product names of the Licensor,\n      except as required for reasonable and customary use in describing the\n      origin of the Work and reproducing the content of the NOTICE file.\n\n   7. Disclaimer of Warranty. Unless required by applicable law or\n      agreed to in writing, Licensor provides the Work (and each\n      Contributor provides its Contributions) on an \"AS IS\" BASIS,\n      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n      implied, including, without limitation, any warranties or conditions\n      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n      PARTICULAR PURPOSE. You are solely responsible for determining the\n      appropriateness of using or redistributing the Work and assume any\n      risks associated with Your exercise of permissions under this License.\n\n   8. Limitation of Liability. In no event and under no legal theory,\n      whether in tort (including negligence), contract, or otherwise,\n      unless required by applicable law (such as deliberate and grossly\n      negligent acts) or agreed to in writing, shall any Contributor be\n      liable to You for damages, including any direct, indirect, special,\n      incidental, or consequential damages of any character arising as a\n      result of this License or out of the use or inability to use the\n      Work (including but not limited to damages for loss of goodwill,\n      work stoppage, computer failure or malfunction, or any and all\n      other commercial damages or losses), even if such Contributor\n      has been advised of the possibility of such damages.\n\n   9. Accepting Warranty or Additional Liability. While redistributing\n      the Work or Derivative Works thereof, You may choose to offer,\n      and charge a fee for, acceptance of support, warranty, indemnity,\n      or other liability obligations and/or rights consistent with this\n      License. However, in accepting such obligations, You may act only\n      on Your own behalf and on Your sole responsibility, not on behalf\n      of any other Contributor, and only if You agree to indemnify,\n      defend, and hold each Contributor harmless for any liability\n      incurred by, or claims asserted against, such Contributor by reason\n      of your accepting any such warranty or additional liability.\n\n   END OF TERMS AND CONDITIONS\n\n   APPENDIX: How to apply the Apache License to your work.\n\n      To apply the Apache License to your work, attach the following\n      boilerplate notice, with the fields enclosed by brackets \"[]\"\n      replaced with your own identifying information. (Don't include\n      the brackets!)  The text should be enclosed in the appropriate\n      comment syntax for the file format. We also recommend that a\n      file or class name and description of purpose be included on the\n      same \"printed page\" as the copyright notice for easier\n      identification within third-party archives.\n\n   Copyright [yyyy] [name of copyright owner]\n\n   Licensed under the Apache License, Version 2.0 (the \"License\");\n   you may not use this file except in compliance with the License.\n   You may obtain a copy of the License at\n\n       http://www.apache.org/licenses/LICENSE-2.0\n\n   Unless required by applicable law or agreed to in writing, software\n   distributed under the License is distributed on an \"AS IS\" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n   See the License for the specific language governing permissions and\n   limitations under the License.\n","owner":"anthropics","repo":"anthropics/financial-services","source_url":"https://github.com/anthropics/financial-services/tree/9affc6e683bbaf66361058117027cf5a50bf1861/plugins/agent-plugins/model-builder/skills/lbo-model"}},"content_hash":[45,121,89,211,100,0,105,47,1,243,86,1,193,103,238,254,158,73,18,11,214,132,206,140,1,93,17,98,191,214,245,231],"trust_level":"unsigned","yanked":false}