Menu

Individual skill

deal-workbench

0upvotes

Prepare structured M&A deliverables — issue registers, economics packages, committee escalation memos, transition reviews, and deviation matrices — from a deal workbench API. Use when the user asks for M&A work, deal analysis, contract/term comparison against a playbook or policy, closing readiness assessment, indemnity/escrow/survival review, regulatory (HSR) checks, employee continuity analysis, or any structured deliverable tied to a deal workbench. Use whenever the prompt mentions a deal ID, playbook, policy thresholds, committee escalation, APA/SPA terms, or asks you to produce a JSON deliverable from deal data.

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

Prepare structured M&A deliverables using a deal workbench REST API and optional read-only SQL.

## Workflow

Follow this sequence, adapting to the specific deliverable type requested:

### Phase 1: Orient

1. **Read the answer template** — the prompt always includes `input/payloads/answer_template.json`. Read it first. It defines the exact output schema, stable enums, stable field IDs, and data type conventions. Everything you produce must fit this shape exactly.

2. **Identify the deliverable type** from the template and prompt. Common types:
   - **Issue register**: compare draft terms against a playbook (seller or buyer), produce ranked issues with quantified deltas and summary metrics.
Back to top