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

Deal Structuring

ASecurity

Designs a deal structure across consideration mix, earnouts, and protections, showing how each element shifts risk and value, for use when the economics and mechanics are still open.

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

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Deal Structuring?

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

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

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

Download with Pro
Files
SKILL.md
---
name: deal-structuring
description: Designs a deal structure across consideration mix, earnouts, and protections, showing how each element shifts risk and value, for use when the economics and mechanics are still open.
---

# Deal Structuring Agent

## When to use
Use this agent when the economics and mechanics of the deal are still open and both sides are trying to bridge a valuation gap or allocate risk. It is most valuable when a straight cash price will not close the deal, when future performance is uncertain, or when the buyer needs protection against what diligence could not fully resolve.

## What it does
It produces a deal structure: a designed combination of consideration mix, earnout terms, and buyer and seller protections, with an explanation of how each element shifts risk and value between the parties.

## Method
This agent designs a deal structure across consideration, earnouts, and protections.

1. Set the objective. Clarify what the structure must actually solve.
   - Name the problem: a valuation gap, uncertainty about future earnings, buyer risk from a thin diligence area, or a seller demand for certainty and speed.
   - The structure follows the problem; do not add contingent mechanics where a clean cash deal would close.

2. Design the consideration mix. Decide the split among cash, stock, and deferred or contingent consideration.
   - Cash gives the seller certainty and the buyer no upside sharing; stock shares upside and risk and aligns the seller but adds volatility; deferred consideration bridges gaps but adds credit risk for the seller.
   - Match the mix to who is more confident about the future and who most needs certainty today.

3. Design the earnout. If future performance is contested, structure a contingent payment.
   - Choose the metric (revenue, EBITDA, or a milestone), the measurement period, and the payout curve.
   - Set a cap on the maximum and a cliff or threshold below which nothing pays; revenue metrics are simple but reward top line without margin discipline, while EBITDA metrics invite disputes over cost allocation.

4. Build the protections. Assemble the buyer's downside package.
   - Combine an escrow or holdback, indemnities for breaches, the reps and warranties package, and survival periods and caps that bound the seller's exposure.

5. Allocate risk deliberately. For each element, state which party bears which risk.
   - An earnout shifts performance risk to the seller; a larger escrow shifts breach risk to the seller; a stock component shifts market risk to both; representation and warranty insurance can move breach risk off the parties entirely.

6. Address governance during any earnout period. Protect the seller's ability to hit the target.
   - Set operating covenants so the seller is not deprived of the people, budget, or control needed to earn the contingent payment while under buyer ownership.

7. Model the value under scenarios. Show the range the structure produces.
   - Give total consideration to the seller and cost to the buyer in a base, an upside, and a downside case, so both sides see the outcomes.

8. State the trade-offs and recommend. Name the recommended structure and what each side gives and gets under it.

## Inputs
- The valuation gap or the specific uncertainty the structure must bridge
- The buyer's currency: available cash, stock, and financing capacity
- The seller's priorities: certainty, upside participation, tax treatment, speed
- Diligence findings that create risk needing protection
- Any constraints on control, governance, or timing during an earnout
- The tax and accounting sensitivities of each party
- Which party is more confident about the forward performance

## Output format
Claude returns a deal structure with these sections:
- The objective: the specific problem the structure is built to solve.
- Consideration mix: the split among cash, stock, and deferred or contingent consideration, with the rationale.
- Earnout design: the metric, measurement period, payout curve, cap, and cliff.
- Protection package: escrow or holdback, indemnities, reps and warranties, and survival and caps.
- Risk allocation: for each element, which party bears which risk and how value shifts.
- Scenario values: base, upside, and downside consideration as described figures in prose, never as a table grid.
- Recommendation: the recommended structure and its trade-offs for each side.

## Example
For Northwind Logistics, the buyer values the business at 300 million and the seller wants 340 million, driven by a new contract the seller is confident will ramp. The structure bridges the gap. Consideration: 290 million cash at close plus an earnout of up to 50 million. Earnout design: paid on incremental EBITDA from the new contract over two years, with a cliff at 8 million of incremental EBITDA below which nothing pays, a linear payout above the cliff, and a 50 million cap. This shifts the ramp risk to the seller, who is the confident party. Protections: a 20 million escrow held eighteen months for indemnity claims, a full reps and warranties package with survival of eighteen months and a cap of 15 percent of price, and representation and warranty insurance to take fundamental breach risk off both sides. Governance: the seller's operating team retains control of the contract's servicing during the earnout so it can hit the target. Scenarios: base case total 320 million, upside 340 million if the contract fully ramps, downside 290 million if it does not. Recommended structure delivers the seller its number only if performance justifies it, and caps the buyer's cost if it does not.

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 →