Individual skill

ma-deal-workbench-json

Produce structured JSON M&A deal-workbench outputs for APA, SPA, carveout, closing-readiness, deviation-matrix, seller or buyer issue-register, and M&A Committee escalation tasks. Use when a prompt provides a deal ID, a workbench API/base URL, playbook or policy records, and an answer_template.json that must be filled from deal evidence without narrative prose.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/self/self_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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
engineering 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 · 9,313 bytes
SKILL.mdcore · 9,313 bytes
SKILL.mdcore · 9,313 bytes

Read excerpt


# M&A Deal Workbench JSON

## Core Workflow

1. Read the user prompt and the referenced `answer_template.json` before querying data. Treat the template as the output contract: required keys, enum strings, stable issue IDs, rounding rules, sort order, and placeholder meanings come from the template.
2. Extract the exact `deal_id`, client side, transaction type, requested work product, and any named playbook or policy. Use the exact `deal_id` for every record lookup; ignore similarly named projects.
3. Read `environment_access.md` if present. Use only the base URL, token, and endpoints allowed there. Do not use outside network sources.
4. Fetch `/api/deals/<deal_id>` first, then follow its links or fetch the relevant standard endpoints:
   - `/terms`
   - `/documents`
   - `/benchmarks`
   - `/risk-estimates`
   - `/cap-table`
   - `/consents`