Individual skill

ma-deal-workbench-json

Analyze M&A deal workbench records and draft APA, SPA, merger, carveout, or committee terms against buyer, seller, or committee playbooks/policies, then return schema-conforming JSON issue registers, closing packages, transition reviews, escalation memos, or deviation matrices. Use when a task mentions TASK_ENV_BASE_URL, deal workbench APIs, deal IDs, playbook or policy thresholds, indemnity, escrow, survival, consents, HSR, employees, material contracts, or M&A legal JSON outputs.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/cc/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# M&A Deal Workbench JSON

Use this skill to solve M&A workbench tasks that require a structured legal/commercial JSON deliverable. Treat the user's `input/payloads/answer_template.json` as the output contract.

## Core Workflow

1. Read the prompt and the answer template before fetching data.
2. Extract the deal ID, client side, deal type, required playbook or committee policy, output units, enum values, required ordering, and any explicit exclusions.
3. Replace `<TASK_ENV_BASE_URL>` with the task environment base URL and fetch all records needed for the requested sections.
4. Build a source map keyed by stable IDs from every record: draft terms, playbook or policy rules, deal economics, consents, regulatory records, employees, cap table, material contracts, diligence findings, risk estimates, benchmarks, documents, and notes.
5. Compare only current draft terms and required missing provisions against the applicable client playbook or committee policy.
6. Fill the exact JSON template. Use stable workbench IDs, required enums, integer dollar amounts, requested percent precision, integer month values, `null` for not applicable scalar fields, and empty arrays for no applicable list items.
7. Validate the final response as parseable JSON with no prose outside the JSON object.
Back to top