Individual skill

ma-deal-workbench-json

Solve M&A deal workbench tasks that require strict JSON outputs for APA, SPA, merger, carveout, closing-readiness, issue-register, deviation-matrix, committee-escalation, consent, employee, indemnity, escrow, tax, regulatory, and transition-review analyses. Use when a prompt references an M&A deal workbench, deal APIs, playbooks, policies, draft terms, benchmarks, risk estimates, or an answer_template.json schema.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/opencode/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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 turn a deal-workbench prompt and answer template into one valid JSON answer. Work from the live deal records and the prompt's schema; do not rely on memorized example outputs.

## Start

1. Read the user prompt and `input/payloads/answer_template.json` before fetching data.
2. Extract the `deal_id`, client side, transaction type, named playbook or policy, requested categories, required ordering, units, precision, and enum spellings.
3. Resolve `<TASK_ENV_BASE_URL>` from the prompt or environment. If it is not explicit, try `TASK_ENV_BASE_URL`, then `http://task-env:9020/`.
4. Fetch the deal bundle. From this skill directory, run:

```bash
python scripts/fetch_workbench.py DEAL_ID --base-url "$TASK_ENV_BASE_URL" --output /tmp/deal_bundle.json
```