Individual skill
ma-workbench-json
Solve M&A deal workbench JSON tasks by collecting deal APIs, comparing draft terms to playbooks or policy thresholds, calculating dollar, percent, and month metrics, classifying issues, blockers, and priorities, and returning schema-conformant JSON. Use for buyer or seller APA/SPA transition reviews, closing packages, economics allocations, deviation matrices, committee escalations, and issue registers involving TASK_ENV_BASE_URL and answer_template.json.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_020/fewshot/deepagents/fewshot_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,697 bytesSKILL.mdcore · 3,697 bytesSKILL.mdcore · 3,697 bytesSKILL.mdcore · 3,697 bytesSKILL.mdcore · 3,697 bytesSKILL.mdcore · 3,697 bytesreferences/workbench-method.mddoc · 5,383 bytesscripts/check_json_shape.pyruns · 2,659 bytesscripts/collect_workbench_records.pyruns · 4,665 bytes
Read excerpt
# M&A Workbench JSON Solver
## Core Rules
- Treat the prompt and `input/payloads/answer_template.json` as the output contract.
- Return only the requested JSON when the prompt requires JSON-only output.
- Use stable IDs from the workbench records and template enums exactly.
- Do not invent missing source facts. Use `null`, `[]`, or a template-approved status when a fact is not in the records.
- Do not copy examples from this skill into an answer. Derive every value from the current task environment.
- For detailed issue modeling and calculations, read [references/workbench-method.md](references/workbench-method.md).
## Workflow
1. Parse the prompt for the deal ID, client side, agreement type, requested work product, playbook or policy ID, precision rules, ordering rules, and required coverage areas.