Menu

Individual skill

ma-deal-workbench-review

0upvotes

Produce a structured-JSON M&A legal-review deliverable (issue register, closing/economics package, committee escalation memo, carveout transition review, or deviation matrix) from the running M&A deal workbench, strictly conforming to a provided answer_template.json. Use when acting as buyer- or seller-side counsel on a PRJ_* deal/project and told to return only JSON.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_020/fewshot/fewshot_attempt_02/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

# M&A Deal Workbench Review

## When to use this skill

Use this skill when a task asks you to act as **buyer- or seller-side transaction counsel** for a specific M&A deal/project and produce a **structured JSON** deliverable by querying the running **M&A deal workbench**. Recognize the family by these signals:

- A deal/project ID such as `PRJ_…`, a named client and target/counterparty, and a side (buyer or seller).
- An instruction to use the workbench at `<TASK_ENV_BASE_URL>` (web UI + REST APIs), often with a read-only SQL endpoint and a token.
- An `answer_template.json` (under `input/payloads/`) that defines the exact output schema, plus an instruction like "return only JSON" / "do not include narrative outside the JSON".

If the task does not point to the deal workbench or does not provide an answer template, do not use this skill.

The deliverable type varies (issue register, closing/economics package, committee escalation memo, carveout transition review, SPA deviation matrix). The shape is always dictated by **the answer_template.json in front of you** — see `references/deliverable_patterns.md` for the recurring patterns.
Back to top