Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Post Deal Monitoring

ASecurity

Builds a post-close tracker of synergy realization, integration milestones, and value creation against the deal thesis once a transaction has closed.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill post-deal-monitoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Post Deal Monitoring?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Post Deal Monitoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-post-deal-monitoring/badge)](https://www.skillsdirectory.com/skills/andreworia-post-deal-monitoring)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: post-deal-monitoring
description: Builds a post-close tracker of synergy realization, integration milestones, and value creation against the deal thesis once a transaction has closed.
---

# Post-Deal Monitoring Agent

## When to use
Use this agent when the deal is closed and value must be tracked: in the first weeks after close to stand up a monitoring framework, or at each subsequent review to check whether the transaction is delivering what was underwritten. It is for the value-capture phase, after signing and close are done. Run it on a fixed cadence so drift is caught early enough to correct.

## What it does
Produces a post-close tracker of synergies, integration milestones, and value creation measured against the deal thesis, so the team can see early whether the acquisition is on plan and where it is drifting.

## Method
1. Restate the deal thesis.
   - Capture the value drivers underwritten at close, the synergy target, and the return the base case assumed.
   - This is the yardstick; everything downstream is measured against it.

2. Break synergies into cost and revenue categories.
   - Give each category a target amount, an expected timing profile, and an owner.
   - Separate cost synergies, which land faster, from revenue synergies, which land slower and less certainly.

3. Track synergy realization against target.
   - Record actual run-rate achieved, percent of target captured, and any one-time cost to achieve incurred so far.
   - Run-rate, not cumulative savings, is the honest measure of where you are.

4. Track integration milestones.
   - Cover systems, org design, key retention, and customer transition, each with a status and a due date.
   - Flag any milestone that has slipped, since integration delays quietly erode synergies.

5. Compare value creation to the deal thesis.
   - Ask whether the combined business is hitting the revenue, margin, and cash targets that justified the price.

6. Recompute a current return view where possible.
   - Update the MOIC or IRR path against what was underwritten so the gap is quantified, not just described.

7. Flag variances with an owner and a date.
   - Where realization lags target, name the cause and the corrective action, and assign it.

8. Set a review cadence and a retirement point.
   - Monthly early, then quarterly, and note when the tracker can be retired as integration completes.

## Inputs
- The deal thesis, synergy target, and underwritten return
- The integration plan with milestones and owners
- Actual post-close operating results to date
- One-time integration and restructuring costs incurred
- Retention status of key people named in the thesis
- The current review date and the next scheduled review

## Output format
Claude returns a tracker in these sections:
- Synergies: each category in prose with target, realized run-rate, percent captured, cost to achieve, and owner.
- Integration milestones: each milestone with status, due date, and a flag if slipped.
- Value versus thesis: actual revenue, margin, and cash against the underwritten case, with an updated return view.
- Variances: each gap with its cause, corrective action, owner, and date.
- Summary: whether the deal is on, ahead of, or behind plan, and the next review date.
Any table is described in prose, not rendered as markdown.

## Example
Twelve weeks after Meridian Foods closed its bakery acquisition: the thesis underwrote fifteen million in annual synergies and a base-case MOIC of 2.1x. Cost synergies, target ten million, run-rate of six million captured (sixty percent), driven by procurement consolidation, with two million of cost to achieve incurred; owner the integration lead. Revenue synergies, target five million from cross-selling, run-rate of one million (twenty percent), behind plan. Integration milestones: ERP migration on track for quarter three; head baker retained; two regional customers not yet transitioned, flagged as slipped. Value versus thesis: revenue in line, gross margin fifty basis points below plan on input costs; updated MOIC path near 1.9x. Corrective action: accelerate the cross-sell pilot, owner the commercial lead, review in four weeks. Overall: slightly behind plan, driven by revenue synergy timing, with the next full review scheduled at the six-month mark.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →