Individual skill
ma-workbench-json-deliverables
Produce structured JSON legal work product (issue registers, deviation matrices, committee escalation memos, closing/transition packages) from a read-only M&A deal workbench containing deal records, draft terms, playbook rules, policy thresholds, benchmarks, risk estimates, cap tables, consents, employees, material contracts, regulatory records, diligence findings, notes, and documents. Use whenever a prompt names a deal ID, points at a deal workbench, and requires an answer conforming to a supplied answer template.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_020/reflect-3/reflect-3_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
- legal Derived category
- productivity Derived category
- productivity-notes 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 · 6,413 bytesSKILL.mdcore · 6,413 bytesreferences/derivation-rules.mddoc · 5,440 bytesreferences/record-model.mddoc · 6,206 bytesscripts/check_answer.pyruns · 7,935 bytes
Read excerpt
# M&A workbench → structured JSON deliverables
These tasks look like legal drafting but are graded like data extraction. The grader
compares your JSON field-by-field against a reference answer and awards partial credit
per field. Prose quality earns nothing; a wrong number, a missing row, or an invented
record ID loses a point each. Optimize for **every scalar traceable to a record**.
## Non-negotiables
1. **Return only the JSON object.** No prose, no markdown fences, no commentary.
2. **The answer template is the contract.** Reproduce its exact key names, nesting, and
spelling. Never rename, never add top-level keys, never drop a field.
3. **Never invent a record ID.** Every ID you emit must appear verbatim in the workbench
(or be an explicitly synthetic ID that the template itself authorizes).