Menu

Individual skill

deal-workbench-analyzer

0upvotes

Analyze M&A deal records from a running deal workbench. Gather terms, playbooks, consents, contracts, employees, regulatory data, risk estimates, benchmarks, and diligence findings, then produce structured issue registers, closing-readiness assessments, escalation packages, and transition reviews.

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

When the task calls for analyzing deal records from a running M&A deal workbench
at `<TASK_ENV_BASE_URL>`, follow this skill.

## High-Level Workflow

1. Read the prompt's `answer_template.json` payload first. It defines the
   required output shape, allowed enumerations, stable identifiers, and units.
   Every field in the template must be populated; do not invent new top-level
   keys or omit required fields.

2. Gather all deal records from the workbench. Do not assume records from
   similarly named projects apply. Use only records keyed to the prompt's
   `deal_id`.