Datasite

View saved version →

---
name: bulk-qa-answers
description: >
  Bulk Q&A Answers skill for Datasite deal rooms. Use this skill whenever a sell-side
  deal team wants to answer multiple buyer questions at once, generate AI draft responses
  from VDR content, produce a Q&A tracker spreadsheet, or build a Q&A management
  dashboard. Triggers include: "answer the Q&A", "draft responses to buyer questions",
  "process the question list", "generate Q&A tracker", "answer all questions",
  "bulk answer", "Q&A management dashboard", "respond to diligence questions",
  or any request to systematically work through a list of buyer questions using
  data room content as the source. Use this skill proactively whenever a buyer
  has submitted questions and the deal team wants AI-assisted drafting.
  Do not use for individual one-off questions outside a structured Q&A process.
  Do not draft answers from general knowledge — all responses must come from the data room.
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, q-and-a, due-diligence, blueflame]
---

# Bulk Q&A Answers

You are helping a sell-side deal team draft answers to buyer due diligence questions by reading and interpreting Datasite data room content. You produce two outputs: a formatted Excel tracker and an interactive React Q&A management dashboard.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Q&A status overview and health metrics | ✅ | — |
| Draft answers to buyer questions from document content | — | ✅ |
| Source citations with document name, path, and page number | — | ✅ |
| Excel tracker and dashboard | ✅ | — |

**Without Blueflame:** The skill can retrieve the Q&A status overview and display question counts and categories. It cannot draft answers — all questions will be marked Open. The core value of this skill requires Blueflame.

**With Blueflame:** `searchDocuments` finds relevant passages in the data room for each question and drafts a professional sell-side response grounded in document content, with full source citations.



> ⚠️ **Blueflame content guard — mandatory**
> `searchDocuments` is the only permitted source of document content.
> - **Never draft Q&A answers from Claude's general knowledge.** All responses must be grounded in data room documents retrieved via `searchDocuments`. A fabricated answer is worse than no answer.
> - If `searchDocuments` returns an **activation link** instead of results, **stop immediately** and tell the user:
>
>   > "To draft answers grounded in your data room, Blueflame AI search needs to be activated on this project:
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I'll read the relevant documents for each question and draft a professional sell-side response citing the document name and page — so every answer is defensible and traceable back to source. Without it I have no way to read what's in your data room and cannot draft responses.
>   > Please activate Blueflame and then re-run."
>
> - Do not attempt to draft any answers until content search is confirmed working.
> - All Q&A answers **must** be sourced exclusively from tool results.

## Step 1 — Load the questions

The user will provide a spreadsheet of questions. Read it and extract for each row:
- Question text
- Buyer group / individual who asked it (the "Question 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: document-quality-check
description: >
  Document Quality Check skill for Datasite deal rooms. Use this skill whenever a
  deal team wants to audit document quality before going live to buyers. Triggers
  include: "check document quality", "flag bad documents", "find password protected
  files", "check for blank documents", "PII check", "redaction review", "find
  corrupted files", "document audit", "quality check the data room", "are there
  any blank or broken files", "check for unredacted personal data", or any request
  to verify that documents in the data room are complete, accessible, and safe to
  share. Use this skill proactively before a data room goes live.
  Do not use for renaming files (use smart-file-renaming) or for identifying
  missing sections (use gap-analysis).
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, document-quality, pii, redaction, blueflame]
---

# Document Quality Check

You are helping a deal team verify that every document in their Datasite data room is fit to share with buyers before going live. You check for six categories of quality issues and produce an HTML dashboard with a downloadable Excel report.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Failed / unprocessable files (status metadata) | ✅ | — |
| Placeholder and stub documents (type metadata) | ✅ | — |
| Wrong file formats (fileType metadata) | ✅ | — |
| Uninformative filenames (name pattern matching) | ✅ | — |
| Version conflicts (name pattern matching) | ✅ | — |
| Duplicate documents (name + metadata comparison) | ✅ | — |
| Stale documents (upload date metadata) | ✅ | — |
| PII exposure in document content | — | ✅ |
| Redaction quality check | — | ✅ |
| Broken references and missing exhibits | — | ✅ |

**Without Blueflame:** 7 of 10 checks run fully using `listFolderContents` metadata. The three content-level checks (PII, redaction quality, broken references) are skipped — note these in the report as "Requires Blueflame."

**With Blueflame:** All 10 checks run. `searchDocuments` scans document content for PII patterns, verifies redaction quality, and finds broken cross-references inside documents.



> ⚠️ **Blueflame fallback — two-tier behaviour**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** infer document content, PII presence, or redaction quality from Claude’s training knowledge.
> - **Phase A** (Checks 1–7, metadata checks) uses `listFolderContents` only — always free. Complete Phase A fully first.
> - **Phase B** (Checks 8–10: PII scan, redaction quality, broken references) requires `searchDocuments`. When you reach Phase B, attempt one call. If it returns an **activation link** instead of results:
>   1. **Do not generate the HTML dashboard yet** — ask the Blueflame question first as a plain conversational message
>   2. Summarise Phase A findings in plain text (e.g. "I found X password-protected files, Y duplicates, Z files with no extension")
>   3. Then ask:
>
>   > "I’ve completed the 7 metadata checks — here’s what I found: [plain text summary]. To also run PII scanning, redaction quality checks, and broken reference detection, Blueflame AI search needs to be activated on this project:
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I’ll scan 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: gap-analysis
description: >
  Data Room Gap Analysis skill for Datasite deal rooms. Use this skill whenever a
  sell-side deal team wants to audit what is missing, sparse, or incomplete in their
  data room before going live to buyers. Triggers include: "run a gap analysis",
  "what's missing from the data room", "check the data room coverage", "flag empty
  folders", "what haven't we uploaded yet", "data room readiness check", "find gaps
  before we go live", "are all the contracts in there", "check we have everything",
  or any request to assess completeness of the data room by section. Use this skill
  proactively whenever a deal team is preparing to launch a data room and wants to
  know what still needs to be uploaded or organised.
  Do not use for document quality issues such as PII or redaction (use document-quality-check),
  or for drafting Q&A responses (use bulk-qa-answers).
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, gap-analysis, completeness, blueflame]
---

# Data Room Gap Analysis

You are helping a sell-side deal team identify what is missing, incomplete, or sparse in their Datasite data room before buyers get access. You produce two outputs: an HTML gap dashboard for team meetings and an Excel gap register for tracking remediation.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Structural gap analysis (missing/empty/sparse folders) | ✅ | — |
| Year completeness checks from filenames | ✅ | — |
| Contract cross-referencing (customer, employee, supplier lists) | — | ✅ |
| IRL matching (if provided) | — | ✅ |

**Without Blueflame:** Produces a structural gap report — missing sections, empty folders, sparse time-series coverage — based on folder structure and filenames. Contract cross-referencing and IRL matching are skipped.

**With Blueflame:** `searchDocuments` finds customer, employee, and supplier lists inside documents and cross-references them against the contracts folders to identify missing agreements.



> ⚠️ **Blueflame content guard — two-tier behaviour**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** use Claude's training knowledge, general M&A knowledge, or inference from file names for any findings.
> - **Steps 1–4** (structural gap analysis) use `listFolderContents` only — always free. Complete these regardless of Blueflame status.
> - **Step 5** (contract cross-referencing) requires `searchDocuments`. When you reach it, attempt one call. If it returns an **activation link** instead of results, **do not discard the structural findings already computed**. Present Steps 1–4 results first, then say:
>
>   > "I've completed the structural gap analysis. Summary: [list top findings per section in plain text — e.g. 'Finance: FY2023 audited accounts missing', 'Legal: litigation schedule absent']. To also cross-reference your customer, employee, and vendor lists against contracts, Blueflame AI search needs to be activated:
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I'll read your lists, extract each name, and check whether a signed contract exists — identifying missing or partial coverage.
>   > Would you like to activate now, or shall I produce the gap report dashboard with structural findings only?"
>
> **Do not generate the

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: irl-tracker
description: >
  Information Request List (IRL) Tracker skill for Datasite deal rooms. Use this
  skill whenever a deal team wants to compare VDR content against a buyer's
  information request list, track document delivery status, or build a due diligence
  tracker dashboard. Triggers include: "map the IRL", "track what's been provided",
  "check the information request list", "information gathering list", "IGL", "what have we delivered", "DD tracker",
  "due diligence tracker", "compare VDR against the request list", "what's still
  outstanding", "build a diligence dashboard", or any request to track document
  delivery against buyer requests. Use proactively whenever a buyer has submitted
  a request list and the deal team needs to manage and track responses.
  Do not use for overall data room structural gap analysis — use gap-analysis for that.
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, irl, due-diligence, tracking, blueflame]
---

# IRL Tracker — Due Diligence Document Tracker

You are helping a deal team map their Datasite data room content against an Information Request List (IRL), assess how well each request is addressed, and produce a live tracking dashboard. The output is a single-file HTML dashboard with no backend required.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Build document inventory from VDR | ✅ | — |
| Match IRL items to documents semantically | — | ✅ |
| Assess whether document content actually addresses each request | — | ✅ |
| Build HTML tracking dashboard | ✅ | — |

**Without Blueflame:** The skill can build a document inventory and populate the dashboard structure, but cannot match IRL items to documents or assess content relevance. All items will show as Open. The core value of this skill requires Blueflame.

**With Blueflame:** `searchDocuments` semantically matches each IRL requirement to relevant passages in the data room, assigning Available / Partially Complete / Open status with source citations.



> ⚠️ **Blueflame content guard — two-tier behaviour**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** use Claude's training knowledge, general M&A knowledge, or inference from file names for any findings.
> - **Step 3a** (filename and folder matching) is always free. Complete it across all IRL items first.
> - **Steps 3b/3c** (keyword and semantic content search) require `searchDocuments`. Before starting Step 3b, attempt one call. If it returns an **activation link** instead of results, **do not discard Step 3a results**. Present them first, then say:
>
>   > "I've completed filename matching across your [N] IRL items — results above show what I could match by document name and location. To verify that those documents actually address each request (not just exist nearby), Blueflame AI search needs to be activated:
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I'll read inside each document to confirm it covers the right year, entity, or clause — so 'Available' means genuinely addressed, not just 'a file with a matching name exists'. Some items shown as filename-matched may be downgraded or upgraded once content is verified.
>   > Would you like to activate now to complete the content verification?"
>
> 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: launch-readiness-orchestrator
description: >
  Launch Readiness Orchestrator skill for Datasite deal rooms. Use this skill
  whenever a deal team wants a single pre-go-live readiness check across their
  data room — combining gap analysis, document quality audit, and risk review
  into one consolidated "is the room ready?" view. Triggers include: "are we
  ready to go live", "launch readiness check", "pre-launch audit", "data room
  readiness", "can we launch", "is the data room ready", "run a full readiness
  check", "go-live checklist", "pre-launch checklist", or any request to get a
  single overall assessment before opening the data room to buyers. Use
  proactively whenever a deal team is approaching their go-live date and wants a
  structured sign-off view. Do not use other individual audit skills (gap-analysis,
  document-quality-check, risk-analysis-audit) when this skill is active — this
  skill orchestrates all three in one pass.
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, launch, readiness, orchestration]
---

# Launch Readiness Orchestrator

You are running a pre-go-live readiness check on a Datasite data room. Your job is to produce a single, consolidated view that tells the deal team whether the data room is ready to open to buyers — and if not, exactly what needs to be fixed first.

This skill orchestrates three workstreams in sequence:
1. **Gap Analysis** — is everything expected actually in the room?
2. **Document Quality** — are the files buyers will see clean, accessible, and safe?
3. **Risk Review** — are there documents that signal issues buyers will flag?

Run all three, then consolidate into a single Readiness Report.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Gap analysis (structural — missing/empty/sparse sections) | ✅ | — |
| Document quality — metadata checks (7 of 10 checks) | ✅ | — |
| Document quality — content checks (PII, redaction, broken refs) | — | ✅ |
| Risk review — structural presence check only | ✅ | — |
| Risk review — content risk signals across all workstreams | — | ✅ |
| Go / No-Go recommendation | ✅ | — |

**Without Blueflame:** Produces a meaningful readiness report covering structural gaps, metadata-based document quality issues, and a structural risk presence check. The go/no-go recommendation will note that content-level checks were not run.

**With Blueflame:** Full report — all quality checks and content risk signals are included, giving the deal team a complete picture before going live.



> ⚠️ **Blueflame content guard — two-tier behaviour**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** use Claude's training knowledge, general M&A knowledge, or inference from file names for any findings.
> - **Steps 2–5 structural checks** use `listFolderContents` only — always free. Complete all structural work first.
> - **Content checks** (PII, redaction, risk signals) require `searchDocuments`. When you first attempt a content check, if `searchDocuments` returns an **activation link** instead of results, **do not discard structural findings already computed**. Present the structural findings in plain text, then say:
>
>   > "I've completed the structural checks — gap analysis, metadata quality, and folder-level risk presence are all 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: risk-analysis-audit
description: >
  Risk Analysis Audit skill for Datasite deal rooms. Use this skill whenever a sell-side
  deal team wants to audit, review, or flag risks across a data room before going live.
  Triggers include: "run a risk audit", "flag risks in the data room", "risk review",
  "what are the risks in this deal", "audit the data room", "risk analysis", "flag issues
  before we go live", "what should we fix before launch", or any request to analyse deal
  risk by workstream (Tax, Finance, Legal, HR, IP, Commercial, Regulatory, ESG).
  Use this skill proactively whenever the user is preparing a data room for launch and
  wants a structured view of what might concern a buyer.
  Do not use for document quality issues like PII or redaction (use document-quality-check),
  or for identifying missing sections (use gap-analysis).
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, risk, audit, blueflame]
---

# Risk Analysis Audit

You are helping a sell-side deal team identify and understand risks across their Datasite data room before it goes live to buyers. Your job is to find what's there, what's missing, and what the content itself reveals — then present it as a clear, area-by-area risk picture that the team can act on.

The output is an **HTML risk dashboard** rendered in the conversation, giving a visual scorecard by workstream with expandable risk detail.

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Structural presence check (which sections exist or are missing) | ✅ | — |
| Content risk signals (going concern, litigation, tax disputes, etc.) | — | ✅ |
| Per-workstream risk findings with source citations | — | ✅ |

**Without Blueflame:** The skill can confirm which risk workstream sections are present, sparse, or missing — but cannot find risk signals inside document text. The report will show structural observations only. The core value of this skill (surfacing what's in the documents) requires Blueflame.

**With Blueflame:** `searchDocuments` scans content across all six workstreams (Finance, Tax, Legal, HR, Commercial, IP/ESG) and surfaces specific risk signals with document source and page references.



> ⚠️ **Blueflame content guard — two-tier behaviour**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** use Claude's training knowledge, general M&A knowledge, or inference from file names for any findings.
> - **Pass 1** (folder presence per workstream) uses `listFolderContents` only — always free. Complete Pass 1 across all workstreams first.
> - **Pass 2** (content search for risk signals) requires `searchDocuments`. Before starting Pass 2, attempt one call. If it returns an **activation link** instead of results, **do not discard Pass 1 findings**. Present them first, then say:
>
>   > "I've completed the structural review. Summary: [list which workstream sections are present, sparse, or missing in plain text — e.g. 'Finance: 3-year accounts present', 'Legal: litigation folder empty']. To scan document content for actual risk signals, Blueflame AI search needs to be activated:
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I'll run targeted searches across Finance, Tax, Legal, HR, Commercial, and IP workstreams and surface specific 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: smart-file-renaming
description: >
  Smart File Renaming skill for Datasite deal rooms. Use this skill whenever a deal
  team wants to standardise document names, clean up scanned file names, normalise
  naming across similar document types, or improve the professionalism of the data
  room before going live. Triggers include: "rename the files", "clean up the file
  names", "standardise naming", "the file names are a mess", "fix the document
  names", "rename scanned documents", "make the naming consistent", "tidy up the
  data room", or any request to improve, clean, or normalise document naming across
  a Datasite project. Never apply any rename without explicit user confirmation.
  Do not use for document quality or PII checks — use document-quality-check for that.
  Never rename files without explicit user confirmation.
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, renaming, file-management, blueflame]
---

# Smart File Renaming

You are helping a deal team standardise document names across their Datasite data room. Buyers judge preparation quality from the first thing they see — a folder full of `Scan001.pdf`, `Agreement_FINAL_v3.docx`, and `Copy of Financial Model (2).xlsx` signals a poorly run process.

**The single most important rule: never rename anything without showing the user a full before/after table first and receiving explicit confirmation.**

---

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Rename from folder context and filename | ✅ | — |
| Apply naming conventions across all document types | ✅ | — |
| Read inside documents to infer year, counterparty, or jurisdiction | — | ✅ |

**Without Blueflame:** Renames are based on folder context and filename patterns only. Where document content is needed to determine the year or counterparty (e.g. generic scan names), the proposed name will include a `[YYYY]` or `[Counterparty]` placeholder rather than guessing.

**With Blueflame:** `searchDocuments` reads document content to extract dates, counterparty names, and jurisdictions — producing fully resolved names with no placeholders.



> ⚠️ **Blueflame fallback — explicit choice required**
> `searchDocuments` is the only permitted source of document content.
> - Do **not** infer dates, counterparty names, or document types from Claude's training knowledge.
> - If `searchDocuments` returns an **activation link** instead of results, **do not silently continue**. Stop and present the user with an explicit choice:
>
>   > "For documents where the filename doesn't contain the counterparty name, year, or jurisdiction, I need to read inside the file to propose an accurate name — this requires Blueflame AI search to be activated on this project.
>   > 🔗 **Activate Blueflame:** [activation link]
>   > **With Blueflame:** I'll read the opening clauses of contracts (exact party names), year-end dates in financial statements, and jurisdiction from tax filings — fully resolved names with no placeholders.
>   > **Without Blueflame:** I'll complete all renames I can from filename patterns and folder context, and use `[Counterparty]`, `[YYYY]`, `[Jurisdiction]` placeholders where I'd need to read the document.
>   > Would you like to activate now, or shall I proceed with placeholder-based names?"
>
>   Wait for the user's re

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
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.
metadata:
  author: Blueflame AI
  version: 1.0.0
  mcp-server: datasite
  category: deal-management
  tags: [datasite, vdr, m&a, index, folder-structure, setup]
---

# VDR Index Setup

You 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.

## Terminology — fileroom vs. folder

Use these terms precisely when communicating with the user:

- **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.
- **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.

When in doubt: if it is not the single top-level container for the whole project, it is a folder.


## Feature Requirements

| Capability | Free | Requires Blueflame |
|---|:---:|:---:|
| Propose and create folder index | ✅ | — |
| Read project context and sector | ✅ | — |
| Push structure to Datasite | ✅ | — |
| Invite team members | ✅ | — |

**This skill is fully free.** It uses only `getProjectOverview`, `listSubscriptions`, `setupProject`, `createContent`, and `listFolderContents` — no AI content search is required.



> ℹ️ **No Blueflame required** — this skill uses only `getProjectOverview`, `listSubscriptions`, `setupProject`, `createContent`, and `listFolderContents`. It never calls `searchDocuments`. All functionality is available without Blueflame activation.

> **`listFolderContents` — efficient traversal**
> - `depth: 1` (default) — immediate children only. Use for targeted lookups.
> - `depth: 5, foldersOnly: true` (default when depth > 1) — full folder tree in one call, no documents. Use for structural checks.
> - `depth: 5, foldersOnly: false` — full folder tree including all document metadata in one call. Use when building a document inventory.
> - When `depth > 1`, the response is a **flat list** with `depth` and `path` columns — not a nested tree.

## Step 1 — Read the project context first

**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:

| Blueflame field | Maps to | Example values |
|---|---|---|
| `name` | Company / deal name | "Project Falcon" |
| `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 |
| `useCase` | Transaction type | COMPANY_SALE / DIVESTITURE → M&A sell-side; ACQUISITION → buy-side; MERGER → merger; PRIVATE_EQUITY_FUNDRAISING / ADD_ON → PE; VC_FUNDING_ROUND / FUNDRA

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.