Menu

Individual skill

reflect-3_attempt_03

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_020/reflect-3/reflect-3_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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 Skill

## Purpose

Solve structured M&A transaction counsel tasks using a running deal workbench. The workbench serves deal records, draft terms, playbook rules, policy thresholds, and diligence data through a REST API and optional read-only SQL. Every task requires gathering data from the workbench, comparing draft positions against a governing framework (playbook or policy), producing a structured JSON answer that conforms to a supplied answer template, and returning only that JSON.

## Core Workflow

Follow this sequence for every task; skip steps only when the task scope explicitly excludes them.

### 1. Read the prompt and template together

- Extract `deal_id`, `client_side` (buyer or seller), and the governing framework (`playbook_id` or `policy_id`) from the prompt.
- Read `input/payloads/answer_template.json` to learn the exact output shape, allowed enums, stable IDs, required fields, units, and ordering rules.
- Note any task-specific filters: e.g., "only current terms," "exclude stale," "only out-of-policy," "transition/separation focus only."