agentleFS
OneWave-AIOneWave-AI/claude-skills/cowork-deal-room/SKILL.md

cowork-deal-room

Skill378 starsChanged 54 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run all five phases sequentially.

    line 29
  2. Distinctive:

    Never fabricate document contents.

    line 41
  3. Distinctive:

    Never invent financial figures.

    line 42
  4. Distinctive:

    If the deal room is sparse, still complete all five phases.

    line 46
  5. Distinctive:

    Do not provide legal advice.

    line 47
  6. Distinctive:

    No contracts found: complete financial and organizational analysis.

    line 56
  7. Distinctive:

    No financials found: complete legal analysis.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.