Individual skill
ma-deal-workbench-json
Produce schema-conformant JSON deliverables (issue registers, deviation matrices, closing-readiness packages, committee escalation memos, transition reviews) from the M&A deal workbench HTTP/SQL API. Use whenever a prompt names a deal ID like PRJ_XXXX, points at a deal workbench base URL, references a playbook (PB_*) or policy (POL_*), and requires output conforming to an answer_template.json with no prose.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_020/self/self_attempt_01/SKILL.md
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
- data Derived category
- data-databases 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 · 8,611 bytesSKILL.mdcore · 8,611 bytesSKILL.mdcore · 8,611 bytesSKILL.mdcore · 8,611 bytesSKILL.mdcore · 8,611 bytesreferences/analysis-playbook.mddoc · 8,352 bytesreferences/output-contract.mddoc · 6,046 bytesreferences/workbench-api.mddoc · 7,793 bytesscripts/fetch_deal.pyruns · 6,731 bytesscripts/units.pyruns · 3,381 bytesscripts/validate_answer.pyruns · 14,769 bytes
Read excerpt
# M&A Deal Workbench → Schema-Conformant JSON
Tasks in this family all share one shape: read a deal's records from a workbench API,
compare the **current draft terms** against the **governing standard** (a playbook or a
policy), classify and quantify each deviation, and emit **one JSON object** that conforms
exactly to a supplied `answer_template.json`.
Two things fail these tasks far more often than legal judgment does:
pulling data from the **wrong deal or a stale row**, and emitting JSON that **doesn't match
the template's shape, enums, or units**. Spend your effort there.
## Operating procedure
### 1. Extract the task contract before touching the network