cowork-deal-room
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.
What this skill does
# 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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.