Menu

Individual skill

deal-workbench-ma-json

0upvotes

Produce schema-conformant JSON for M&A deal workbench review tasks. Use when a prompt provides a deal_id and answer_template.json and asks for APA/SPA issue registers, closing and economics packages, committee policy escalation packages, transition reviews, deviation matrices, or similar legal/commercial analyses using deal APIs, playbooks, policies, terms, benchmarks, risk estimates, cap tables, consents, employees, material contracts, regulatory records, diligence findings, documents, and notes.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/fewshot_attempt_03/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

# Deal Workbench M&A JSON

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` before querying data. Extract the deal ID, client side, transaction type, requested work product, applicable playbook or policy ID, required rounding, required ordering, allowed enums, and every required output field.
2. Read `environment_access.md` for the base URL, query token, and allowed endpoints. Use only that workbench environment for network access.
3. Fetch records for the exact deal ID. Do not use records from similarly named projects.
4. Compare current draft terms against the applicable playbook rules or policy thresholds. Treat absent protective terms as issues when the prompt, playbook, policy, or surrounding deal data makes the term required.
5. Build the answer directly against the template. Preserve required keys, enum spellings, nulls, empty arrays, source ID fields, and requested ordering.
6. Validate that the final response is valid JSON and contains no narrative outside the JSON object.

## Data Collection

Use the helper when available:
Back to top