Update to Datasite

{
  "name": "vdr-index-setup",
  "description": "VDR Index Setup skill for Datasite deal rooms. Use this skill whenever a user wants to create, propose, design, or set up a Virtual Data Room (VDR) index or folder structure for a deal. Triggers include: \"set up a data room\", \"create a VDR index\", \"build a deal room structure\", \"prepare the index\", \"set up the fileroom\", \"I need a data room for [deal/company]\", or any request to organise or structure documents for due diligence. Also triggers when a user wants to replicate an existing deal room structure or import an index from a spreadsheet or reference deal. This skill MUST be used whenever the user is starting a new deal room or wants to customise the folder hierarchy before documents are uploaded. Do not use to audit or review an existing data room — use gap-analysis, document-quality-check, or risk-analysis-audit for that.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 210
    }
  ],
  "skill_md_contents": "---\nname: vdr-index-setup\ndescription: >\n  VDR Index Setup skill for Datasite deal rooms. Use this skill whenever\n  a user wants to create, propose, design, or set up a Virtual Data Room (VDR) index\n  or folder structure for a deal. Triggers include: \"set up a data room\", \"create a\n  VDR index\", \"build a deal room structure\", \"prepare the index\", \"set up the fileroom\",\n  \"I need a data room for [deal/company]\", or any request to organise or structure\n  documents for due diligence. Also triggers when a user wants to replicate an existing\n  deal room structure or import an index from a spreadsheet or reference deal. This skill\n  MUST be used whenever the user is starting a new deal room or wants to customise the\n  folder hierarchy before documents are uploaded.\n  Do not use to audit or review an existing data room — use gap-analysis,\n  document-quality-check, or risk-analysis-audit for that.\nmetadata:\n  author: Blueflame AI\n  version: 1.0.0\n  mcp-server: datasite\n  category: deal-management\n  tags: [datasite, vdr, m&a, index, folder-structure, setup]\n---\n\n# VDR Index Setup\n\nYou are helping a deal team on Datasite create a professional, customised Virtual Data Room (VDR) index — the folder hierarchy buyers and advisors will navigate during due diligence. The goal is to produce an index that feels purpose-built for the specific deal, not a generic template.\n\n## Terminology — fileroom vs. folder\n\nUse these terms precisely when communicating with the user:\n\n- **Fileroom** — the single top-level container inside a Datasite project. A project typically has one buyer-facing fileroom. It is not a subject area — it is the container that holds all subject areas.\n- **Folder** — everything inside the fileroom: the subject areas (Financial, Legal, HR, Tax, IP, etc.) and all sub-levels beneath them. Always call these folders, never filerooms.\n\nWhen in doubt: if it is not the single top-level container for the whole project, it is a folder.\n\n\n## Feature Requirements\n\n| Capability | Free | Requires Blueflame |\n|---|:---:|:---:|\n| Propose and create folder index | ✅ | — |\n| Read project context and sector | ✅ | — |\n| Push structure to Datasite | ✅ | — |\n| Invite team members | ✅ | — |\n\n**This skill is fully free.** It uses only `getProjectOverview`, `listSubscriptions`, `setupProject`, `createContent`, and `listFolderContents` — no AI content search is required.\n\n\n\n> ℹ️ **No Blueflame required** — this skill uses only `getProjectOverview`, `listSubscriptions`, `setupProject`, `createContent`, and `listFolderContents`. It never calls `searchDocuments`. All functionality is available without Blueflame activation.\n\n> **`listFolderContents` — efficient traversal**\n> - `depth: 1` (default) — immediate children only. Use for targeted lookups.\n> - `depth: 5, foldersOnly: true` (default when depth > 1) — full folder tree in one call, no documents. Use for structural checks.\n> - `depth: 5, foldersOnly: false` — full folder tree including all document metadata in one call. Use when building a document inventory.\n> - When `depth > 1`, the response is a **flat list** with `depth` and `path` columns — not a nested tree.\n\n## Step 1 — Read the project context first\n\n**Before asking the user anything**, call `getProjectOverview` on the current project. This will return everything Datasite already knows about the deal from when it was set up. Extract and map the following fields:\n\n| Blueflame field | Maps to | Example values |\n|---|---|---|\n| `name` | Company / deal name | \"Project Falcon\" |\n| `industryType` | Sector | TECHNOLOGY_MEDIA_TELECOM → Tech/SaaS; LIFE_SCIENCES_HEALTHCARE → Healthcare; CONSUMER → Retail/Consumer; INDUSTRIALS_TRANSPORT_DEFENSE → Manufacturing/Transport; ENERGY_MINING_OIL_GAS → Oil & Gas; FINANCIAL_SERVICES → Financial Services; REAL_ESTATE → Real Estate |\n| `useCase` | Transaction type | COMPANY_SALE / DIVESTITURE → M&A sell-side; ACQUISITION → buy-side; MERGER → merger; PRIVATE_EQUITY_FUNDRAISING / ADD_ON → PE; VC_FUNDING_ROUND / FUNDRAISING → capital raise; RESTRUCTURING_OR_INSOLVENCY → restructuring |\n| `transactionValue` | Size / complexity | LESS_THAN_US_10_M → SME; BETWEEN_US_10_M_AND_100_M → lower mid-market; BETWEEN_US_100_M_AND_500_M → mid-market; BETWEEN_US_500_M_AND_1_B / GREATER_THAN_US_1_B → large-cap |\n| `datacenter` | Geography hint | USA → US/North American; DEU → European (assume GDPR, EU regulatory); AUS → Australian |\n\nWith these four fields you already know the company name, sector, deal type, approximate size, and a geography signal. **Do not ask the user to repeat this information.**\n\n### What to ask about (only the genuine gaps)\n\nAfter reading the project, there may be a small number of things worth clarifying. Ask only what you actually need, in a single short message — not a form:\n\n- **Specific industry sub-type** if `industryType` is broad and it meaningfully changes the index. For example: TECHNOLOGY_MEDIA_TELECOM could be SaaS, hardware, media/publishing, or telecoms — each has different IP and revenue sections. CONSUMER could be retail, food & beverage, or e-commerce. If the project name makes it obvious (e.g. \"Project Falcon — CloudSoft Ltd\"), skip this.\n- **Jurisdiction precision** if the datacenter alone is ambiguous. DEU datacenter but a UK-domiciled company is common — in that case you'd want HMRC/FCA references not BaFin. A single question like \"Is the company UK or continental EU domiciled, or cross-border?\" is enough.\n- **Carve-out or subsidiary** flag if the `useCase` doesn't reveal it — a carve-out needs Transition Services Agreement, shared services, and stranded costs sections that a clean M&A sale doesn't.\n\nIf none of these gaps exist (e.g. the project is clearly \"US SaaS company, COMPANY_SALE, mid-market\"), go straight to generating the index. Don't ask questions for the sake of it.\n\n### Optional: reference structure\n\nAlso offer this once, briefly: \"If you'd like me to base the index on an existing deal structure, you can attach the index as a spreadsheet or give me a deal name and I'll read it from the platform.\" If the user provides one, go to **Step 1b** before generating.\n\n> **If the user has already attached a file or referenced another VDR at the start of the conversation, skip this offer entirely — go directly to Step 1b.** Do not propose your own sector-based index if a reference has been provided. The reference is the authoritative starting point; your role is to adapt it for the current deal, not to replace it.\n\n## Step 1b — Read a reference index (if provided)\n\n**If the user uploads a spreadsheet:**\nRead the file. Extract the folder hierarchy from the Index and Title columns.\n\n**If the user names a reference deal:**\nCall `listFolderContents` with `depth: 5` (leave `foldersOnly` at its default of `true`) to retrieve the full folder hierarchy in a single call. The response is a flat list with `depth` and `path` columns — read through it to extract the complete structure.\n\nAfter reading either source, **ask the user one question before proceeding:**\n\n> \"I've read the reference structure — [N] folders across [N] levels. How would you like me to use it?\n> - **Use as-is** — push it to the data room exactly as provided, no changes\n> - **Suggest additions** — keep the reference intact and flag any sections that are typically expected for a [sector] deal but aren't currently included\n> - **Full adaptation** — use it as a base and apply deal-specific tailoring for [company name] ([sector], [deal type])\"\n\nWait for the user's choice before doing anything else.\n\n- If **use as-is**: skip Step 2 entirely, go straight to Step 4 (confirm and push). Do not modify, rename, or reorder anything.\n- If **suggest additions**: present the reference index as-is, then append a clearly separated section: *\"Suggested additions for [sector]:\"* listing only what is missing. The user decides what to include before anything is pushed.\n- If **full adaptation**: proceed to Step 2 and generate the tailored index using the reference as the base structure.\n\n## Step 2 — Generate the proposed index\n\nUsing the project profile you've assembled, produce a complete, numbered folder hierarchy. Read `references/sector-templates.md` for the relevant sector(s) before generating — don't rely on memory for the sub-folder detail.\n\n**How to tailor the index:**\n\n**Sector** — pull the relevant sector section from the reference templates. Key distinctions:\n- SaaS / Technology → deep IP section (registered/unregistered rights, open-source, licensing in/out, domain names, software asset list), ARR/MRR in Finance, data privacy prominent under IT\n- Healthcare → add Regulatory & Clinical section (licences, CQC/FDA filings, clinical contracts), careful separation of NHS vs. private revenue\n- Manufacturing → add Plant & Equipment, Supply Chain, and Environmental sections\n- Oil & Gas → add Reserves, Environmental & Regulatory, Concession Agreements sections\n- Retail → add Leasehold Properties, Brand & Licensing, Supplier Contracts sections\n- Financial Services → add Regulatory Capital, FCA/SEC authorisations, Client Money sections\n\n**Transaction type:**\n- M&A sell-side (COMPANY_SALE, DIVESTITURE) → include Closing Documents section at the end\n- PE / add-on (PRIVATE_EQUITY_FUNDRAISING, ADD_ON) → stronger management/governance sections, lighter closing docs, include Management Accounts and KPIs\n- Carve-out (DIVESTITURE where partial) → add Transition Services Agreement, Shared Services, Stranded Costs, and Intercompany Agreements sections\n- Capital raise (VC_FUNDING_ROUND, FUNDRAISING) → include Investor Presentations, Cap Table History, Use of Proceeds, Funding History\n- Restructuring → include Insolvency Proceedings, Creditor Agreements, Security Documents\n\n**Geography:**\n- US / USA datacenter → IRS/SEC/EIN references, Federal/State/Local tax split, FCPA under Compliance\n- European / DEU datacenter → GDPR sub-folder prominent under IT/Data, EU regulatory references, VAT returns in Tax\n- UK-domiciled → HMRC references, FCA/CMA in Regulatory, Companies House in Corporate, use \"Articles of Association\" not \"By-Laws\"\n- Cross-border → duplicate Tax and Legal sections per jurisdiction (e.g. \"Tax — UK\", \"Tax — Germany\")\n\n**Size / complexity:**\n- SME (< $10M) → 2–3 levels, combine Accounting into Finance, lighter HR section\n- Lower mid-market ($10–100M) → standard 3 levels, most sections present but not fully expanded\n- Mid-market ($100–500M) → full 3–4 levels as in the base templates\n- Large-cap (> $500M) → maximum depth, consider splitting into multiple filerooms by workstream\n\n**Years of financial and corporate history** — set automatically, never ask the user:\n- Standard M&A sell-side (mid-market and below) → **3 years** audited financials (last 3 closed years, i.e. today's year − 1, − 2, − 3) + current-year management accounts to date\n- Large-cap (> $500M) → **5 years** audited financials; buyers and their advisors will expect this\n- VC / early-stage fundraise (`VC_FUNDING_ROUND` + `LESS_THAN_US_10_M`) → **2 years**, or inception-to-date if the company is younger; note this in the folder label\n- Restructuring / distressed → **3 years** but lead with management accounts over audited, since audits may be delayed or qualified\n- **Last closed financial year = today's year − 1.** Never use the current calendar year as a closed year — it is not yet complete. In 2026, the last closed year is FY2025.\n- Always use actual closed years (e.g. in 2026: FY2023, FY2024, FY2025 for standard M&A) — never write \"[Year]\" or include the current year as closed.\n- If the company is less than 3 years old, include all available years and add a note: e.g. \"Audited Financial Statements (FY2024, FY2025 — include inception-to-date accounts if prior history unavailable)\"\n- Apply the same year logic to corporate history folders (board minutes, tax returns, regulatory filings) — use the same horizon as financials for consistency\n\n**Format of the proposal:**\nPresent the index as a clean numbered hierarchy with indentation:\n\n```\n1. General Information\n   1.1 Corporate Organisation\n       1.1.1 Group Structure Chart\n       1.1.2 Certificate of Incorporation\n       1.1.3 Articles of Association\n       1.1.4 Board Minutes and Resolutions (last 3 years)\n   1.2 Shareholders\n       1.2.1 Shareholder Register\n       1.2.2 Shareholder Agreements\n       1.2.3 Cap Table\n2. Finance\n   2.1 Audited Financial Statements (FY2023, FY2024, FY2025)  ← example using 2026 as today; always use actual last-3-closed-years\n   2.2 Management Accounts (monthly, last 24 months)\n   ...\n```\n\nWhere years are relevant, always use actual calendar years based on today's date — never write \"[Year]\".\n\nClose with: \"This is my proposed index for [Company Name]. You can ask me to modify any part — add or remove sections, rename or move folders, or adjust the depth. Once you're happy I can push it to the data room, or export it to Excel first.\"\n\n## Step 3 — Iterate with the user\n\nHandle all edit requests conversationally:\n\n- **Add a section** → insert in a logical position and renumber. Briefly note where you've placed it if it's not obvious.\n- **Remove a section** → confirm and renumber. If it has children, confirm those go too.\n- **Rename** → apply to that folder only, unless the user says otherwise.\n- **Move** → relocate and renumber throughout. Adjust child numbering if the hierarchy level changes.\n- **Adjust depth** → \"collapse HR to one level\" flattens sub-folders; \"expand Contracts\" prompts for the desired sub-sections.\n\nAfter each change, show the updated portion (or the full index if it's a large restructure). Confirm the complete final state before moving to Step 4.\n\n## Step 4 — Confirm before pushing\n\nShow a clear confirmation gate before creating anything:\n\n> \"Here's the final index for **[Company Name]** — **[N] folders** across **[N] levels**. Ready to create this in the **[Fileroom Name]** data room. Shall I go ahead?\"\n\nAlso offer: \"Or I can export it as an Excel file in the Datasite import format if you'd prefer to import it manually.\"\n\nOnly proceed once the user confirms.\n\n## Step 5 — Push the index to Datasite\n\n> ⚠️ **PREPARE projects:** These use a Staging Folder (sandbox) exclusively. All content must be created within the Staging Folder — do not create filerooms or folders outside it. Use `listFolderContents` to locate the sandbox (type: SANDBOX, name: \"Staging Folder\") before creating any content.\n\n\n**Two options — choose based on whether the project already exists:**\n\n**Option A — New project (project does not yet exist):**\nUse `listSubscriptions` to find the available subscription, then call `setupProject` with the confirmed folder tree as a `contentTree` JSON array. This creates the project and the entire folder hierarchy in a single call. Example structure:\n```\n[{\"name\":\"Financial\",\"children\":[{\"name\":\"Audited Financial Statements\"},{\"name\":\"Management Accounts\"}]},{\"name\":\"Legal\"}]\n```\nTop-level nodes in `contentTree` become filerooms; nested nodes become folders.\n\n**Option B — Project already exists:**\n1. `listFolderContents` (no `metadataId`, `depth: 1`) — check if a fileroom already exists. Returns immediate top-level items only. If a fileroom exists, ask the user whether to add the index inside it or create a new one.\n2. `createContent` — create folders inside the existing fileroom. Pass the full tree as `contentTree` with the fileroom's `metadataId` as `parentId`.\n\n**Workflow:**\n1. `listFolderContents` (no `metadataId`, `depth: 1`) — check if a fileroom already exists.\n2. `createContent` — create the top-level fileroom if needed.\n3. `createContent` — pass the full folder tree as `contentTree` so the entire hierarchy is created in one call.\n\n**Error handling:** if a folder fails, note it and continue. Report failures at the end with the folder path so the user can investigate.\n\n**On completion:**\n> \"Done ✓ — **[N] folders** created in **[Fileroom Name]**. Top-level sections: [list].\n> 🔗 Open in Datasite: `https://app.global.datasite.com/en/platform/prepare/[projectId]/overview`\n> Let me know if you’d like to adjust anything or invite team members.\"\n\n**Important:** Always use the URL format above when linking to a Datasite project — `https://app.global.datasite.com/en/platform/prepare/{projectId}/overview`. Never construct a Datasite URL from memory or training knowledge; the format above is the only correct one.\n\n---\n\n## Reference materials\n\nRead `references/sector-templates.md` for the full folder structures for each sector. Load only the section(s) relevant to the current deal — there's no need to read the whole file.\n\n**Sectors covered:** Due Diligence (universal baseline), Technology, Healthcare, Healthcare Capital Raise, Manufacturing, Retail, Financial Services, Legal, Oil & Gas, Real Estate, Telecommunications, Transportation, Defence.\n\n---\n\n## Common Issues\n\n**`getProjectOverview` fails or returns the wrong project**\nCheck that the Datasite MCP connector is connected (Settings → Extensions → Datasite should show \"Connected\"). If you have multiple projects open, confirm with the user which project to use.\n\n**`listFolderContents` returns no results**\nThe fileroom may be empty or unpublished. Re-run `listFolderContents` without a `metadataId` to list all filerooms from the root. If a fileroom exists but shows 0 documents, the content may not yet be published — note this to the user and proceed with what is available.\n\n**`searchDocuments` returns an activation link instead of results**\nBlueflame AI search is not yet active on this project. Follow the Blueflame prompt in the skill instructions above. Do not attempt to answer using Claude's training knowledge.\n\n**MCP disconnects mid-workflow**\nReconnect via Settings → Extensions → Datasite. Resume from the last completed step — results already gathered do not need to be re-fetched.\n\n**`updateContent` or `createContent` returns a permissions error**\nThe user's Datasite account may not have Editor permissions on this project. Ask them to check their role in Datasite project settings.\n"
}