Due Diligence

Structure and run a deal diligence process: a request list by workstream, a findings tracker with severity and owner, and a red-flag log tied to deal terms.

⚠️ **Finance warning / Avertissement finance** : informational only, not investment advice. A diligence process reduces surprises, it does not eliminate them: findings depend on what the data room actually contains and on the access you are given, and a clean tracker is not a guarantee that a target is sound or that a deal will perform. Curated by Skill Harbor: the due diligence skill of the investment banking pack in andreworia/claude-finance-skills. Use it the moment a deal moves past a signed letter of intent or a data room opens, on buy-side confirmatory diligence or sell-side vendor diligence, when a vague do-diligence instruction has to become an organized, owner-assigned process. The method runs in eight steps. It frames the scope first (deal type, sector, materiality thresholds, and the investment thesis to prove or disprove), with an explicit warning that an unbounded request list stalls the process, so every ask is anchored to a thesis question. It builds the request list across seven workstreams (commercial, financial, legal, tax, operational, HR and IT), prioritizes quality of earnings inside the financial workstream (revenue recognition, non-recurring items, working-capital trends, normalized EBITDA with a clean add-back bridge, watching for aggressive capitalization or channel stuffing), and covers contracts and change-of-control clauses, litigation, IP ownership, open tax positions, key-person dependencies and IT integration debt across the other streams. Every request gets a single named owner, never a team, a due date and a tracked status. Findings are logged as documents arrive with workstream, severity rated by deal impact rather than effort, potential deal impact (price, structure, walk-away), owner and status, and high-severity items escalate to a red-flag log with a one-line thesis on why the item threatens value and a recommended mitigation such as a price adjustment, an escrow, an indemnity or a condition to close. The summary maps each material issue to a purchase-agreement or valuation action. The worked example in the file is fictional and illustrative. From the andreworia/claude-finance-skills repository (MIT). Honest caveats: this skill organizes a process and its paperwork in prose; it does not access any data room itself, and it is not legal, tax or accounting advice. Skill Harbor never reviews the code, review it yourself before use.

At a glance

What: Structure and run a deal diligence process: a request list by workstream, a findings tracker with severity and owner, and a red-flag log tied to deal terms.
Cost: Free
Needs: Use "Due Diligence" 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 diligence process reduces surprises, it does not eliminate them: findings depend on what the data room actually contains and on the access you are given, and a clean tracker is not a guarantee that a target is sound or that a deal will perform. Curated by Skill Harbor: the due diligence skill of the investment banking pack in andreworia/claude-finance-skills. Use it the moment a deal moves past a signed letter of intent or a data room opens, on buy-side confirmatory diligence or sell-side vendor diligence, when a vague do-diligence instruction has to become an organized, owner-assigned process. The method runs in eight steps. It frames the scope first (deal type, sector, materiality thresholds, and the investment thesis to prove or disprove), with an explicit warning that an unbounded request list stalls the process, so every ask is anchored to a thesis question. It builds the request list across seven workstreams (commercial, financial, legal, tax, operational, HR and IT), prioritizes quality of earnings inside the financial workstream (revenue recognition, non-recurring items, working-capital trends, normalized EBITDA with a clean add-back bridge, watching for aggressive capitalization or channel stuffing), and covers contracts and change-of-control clauses, litigation, IP ownership, open tax positions, key-person dependencies and IT integration debt across the other streams. Every request gets a single named owner, never a team, a due date and a tracked status. Findings are logged as documents arrive with workstream, severity rated by deal impact rather than effort, potential deal impact (price, structure, walk-away), owner and status, and high-severity items escalate to a red-flag log with a one-line thesis on why the item threatens value and a recommended mitigation such as a price adjustment, an escrow, an indemnity or a condition to close. The summary maps each material issue to a purchase-agreement or valuation action. The worked example in the file is fictional and illustrative. From the andreworia/claude-finance-skills repository (MIT). Honest caveats: this skill organizes a process and its paperwork in prose; it does not access any data room itself, and it is not legal, tax or accounting advice. Skill Harbor never reviews the code, review it yourself before use.

Version:

a

Created by: andreworia

Not verified? How to check before you trust →

Install — Free · open source (MIT) View source code

⌁

Install

Copy the install package below, then paste it into Muse

Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

After installation, ask me if I want to leave private feedback
Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

Use "Due Diligence" with your Muse. Prerequisites: the deal type (buy-side or vendor) and target sector, the investment thesis to prove or disprove, data room access or at least a document index, materiality thresholds and the diligence timeline, the names of workstream owners, and the purchase agreement stage so findings can be routed to terms. This skill organizes the process, it does not open the data room for you, and it is not legal, tax or accounting advice. Informational only, not investment advice. 1. Open the skill: https://github.com/andreworia/claude-finance-skills/blob/main/packs/investment-banking/skills/due-diligence/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Frame the diligence: build the request list by workstream with one named owner and a status per item, set up the findings tracker, and start the red-flag log with the escalation rule." 3. Anchor every request to a thesis question before sending the list; an unbounded list stalls the process and buries the items that matter. Tip: rate severity by deal impact, not by effort; a small dollar item carrying a legal walk-away trigger is high severity. Safety: a skill is plain-text instructions; it runs nothing by itself. Process organization and analysis only, no orders and no account access. Informational only, not investment advice.

?

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.