Individual skill
deal-workbench-ma-review
Prepare strict JSON M&A legal review outputs from a running deal workbench. Use when a task asks Codex to act as buyer-side, seller-side, or committee M&A counsel, gather deal/workbench records over the provided API, compare draft acquisition terms against playbooks or policy thresholds, quantify deviations, identify closing blockers or missing required provisions, and return an answer conforming exactly to a supplied JSON template.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/fewshot_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
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
# Deal Workbench M&A Review
Use this skill to complete M&A deal-workbench tasks that require a structured JSON legal package rather than prose.
## Required Inputs
- The user prompt, especially the client side, deal ID, requested work product, rounding rules, and named playbook or policy.
- The task's `input/payloads/answer_template.json`; treat it as the output contract.
- The environment access file for the base URL, allowed endpoints, and SQL token if available.
Do not infer facts from similarly named projects or previous examples. Use only records for the requested deal ID.
## Collect The Workbench Bundle
