Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
onewave-ai avatar

Cowork Deal Room

  • 162 installs
  • 237 repo stars
  • Updated July 15, 2026
  • onewave-ai/claude-skills

Organize and manage sales deal rooms with structured collaboration and stakeholder alignment.

About

The cowork-deal-room skill helps Claude manage collaborative deal rooms for complex sales cycles. It structures deal room content, tracks stakeholder engagement, and maintains momentum through organized communication. Sales teams can accelerate deal cycles by keeping all participants aligned and informed.

  • Claude Code skill
  • Agent productivity
  • Business workflow automation
  • Easy integration
  • Specialized domain expertise

Cowork Deal Room by the numbers

  • 162 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #3,200 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill cowork-deal-room

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs162
repo stars237
Last updatedJuly 15, 2026
Repositoryonewave-ai/claude-skills

What it does

Organize and manage sales deal rooms with structured collaboration and stakeholder alignment.

Who is it for?

Business professionals using Claude Code

Skip if: Non-Claude projects

What you get

  • enhanced agent workflow

Files

SKILL.mdMarkdownGitHub ↗

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.

Related skills

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.