Individual skill
ma-deal-workbench
Prepare schema-exact JSON work products from an M&A deal workbench. Use when Codex is asked to review APA/SPA terms, seller or buyer playbooks, committee policy thresholds, closing conditions, economics, transition packages, consents, regulatory facts, diligence findings, benchmarks, risks, notes, or related deal records and return only JSON conforming to a provided answer_template.json.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/fewshot_attempt_01/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
- productivity Derived category
- productivity-notes 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
# M&A Deal Workbench JSON
## Core Workflow
1. Read the user prompt and the provided `input/payloads/answer_template.json` before querying data. Extract:
- deal ID, project name, client side, counterparty, work product type, and applicable playbook or policy ID;
- required units, rounding, enum values, stable issue IDs, ordering rules, and required top-level fields;
- whether the task asks for all issues, only escalations, only transition issues, closing readiness, economics, or a deviation matrix.
2. Reach the running workbench only through the base URL supplied by the task or environment access file. Prefer the documented JSON APIs over the UI. Query all relevant records for the requested work product, commonly:
- `GET /api/deals/<deal_id>`
- `GET /api/deals/<deal_id>/terms`
- `GET /api/playbooks/<playbook_id>/rules` or `GET /api/policies/<policy_id>/thresholds`
- `GET /api/deals/<deal_id>/risk-estimates`