Menu

Individual skill

ma-deal-workbench-json

0upvotes

Use when solving M&A deal workbench tasks that require fetching deal records, comparing APA or SPA draft terms to buyer or seller playbooks or committee policy, calculating deal economics, and returning strict JSON issue registers, deviation matrices, closing packages, or committee escalations.

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

# M&A Deal Workbench JSON

Use this skill for M&A workbench tasks where the prompt provides a deal ID, a task environment base URL, an answer template, and asks for JSON only.

## Core Rules

- The prompt and the task's answer template are the output contract. Match field names, nesting, enum strings, nullability, ordering instructions, units, and rounding exactly.
- Treat the deal ID, client side, applicable playbook or policy, and endpoint list in the prompt as authoritative. Do not use records from similarly named projects.
- Fetch source records before reasoning. Do not invent source IDs, amounts, dates, holder names, or policy thresholds.
- Use stable IDs from the workbench in all source fields. For a required term missing from the draft, use an empty `source_term_ids` array unless the template asks for document, regulatory, consent, or other record IDs.
- Return only valid JSON. No narrative, Markdown, citations, or comments outside the JSON object.

## One-Pass Workflow
Back to top