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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
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.
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:
Gap Analysis — is everything expected actually in the room?
Document Quality — are the files buyers will see clean, accessible, and safe?
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)
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 behavioursearchDocuments 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 above. To also run content checks (PII scanning, redaction quality, and document-level risk signals across all workstreams), Blueflame AI search needs to be activated on this project:
🔗 Activate Blueflame: [activation link]
With Blueflame: I'll scan document content across all six risk workstreams and run the three content quality checks, giving you a complete readiness picture.
Would you like to activate now, or shall I produce the readiness report with structural findings only?"
Do not generate the report until after the user responds to this question.
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
Call getProjectOverview. Extract:
Company / deal name
Sector (industryType)
Transaction type (useCase)
Deal size (transactionValue)
Geography (datacenter)
Do not ask the user for information already present in the project overview.
Step 2 — Find the fileroom and scan the structure
Call listFolderContents to find the active fileroom(s). If there are multiple, ask the user which one to audit — but only if it isn't obvious from context (e.g. one is clearly a buyer-facing room, another is a working folder).
Call listFolderContents on the root of the fileroom. Recurse through all top-level sections. You need:
A full list of every folder and its child count
Which folders are empty (0 documents)
Which folders exist but have suspiciously low content relative to what the section type would normally contain
Build an internal map of: folder path → document count. You will use this across all three workstreams.
Step 3 — Gap Analysis
Using the folder map from Step 2, compare against the expected structure for this deal type and sector.
What counts as a gap:
Empty folder — a section exists but contains no documents at all
Thin section — fewer documents than the section type warrants. Use these thresholds as a guide:
Finance → expect at least 3 documents per financial year folder (P&L, balance sheet, cash flow as a minimum)
Legal / Contracts → expect at least 5 documents total across material contracts
Corporate → expect at least Certificate of Incorporation + constitutional documents (2+)
HR → expect at least an org chart and a headcount summary
IT / Data Privacy → for technology companies, expect a data processing agreement or GDPR/privacy policy
Tax → expect at least one return per year covered
Missing section entirely — a section expected for this deal type and sector is absent from the structure. Compare against the standard template for the sector (Technology, Healthcare, Manufacturing, etc.) and flag whole sections that are missing
Severity ratings for gaps:
🔴 Blocker — empty Finance, Legal, or Corporate section; missing audited financials; no contracts at all
🟢 Minor — cosmetic gaps (e.g. missing cover sheet, no index document)
Step 4 — Document Quality Check
For each document in the fileroom, assess quality based on available metadata (file name, file type, size, upload date).
Metadata-only flags (always available, no Blueflame needed):
Zero-byte or near-zero-byte files — size of 0 KB or under 5 KB for a supposedly substantive document (e.g. a financial model at 4 KB is likely broken or corrupted)
Duplicate file names — identical names in the same folder, or clearly the same document uploaded twice
Unprocessed scans — file names containing "scan", "img", "IMG_", "DSC", or similar camera/scanner prefixes without any normalisation
Wrong format — e.g. a .jpg or .bmp in a Financials folder (images where PDFs or spreadsheets are expected)
Stale documents — upload date more than 12 months before today's date in an "active" section like Management Accounts or Board Minutes
Content-level flags (requires Blueflame):
If Blueflame is active, use searchDocuments to check for:
Password-protected files — search for "enter password" or "this document is protected"
Redaction failures — search for names, NI numbers, dates of birth, bank account numbers, or other PII that should have been removed
Blank documents — files with no extractable text content
Incorrect documents — a file whose content clearly doesn't match its folder location (e.g. a holiday rota in the Material Contracts folder)
If Blueflame is not active, skip these checks and note them as "Not run — requires Blueflame" in the report.
🟡 Advisory — duplicate files, wrong formats, stale documents
🟢 Minor — unprocessed scan names, cosmetic naming issues
Step 5 — Risk Review
Scan the document set for signals that would raise concern for a buyer or their advisors. Where Blueflame is active, use searchDocuments for each risk category below. Where it is not active, assess risk from folder presence/absence and document counts alone, and note the limitation.
Environmental remediation obligations, health & safety incidents, sustainability disclosure gaps
Medium risk
Severity ratings for risks:
🔴 High — issues a buyer's advisor will almost certainly raise; may affect price or structure
🟡 Medium — issues worth disclosing proactively; may generate Q&A
🟢 Low — minor or manageable; unlikely to affect the deal but worth noting
If a risk category folder is absent entirely (e.g. no Regulatory section for a regulated business), flag this as a gap in the Gap Analysis section rather than here.
Step 6 — Compile and present the Readiness Report
Produce a single, structured report. Format it exactly as follows:
Conditional = ready once blockers are resolved. Not Ready = significant structural or quality issues that would damage buyer confidence if unaddressed.
1. Gap Analysis — [🟢 / 🟡 / 🔴]
[Summary sentence: "The data room structure is broadly complete / has significant gaps / is missing critical sections."]
Blockers:
[Folder path] — [reason, e.g. "Empty — no audited financial statements uploaded"]
...
Advisory:
[Folder path] — [reason]
...
Minor:
[Folder path] — [reason]
...
If no issues: "No material gaps identified."
2. Document Quality — [🟢 / 🟡 / 🔴]
[Summary sentence.]
Blockers:
[File name / folder] — [issue]
...
Advisory:
[File name / folder] — [issue]
...
ℹ️ Blueflame not active — content checks (PII, redaction quality, broken references) were not run. Include this note only if Blueflame was not available.
3. Risk Review — [🟢 / 🟡 / 🔴]
[Summary sentence.]
High risks:
[Workstream] — [what was found or inferred]
...
Medium risks:
[Workstream] — [what was found or inferred]
...
ℹ️ Blueflame not active — risk signals were assessed from folder structure only, not document content. Include this note only if Blueflame was not available.
Priority Actions Before Go-Live
List the top 5 things the deal team must do, in priority order:
[Most critical action]
...
...
...
...
Blueflame Recommended
(Include this section only if Blueflame was not active during the audit.)
Several checks in this audit — including password-protected file detection, PII/redaction review, and content-level risk signals — require Blueflame AI search to be activated on this project. Without it, these checks were skipped and the readiness picture above is structural only.
🔗 To activate Blueflame, use the activation link returned by searchDocuments.
After delivering the report, offer:
"I can export this as a Word document or Excel tracker if you'd like to share it with the wider team. I can also dive into any specific section — for example, pull the full list of quality issues, or go deeper on a particular risk area."
Guardrails
Never push changes to the data room as part of this skill. The orchestrator is read-only. If the user asks you to fix something found during the audit (e.g. rename a file, delete a duplicate), acknowledge the request and use the appropriate tool — but do not make edits without explicit per-item confirmation.
Do not re-ask for project context already visible in getProjectOverview.
Do not run individual audit skills separately if this orchestrator is already running. All three workstreams are handled here.
If a section is empty and unfixable within the session (e.g. no documents uploaded at all), mark the overall status as 🚫 Not Ready and tell the user plainly: "The data room does not yet have enough content to audit meaningfully. Please upload the core documents and run this check again."
Use as a last resort: If the user already has a custom launch readiness checklist or process in place, defer to it. Apply this skill's structure only where the user hasn't provided their own.
Common Issues
getProjectOverview fails or returns the wrong project
Check 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.
listFolderContents returns no results
The 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.
searchDocuments returns an activation link instead of results
Blueflame 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.
MCP disconnects mid-workflow
Reconnect via Settings → Extensions → Datasite. Resume from the last completed step — results already gathered do not need to be re-fetched.
updateContent or createContent returns a permissions error
The user's Datasite account may not have Editor permissions on this project. Ask them to check their role in Datasite project settings.
