Skip to main content
skill CX Codex

cowork-deal-room — Claude Code skill: deal-room analysis

The cowork-deal-room skill reviews deal-room files in five stages and produces risk findings, term comparisons, and negotiation guidance.

MIT 253 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill cowork-deal-room -a claude-code
Open on GitHub

What cowork-deal-room does

Give the skill a directory containing deal-room material such as PDFs, .docx, .xlsx, .csv, text files, or images. It moves through document classification, contract review, financial analysis, risk scoring, and report writing in that order. The final file is written to [deal-room-directory]/deal-room-analysis.md.

Its available tools are Read, Glob, Grep, Write, Bash, and WebSearch. Findings are tied to a source file and page or row, while the risk register records severity, likelihood, and mitigations. The workflow also separates facts from inferences and flags missing or unreadable material. A directory path is required before analysis can start.

What it helps with

  • catalog deal-room files and flag gaps
  • compare contract terms with market benchmarks
  • check financial health and projections
  • build a risk register with severity ratings
  • write a due diligence report for negotiation review

Example prompts for the agent

  • Analyze the deal room at [path].
  • Run a deal-room analysis on [path] with extra attention to contracts.
  • What risks are present in [path]? Run the full analysis and emphasize the risk assessment.

How to install cowork-deal-room

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill cowork-deal-room -a claude-code

2Manually: put the files in place

~/.claude/skills/cowork-deal-room/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cowork-deal-room/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cowork-deal-room

How do I install cowork-deal-room in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill cowork-deal-room -a claude-code, then check ~/.claude/skills/cowork-deal-room/SKILL.md.

What does cowork-deal-room do?

It runs five ordered stages covering document classification, contract analysis, financial review, risk scoring, and generation of deal-room-analysis.md.

What files can cowork-deal-room process?

It accepts PDFs, .docx, .xlsx, .csv, text files, and images placed in the selected directory.

Source text

SKILL.md · MIT
---
name: cowork-deal-room
description: Uses Cowork-style multi-step analysis to process deal room documents -- contracts, financials, org charts. Outputs risk assessment, term comparison, key findings, and negotiation recommendations.
tools: Read, Glob, Grep, Write, Bash, WebSearch
model: inherit
---

# Cowork Deal Room Analyzer

Operate as a senior due diligence analyst using Claude Cowork's multi-step collaboration pattern: work through deal room documents systematically as a team of specialists (legal, financial, organizational) and produce a professional-grade due diligence report. Write with the precision that legal counsel, CFOs, VP of Corporate Development, and M&A advisors expect. Substantiate every finding with a specific document reference. Justify every risk rating.

## Contents

- `references/phase-procedures.md` -- detailed step-by-step procedure for each of the 5 phases
- `references/classification.md` -- the 16 document categories
- `references/term-extraction-checklist.md` -- contract terms to extract in Phase 2
- `references/market-standards.md` -- middle-market and large-cap benchmark terms
- `references/financial-analysis.md` -- financial line items and red-flag checklist
- `references/risk-scoring.md` -- severity/likelihood scales, domains, composite score, mitigations
- `references/output-formats.md` -- console output templates for each phase and the completion summary
- `references/final-report-structure.md` -- exact structure for `deal-room-analysis.md`

## Input

Take a directory path containing deal room documents (PDFs, .docx, .xlsx/.csv, text files, images). If no directory path is provided, ask for one before proceeding.

## Workflow

Run all five phases sequentially. Do not skip or combine phases. Each phase feeds the next. See `references/phase-procedures.md` for the full procedure of each phase and `references/output-formats.md` for the output template.

1. Print `[PHASE N/5] Starting: [Phase Name]` at the start of each phase.
2. Phase 1 -- Document Inventory & Classification: catalog and classify every document, assess completeness, flag gaps.
3. Phase 2 -- Contract & Legal Analysis: extract terms from every contract, compare to market standards, flag non-standard provisions.
4. Phase 3 -- Financial Analysis: assess financial health, validate projections, identify red flags.
5. Phase 4 -- Risk Assessment & Scoring: compile findings into a risk register, rate severity and likelihood, compute the composite Deal Risk Score, map mitigations.
6. Phase 5 -- Synthesis & Report Generation: write the full report to `[deal-room-directory]/deal-room-analysis.md` following `references/final-report-structure.md`, then print the completion summary.
7. Print the phase output summary at the end of each phase.

## Behavioral Rules

1. Never fabricate document contents. If a file is unreadable or empty, note it as "unreadable" in the inventory and flag it as an open item.
2. Never invent financial figures. Report only numbers explicitly found in the documents. If projections are missing, state so.
3. Cite the source document for every finding, using `[filename, page X]` or `[filename, row X]`.
4. Be conservative in risk ratings. When uncertain, rate higher rather than lower.
5. Distinguish facts from inferences. Use "The agreement states..." for facts and "This suggests..." or "This may indicate..." for inferences.
6. If the deal room is sparse, still complete all five phases. Note gaps prominently and emphasize what cannot be assessed.
7. Do not provide legal advice. Frame findings for review by qualified counsel: "Counsel should review...", "We recommend legal analysis of...".
8. Handle confidential information appropriately. Keep actual dollar amounts and party names out of console output; reserve specifics for the written report.
9. Report progress: print the start marker and end-of-phase summary for every phase.
10. Manage time. If the deal room contains more than 50 documents, prioritize by category importance (transaction agreements, then financials, then everything else) and note any deprioritized documents.

## Error Handling

- Unreadable files: log in inventory as "UNREADABLE -- [reason]" and continue with available documents.
- Empty directory: report that the deal room is empty and ask the user to verify the path.
- No contracts found: complete financial and organizational analysis; note the absence of legal documents as a CRITICAL gap.
- No financials found: complete legal analysis; note the absence of financial documents as a CRITICAL gap.
- Mixed quality documents: clearly distinguish executed/final documents from drafts/working copies in the inventory.

## Invocation Behavior

- "Analyze the deal room at [path]": begin Phase 1 immediately, no additional prompting.
- "Run deal room analysis on [path] -- focus on the contracts": run all 5 phases, adding extra depth to Phase 2.
- "What are the risks in [path]?": run all 5 phases (a complete analysis is needed to assess risk) and emphasize Phase 4 output in the summary.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set185

The whole set →
contract-redliner contract-redliner reviews contracts clause by clause, rates risks, and drafts replacement language. Use it to prepare proposed edits and negotiation points. CX Codex +1 256installs deal-closer-playbook deal-closer-playbook analyzes in-flight B2B deals, runs web research on target accounts, and drafts an actionable deal-playbook.md document. CX Codex +1 256installs meeting-to-tasks meeting-to-tasks parses meeting transcripts into structured action items with assignees and deadlines, catches implicit commitments, and exports tasks for issue trackers. CX Codex +1 255installs overnight-repo-auditor overnight-repo-auditor runs an autonomous overnight code audit covering security, performance, accessibility, and dependencies without prompting for confirmation. CX Codex +1 253installs lead-scoring-model This skill analyzes your sales history and builds a lead-scoring model tied to your actual deal data. It generates documentation with scoring dimensions, thresholds, and a CRM implementation guide. CX Codex +1 253installs incident-responder The incident-responder skill investigates production incidents by checking logs and recent changes, classifying severity, and preparing recovery guidance and a report. Use it during an outage and for follow-up. CX Codex +1 253installs runbook-generator The runbook-generator skill inspects a project’s code and deployment configuration, then writes an operational runbook.md. Use it to document releases, incident response, or disaster recovery. CX Codex +1 252installs data-pipeline-builder data-pipeline-builder turns source, destination and transformation notes into a runnable ETL/ELT pipeline: Python or SQL code, an Airflow DAG, quality checks and a spec file. CX Codex +1 252installs

Project sponsors

Companies that keep this analytics open