cowork-data-room-builder — Claude Code skill: setup & overview
cowork-data-room-builder — a Claude Code skill that prepares sell-side data rooms for fundraising, M&A, or loans. It sweeps document folders, flags missing files, and structures the room with an index.
MIT 104 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a claude-codeWhat cowork-data-room-builder does
The skill generates a diligence checklist based on the stage and transaction type, from seed rounds to acquisitions and debt facilities. It walks target folders to pair files with categories like corporate records, cap tables, material contracts, and tax filings. Matches are classified as executed finals, drafts, or stale documents.
It then delivers a gap report using HAVE, HAVE-BUT-DRAFT, HAVE-BUT-STALE, and MISSING statuses. Missing items are ranked by when diligence teams request them, highlighting formation filings and cap tables before customer agreements. Once approved, the skill builds numbered folders and generates an INDEX.md linking every item to its file.
Original directories stay completely untouched because documents are copied rather than moved. Before sharing, a red-flag pass flags unsigned copies, change-of-control assignment clauses, and unredacted compensation records for legal counsel review.
What it helps with
- generate deal-stage diligence checklists for acquisitions or fundraising
- detect missing and unexecuted corporate records across local folders
- organize data room files into clean numbered folders with an
INDEX.md - flag change-of-control clauses and unredacted compensation data
Example prompts for the agent
- Build the checklist for Series A
- What am I missing in the legal and finance folders?
- Assemble the room from ./docs and ./contracts
How to install cowork-data-room-builder
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-data-room-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-data-room-builder/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a codex2Manually: put the files in place
.agents/skills/cowork-data-room-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a cursor2Manually: put the files in place
.cursor/skills/cowork-data-room-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-data-room-builder2Manually: put the files in place
.github/skills/cowork-data-room-builder/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-data-room-builderManually: put the files in place
.devin/skills/cowork-data-room-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-data-room-builder
How to install cowork-data-room-builder in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-data-room-builder -a claude-code. The skill installs into ~/.claude/skills/cowork-data-room-builder/SKILL.md.
What does cowork-data-room-builder do?
It maps local corporate files against diligence requirements, pinpoints missing documents, and copies everything into a numbered export directory with an INDEX.md.
Does the skill alter or move source files?
No. It strictly copies files into a separate structure, ensuring original company folders remain untouched.
Source text
SKILL.md · MIT
--- name: cowork-data-room-builder description: Prepare YOUR data room for a fundraise, acquisition, or bank diligence -- builds the checklist for your deal stage, sweeps your folders for what you already have, produces a gap report, and organizes everything into the structure buyers and investors expect. The sell-side complement to cowork-deal-room. tools: Read, Glob, Grep, Write, Bash, WebSearch model: inherit --- # Cowork Data Room Builder Prepare a data room the way a banker's analyst does: know what the other side's diligence team will ask for before they ask, find it or flag it, and present it in the structure they expect. Inputs: the deal type (seed/Series A/growth round, acquisition, loan) and one or more folders of company documents. ## Workflow 1. **Build the request list.** Generate the diligence checklist for the stated deal type and stage: corporate records, cap table and securities, financials, material contracts, IP, employment, tax, insurance, litigation, and (for later stages) customer concentration and compliance. Present it for approval -- the user may know their acquirer's quirks. 2. **Sweep.** Walk the provided folders and match every document to a checklist item. Classify each match `FINAL` (executed/signed), `DRAFT`, or `STALE` (superseded or older than the period requested). One file can satisfy multiple items. 3. **Gap report.** Output the checklist with status per item: `HAVE`, `HAVE-BUT-DRAFT`, `HAVE-BUT-STALE`, `MISSING`. Rank the missing items by how early diligence will hit them (corporate formation docs and cap table before customer contracts). This report is the deliverable that saves the deal timeline. 4. **Organize.** On approval, build the data room folder structure (numbered top-level sections matching the checklist), copy -- never move -- documents in with clean names (`3.2-msa-acme-corp-executed-2025.pdf`), and write `INDEX.md` mapping every checklist item to its file. 5. **Red-flag pass.** Before anything is shared, list documents that need a decision: unsigned versions where an executed copy should exist, contracts with change-of-control or assignment clauses the deal will trigger, documents containing employee compensation or customer-identifying data that may warrant redaction or a later disclosure phase. ## Rules - Copy, never move. The data room is a curated export; source folders stay untouched. - Never place a draft where a final belongs without labeling it `DRAFT` in the filename and index. - Never redact or exclude documents silently -- list redaction candidates and let counsel decide. - The gap report states what was searched, so "MISSING" means "not in the provided folders," not "does not exist." - Stage-appropriate depth: do not demand SOC 2 reports from a pre-seed company; do not omit them for a growth round. - This is preparation support, not legal or securities advice. Frame judgment calls for counsel. ## Quick Commands - "Build the checklist for [deal type]" -- step 1 only - "What am I missing?" -- steps 1-3, the gap report - "Assemble the room from [folders]" -- full workflow - "Red-flag check" -- step 5 against an existing data room
© OneWave-AI · MIT · OneWave-AI/claude-skills