Individual skill

ma-deal-workbench-review

Analyze M&A deal workbench tasks that require counsel-side JSON outputs using TASK_ENV_BASE_URL/API records, playbooks or policies, issue matrices, closing packages, committee escalations, transition reviews, consents, employees, regulatory records, benchmarks, risk estimates, and schema-conformant answer_template.json responses.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/codex/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

## Core Workflow

Use this skill when a task asks for buyer-side or seller-side counsel analysis from an M&A deal workbench and requires JSON matching an `answer_template.json`.

1. Read the prompt and `input/payloads/answer_template.json` first. Extract the deal ID, client side, deal type, requested package type, applicable playbook or policy IDs, required ordering, units, enum values, and whether in-policy terms should be included or excluded.
2. Collect deal records from `TASK_ENV_BASE_URL` using the routes named in the prompt. A helper is available:

   ```bash
   python skill/scripts/fetch_workbench.py "$TASK_ENV_BASE_URL" "$DEAL_ID" --playbook-id "$PLAYBOOK_ID" --policy-id "$POLICY_ID" --output workbench_records.json
   ```

   Omit unknown optional IDs. Use direct API calls for any prompt-specific endpoint not covered by the helper.