Menu

Individual skill

deal-workbench-review

0upvotes

How to review M&A deal documents using the deal workbench API. Use when the task involves reviewing purchase agreements, producing issue registers, preparing closing packages, compiling committee escalation memos, conducting transition reviews, or building deviation matrices against a deal workbench. Applies to buyer-side or seller-side APA/SPA reviews, playbook comparisons, policy threshold checks, and any structured M&A deal analysis where the task provides an answer_template.json payload and references a running deal workbench at a TASK_ENV_BASE_URL.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_020/fewshot/opencode/fewshot_attempt_01/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

# Deal Workbench Review

This skill teaches a systematic method for completing M&A deal review tasks against the deal workbench API. The core pattern is: read the template first, gather all deal data from the workbench, compare draft terms against playbook rules or policy thresholds, compute dollar amounts from the headline purchase price, and produce JSON that conforms exactly to the provided answer template.

## Key Principle

The task always provides an `answer_template.json` payload. This is your contract for output shape. Read it first and treat every field, enum, and constraint in it as non-negotiable. The workbench API provides the facts; the template defines what shape those facts must take.

## Connecting to the Workbench

[Credential-related source omitted]

The primary API surface for a deal `DEAL_ID` consists of these endpoints:
Back to top