CIM Teardown
Turn a 60 to 120 page CIM into a structured brief: seller claims tracked against evidence, the EBITDA bridge rebuilt, and diligence priorities ordered.
- What
- Turn a 60 to 120 page CIM into a structured brief: seller claims tracked against evidence, the EBITDA bridge rebuilt, and diligence priorities ordered.
- Cost
- Free
- Needs
- Use "CIM Teardown" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
⚠️ **Finance warning / Avertissement finance** : informational only, not investment advice. A CIM is a seller marketing document: its claims are assertions until diligence proves them, private equity carries a real risk of loss, and no teardown here is a promise of return. Curated by Skill Harbor: the CIM teardown skill of the private equity pack in andreworia/claude-finance-skills. Use it after receiving a full CIM from a sell-side advisor and before the first internal deal team meeting; the output is the briefing document for management meetings and workstream kickoffs, and the starting point for the DDQ and the diligence architecture. The method extracts the deal overview without interpretation (business, history, employees, products, customers, geographies, ownership, process type, stated financials and valuation parameters), states the seller investment thesis as three to five pillars, each quoted near-verbatim with a note on whether the CIM supports it with data or merely asserts it and a confidence level, and decomposes the business model (revenue streams and their growth, pricing model, go-to-market, revenue recognition, stated retention and churn), flagging missing retention data as a critical diligence question. It rebuilds the EBITDA bridge from revenue through gross margin and operating expenses to stated EBITDA, categorises every add-back as clearly one-time, recurring but reclassified, or needing quality of earnings scrutiny, and lists the three to five normalisation items most likely to be challenged, with the estimated EBITDA impact if they are rejected. A management assertions tracker pairs every quantified claim with the evidence actually provided, and risks are split into risks the CIM acknowledges, risks it downplays or omits, and structural risks such as carve-out complexity or a secondary buyout where the prior sponsor already took the easy value. It ends with an ordered list of the top ten diligence questions, each with a workstream owner, the data required, and the risk if unanswered, prioritised by pass potential and by weakness of the CIM evidence. From the andreworia/claude-finance-skills repository (MIT). Honest caveats: the teardown is only as good as the CIM text you paste, and seller figures, retention rates and market claims must be verified by you against primary data in diligence. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "CIM Teardown" with your Muse. Prerequisites: the full CIM text (paste the executive summary and key sections, or provide the document), your fund sector and return parameters so good can be calibrated, and any screening note already prepared to avoid duplication. No account and no credentials are involved: this skill produces a teardown memo only, and every seller figure in it is an assertion to verify in diligence. Informational only, not investment advice. 1. Open the skill: https://github.com/andreworia/claude-finance-skills/blob/main/packs/private-equity/skills/cim-teardown/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Tear down this CIM: extract the deal overview without editorialising, state each thesis pillar with its evidence and confidence, rebuild the EBITDA bridge and categorise every add-back, build the management assertions tracker, split the risks into acknowledged, downplayed and structural, and give me the top ten diligence questions with owners and data needed." 3. Check the assertions tracker before the team meeting: any headline claim with thin evidence belongs at the top of the diligence list, not in the thesis. Tip: do the extraction pass first and keep it verbatim; interpretation added at extraction quietly becomes assumed fact for the whole team. Safety: a skill is plain-text instructions; it runs nothing by itself. Analysis and documents only, no orders and no account access. Informational only, not investment advice.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.