Individual skill
ma-deal-workbench-json
Produce template-conformant JSON deliverables (issue registers, deviation matrices, closing packages, committee escalation memos, transition reviews) from an M&A "deal workbench" HTTP service. Use whenever a prompt casts you as buyer-side or seller-side counsel on a deal ID like PRJ_*, points at a workbench base URL with /api/deals routes, and requires output conforming to an answer_template.json with no prose outside the JSON.
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_020/self/self_attempt_03/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 · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesSKILL.mdcore · 8,745 bytesreferences/classification_rules.mddoc · 7,216 bytesreferences/output_contract.mddoc · 3,941 bytesreferences/workbench_api.mddoc · 8,097 bytesscripts/fetch_deal.shruns · 5,676 bytesscripts/validate_answer.pyruns · 17,728 bytes
Read excerpt
# M&A Deal Workbench → Structured JSON
You are counsel on one deal. A read-only workbench holds the facts; a JSON template
defines the deliverable. Your job is to reconcile the **current draft terms** against the
**standard that binds this deal** (playbook or policy), quantify the gaps against the
**correct dollar base**, and emit JSON that conforms to the template exactly.
Grading is mechanical. Prose quality earns nothing; a wrong enum case, a stale term, or an
aggregate that disagrees with your own rows costs everything.
## Five non-negotiables
1. **The template is the contract.** Key names, enum spellings, nesting, and units come
from the template — never from your judgment about what would be cleaner.