Guide · Agent skill
How to use the M&A Integration Tracker agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The M&A Integration Tracker is an agent skill, a set of instructions that an AI assistant such as Claude loads so it can do a specific job. This one, named integration-management, handles the legal side of a company acquisition after closing: a phased workplan, a consent tracker, contract assignment sorting, and weekly status reports. This guide explains what the skill does, how to install it, how to ask for it in plain language, and what to check before relying on its output.
M&A Integration Trackeranthropics/claude-for-legal · Apache-2.0 Download the skill Quick start
- 1Download and unzip the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
- 2Set up the deal folder. Create or confirm the deal folder under ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/ with the deal code. The skill will create deal-context.md if it is missing.
- 3Provide deal documents. Share the purchase agreement, closing checklist, deal summary or a plain-language description of the deal so the skill has inputs to work from.
- 4Initialize the tracker. Ask for the tracker to be initialized for the deal, or run --init. The skill builds the phased workplan and consent tracker.
- 5Import and tier contracts. Provide the contract list from a repository or upload, then run --contracts so the skill sorts each contract into a tier.
- 6Review deadlines against the purchase agreement. Check every date and consent the skill extracted against the source documents before relying on them.
- 7Generate reports and export. Use --report for weekly status and --export with --format csv or table to share sections of the tracker.
What the integration-management skill does
Once installed, the agent acts as a program manager for the legal workstreams of a deal after it closes. The source describes it as the program management layer for post-closing integration. It covers consents, contract assignments, entity rationalization, IP recordals and purchase agreement obligations, and it tracks what is done, what is due, what is blocked and what needs a decision.
It is not for business, IT or HR integration planning. The skill explicitly excludes those workstreams.
- Builds a phased workplan with Day 1, Day 30, Day 90 and Day 180 targets
- Keeps a tracker of required and desired third-party consents
- Sorts a company's contracts into tiers by how they must be assigned or consented to
- Generates weekly status reports
- Exports the tracker to CSV or as a table
- Reads deal documents such as the purchase agreement and closing checklist when they are available
- Saves the tracker as a YAML file in a local folder on your machine
Install the skill in Claude
Download the skill's ZIP file from this page. The skill is a single file, SKILL.md. Unzip it into one of these locations: ~/.claude/skills/ to make it available to you across projects, or the .claude/skills/ folder inside a specific project to limit it to that project.
If you use the Claude apps instead, you can upload the skill under Settings, then Capabilities, then Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills, then upload
~/.claude/skills/Prepare the deal folder and documents
The skill stores its work per deal, under a folder named after the deal code. It reads deal-context.md from that folder for the deal code, target company, close date, deal lead and outside counsel. If deal-context.md is missing, the skill asks for those details and creates the file.
If a closing-checklist.yaml file exists in the same folder, the skill inherits any post-closing items from it. For the best starting tracker, make the purchase agreement available. The source says its Required Consents schedule and post-closing covenants are the authoritative source for hard deadlines. If you only have a deal summary, a to-do list or a plain-language description of the deal, the skill can still build a starter tracker that you then edit.
- Purchase agreement: gives the most complete tracker, including Required Consents and deadlines
- Deal summary or term sheet: key economics and timeline
- Closing checklist or post-close to-do list from outside counsel
- Contract list from a repository or a disclosure schedule
- Plain-language description of the deal if nothing is written down
~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/deal-context.mdTrigger the skill with natural requests
You do not have to memorize the flags. The skill's description lists phrases that activate it, so you can ask in ordinary language. Phrases in the skill description include 'integration', 'post-close', 'post-closing', 'consents outstanding', 'contract assignment', 'integration status' and 'what's left on the deal'.
The flags map to modes: --init builds the workplan and consent tracker, --contracts imports and tiers the contract list, --report generates a status report, --update records a manual change or parses an uploaded status document, and --export writes CSV or a table. Export accepts --format csv or table and --section all, consents, contracts or workplan. --deal selects a deal code.
- 'Initialize the integration tracker for deal ACME from the purchase agreement.'
- 'What consents are still outstanding?'
- 'Import the contract list and tier the contracts by assignment mechanism.'
- 'Give me this week's integration status.'
- 'Export the consents section as a CSV.'
/corporate-legal:integration-management --export --format csv --section consents --deal ACMEUnderstand the tracker it creates
The tracker lives in integration-tracker.yaml inside the deal folder. Its main parts are metadata, pa_dates (such as the required consents deadline, rep survival expiry, escrow release and earn-out milestones), a workplan split into four phases, a list of required and desired consents, and contracts sorted into tiers 1 to 4.
Each workplan item has an ID, owner, workstream, priority, deadline, deadline basis, status and any blocker. Each consent entry has a counterparty, whether it is required, its status and any deadline. The skill shows a summary of changes after every write and flags anything new that needs attention.
- Contract tiers: 1 = Required Consent, 2 = material and consent-required, 3 = change of control, 4 = auto-assign
- Workplan statuses include not_started, in_progress, complete, blocked and deferred
- Consent statuses include not_started, outreach_sent, in_negotiation, obtained, waived and refused
Safety, privacy and limits
According to the skill's listing, it runs no scripts and uses no network connection. It works by reading the documents you provide and writing its tracker and reports to local files. Deal documents stay on the machine where you run the skill, as far as the skill itself is concerned. Check your own tool's data handling separately if you upload documents to a hosted app.
The skill extracts deadlines from documents, so every date it reports must be verified against the purchase agreement by the lawyer responsible. Treat the tracker as a working aid, not as a record of legal obligations.
- No scripts are run and no network access is used, per the listing
- Writes files only to the deal folder under ~/.claude/plugins/config/claude-for-legal/
- If a matter workspace is enabled, outputs go to that matter's folder instead
- Deadlines and consent status must be checked against the source documents
Tips for getting better results
Give the skill the purchase agreement early, because the Required Consents schedule and post-closing covenants produce the firmest deadlines. Run --contracts once you have a complete contract list so the tiers are set before outreach begins. Use --report on a regular schedule and --update after calls or emails so the tracker reflects reality.
Keep the deal code consistent, because the skill reads and writes files by that code. Export a CSV when you need to share the consent list with colleagues who do not use the skill.
- Provide the purchase agreement or Required Consents list first
- Import the contract list before starting consent outreach
- Update statuses after every meaningful conversation with a counterparty
- Use --export for shareable copies of any section
What people use it for
- Tracking which required consents named in the purchase agreement are still outstanding after closing
- Sorting a large contract portfolio by whether each contract auto-assigns, needs consent or is triggered by a change of control
- Producing a weekly status report for the deal lead on legal workstreams
- Building a Day 1, Day 30, Day 90 and Day 180 workplan for outside counsel handoff
- Exporting the consent list as CSV for a legal operations team
Frequently asked questions
Is the M&A integration-management skill free?
The source material for this page does not state pricing or licence terms beyond the licence listed as Apache-2.0. Check the licence file in the repository for the terms that apply to the code.
What do I need to use the integration-management skill?
You need the Claude for Legal corporate-legal configuration folder with deal-context.md, which the skill creates if missing. You also need access to deal documents such as the purchase agreement, closing checklist or contract repository.
How do I install the integration-management skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.
Does the skill run scripts or use the internet?
According to the listing, it runs no scripts and uses no network. It reads the documents you provide and writes its tracker to local files.
Can the skill replace a lawyer reviewing the purchase agreement?
No. The skill extracts deadlines from documents, and the lawyer must verify them against the purchase agreement. It is a program management aid for legal workstreams after closing.
Does it cover business, IT or HR integration?
No. The skill is limited to legal workstreams such as consents, contract assignments, entity rationalization, IP recordals and purchase agreement obligations. It explicitly excludes business, IT and HR integration planning.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are in-house or outside counsel managing legal workstreams after an M&A deal closes, or a legal ops team that needs a consistent tracker for consents and contract assignments across many contracts. Pick something else if you need business, IT or HR integration planning, or if you want a tool to replace reading the purchase agreement yourself.
Download the skill