Menu

Individual skill

ma-deal-workbench-json

0upvotes

Solve M&A deal workbench tasks that require schema-exact JSON outputs from deal APIs, playbooks, policies, diligence, consents, regulatory, employee, benchmark, risk, and draft-term records.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/naive/fewshot_attempt_02/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 Solver

Use this skill when the user asks for an M&A legal or deal-team package based on a running deal workbench and an `answer_template.json`.

## Core workflow

1. Read the prompt and `input/payloads/answer_template.json` first.
2. Extract the deal ID, client side, requested package type, playbook or policy ID, required endpoints, units, rounding rules, allowed enums, stable IDs, and ordering instructions from the prompt/template.
3. Fetch only records for the requested deal. Do not assume similarly named projects apply.
4. Build the answer from current workbench records, not from memory. Return only valid JSON conforming to the template.

Useful endpoint patterns are:

- `GET /api/deals/<deal_id>`
Back to top