Individual skill
ma-deal-workbench-json
Produce structured JSON deal-review deliverables (issue registers, deviation matrices, closing packages, committee escalation memos, transition reviews) from the M&A deal workbench API. Use whenever a task names a deal_id like PRJ_*, points at a deal workbench base URL, and requires returning only JSON conforming to a supplied answer_template.json.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_020/self/self_attempt_02/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
- 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 · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesSKILL.mdcore · 10,764 bytesreference/field_semantics.mddoc · 7,545 bytesreference/workbench_api.mddoc · 6,066 bytesscripts/extract_contract.pyruns · 4,218 bytesscripts/validate_answer.pyruns · 7,463 bytesscripts/wb.pyruns · 6,983 bytes
Read excerpt
# M&A Deal Workbench → structured JSON
A family of tasks share one shape: you are counsel for one side of one deal, you
read that deal's records from a workbench API, you compare the current draft
against a playbook or policy, and you emit **one JSON object conforming to a
supplied `answer_template.json`** with no prose around it.
The deliverable name changes (issue register, deviation matrix, closing package,
committee escalation memo, transition review). The method below does not.
## The single most important rule
**The answer template is the specification. The prompt is context.**
