Individual skill

ma-deal-workbench-json

Use when solving M&A deal workbench tasks that require fetching deal workbench API records and returning schema-conforming JSON legal work product, including buyer or seller issue registers, SPA or APA deviation matrices, closing packages, transition reviews, and committee escalation summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/codex/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.

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

SKILL.mdcore · 2,445 bytes
SKILL.mdcore · 2,445 bytes
SKILL.mdcore · 2,445 bytes
agents/openai.yamlasset · 216 bytes
references/deal-workbench-json.mddoc · 7,112 bytes
scripts/fetch_deal_context.pyruns · 3,751 bytes

Read excerpt


# M&A Deal Workbench JSON

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` first. Extract the exact `deal_id`, client side, requested deliverable, required enums, stable IDs, rounding rules, ordering rules, and top-level JSON shape.
2. Read the environment access note for the base URL. Fetch only the named deal and directly relevant playbook or policy records. Do not browse unrelated deals.
3. Use `scripts/fetch_deal_context.py` to gather the standard workbench bundle when helpful:

```bash
python3 scripts/fetch_deal_context.py --base-url "$TASK_ENV_BASE_URL" --deal-id "$DEAL_ID" --output deal_context.json
```

Pass `--playbook-id` or `--policy-id` if the prompt names one and the deal record does not.
4. Before drafting final JSON, read [references/deal-workbench-json.md](references/deal-workbench-json.md) for field mapping, issue classification, calculation, and validation rules.