When the user wants to prepare a due diligence data room for fundraising, or when an investor has requested additional materials after a pitch. Also activates for "data room", "due diligence", "DD checklist", or "what documents do investors need?".
60
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/data-room/SKILL.mdFrom startup-context: stage, legal entity type, founding date, team composition, fundraising history, cap table basics, revenue/metrics, and any existing legal or financial documents.
From the user: current round stage (pre-term sheet vs. post-term sheet), which investor is requesting materials, and any specific document requests received.
.agents/startup-context.md to understand stage, entity type, and what documents should already exist.A structured checklist in markdown, organized by category:
## Data Room Checklist — [Company Name] — [Round]
### Section 1: Corporate Documents
- [x] Certificate of Incorporation — exists, current
- [ ] Board consent for fundraise — needs creation
- [ ] 409A valuation — needs update (last done 14 months ago)Followed by a recommended folder structure and access-level guidance.
1. Corporate Documents: Certificate of Incorporation (and amendments), bylaws, board minutes (last 12 months), board consent for fundraise, stockholder agreements, QSBS eligibility docs, state registrations, any pending litigation.
2. Cap Table & Equity: Fully diluted cap table (Carta/Pulley export, not a manual spreadsheet), option plan and grant ledger, SAFEs/convertible notes with terms, pro forma post-round cap table, current 409A valuation (<12 months old), secondary sale history.
3. Financials: P&L, balance sheet, cash flow — actual, last 12 months (monthly). Bank balance and burn rate. 18-36 month projections with stated assumptions. Revenue breakdown by customer/cohort. Unit economics (CAC, LTV, gross margin, payback). AR/AP aging. Outstanding debt.
4. Metrics & KPIs: Monthly KPI dashboard (MRR/ARR, growth, churn, NRR, DAU/MAU). Cohort retention. Sales pipeline (B2B) or funnel conversion (B2C/PLG).
5. Product & Technology: Product roadmap (6-12 months), architecture overview, IP ownership confirmation, patent filings, open source license audit, SOC 2 or security summary.
6. Contracts & Customers: Top 10 customer contracts, customer concentration analysis (<20% per customer is ideal), key vendor/partner agreements, exclusivity or non-compete clauses, churn log.
7. Team & HR: Org chart, founder/key employee bios, employment agreements (confirm IP assignment), contractor agreements, option grant summary, HR disputes, benefits summary.
8. Legal & Compliance: Privacy policy and GDPR/CCPA status, regulatory licenses, trademarks, terms of service, insurance (D&O, E&O, cyber).
/01-Corporate /05-Product-and-Technology
/02-Cap-Table-Equity /06-Contracts-Customers
/03-Financials /07-Team-HR
/04-Metrics-KPIs /08-Legal-Compliance
/09-Pitch-Materialspitch-deck — the deck is the top-of-funnel; the data room is the supporting evidenceinvestor-research — knowing which investors are in the pipeline helps prioritize what to prepare firstExample prompt: "We just got a term sheet for our Series A. What do I need in my data room?"
Good output approach: Generate the full 8-section checklist scoped for confirmatory DD. Cross-reference against startup context to pre-fill what likely exists. Flag highest-risk items (cap table accuracy, IP assignments, 409A currency). Recommend a folder structure and 2-4 week timeline.
Example prompt: "I'm about to start fundraising for our seed round. Should I set up a data room now?"
Good output snippet:
Yes — a proactive data room signals operational maturity. For seed, focus on:
- Clean cap table export (Carta or Pulley, not a spreadsheet)
- Certificate of Incorporation and amendments
- 6-month financial summary (revenue, burn, bank balance)
- IP assignment agreements for all founders and contractors
- Monthly KPI dashboard (MRR, user count, growth rate)
4ad31b4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.