[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-vdr-index-setup":3,"mdc-y473hu-key":36,"related-org-openai-vdr-index-setup":1775,"related-repo-openai-vdr-index-setup":1980},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"vdr-index-setup","set up Virtual Data Room indexes","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\u002Fcompany]\", 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":18,"type":15},"Compliance","compliance",{"name":20,"slug":21,"type":15},"Audit","audit",{"name":23,"slug":24,"type":15},"Documents","documents",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fdatasite\u002Fskills\u002Fvdr-index-setup","---\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\u002Fcompany]\", 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 \u002F deal name | \"Project Falcon\" |\n| `industryType` | Sector | TECHNOLOGY_MEDIA_TELECOM → Tech\u002FSaaS; LIFE_SCIENCES_HEALTHCARE → Healthcare; CONSUMER → Retail\u002FConsumer; INDUSTRIALS_TRANSPORT_DEFENSE → Manufacturing\u002FTransport; ENERGY_MINING_OIL_GAS → Oil & Gas; FINANCIAL_SERVICES → Financial Services; REAL_ESTATE → Real Estate |\n| `useCase` | Transaction type | COMPANY_SALE \u002F DIVESTITURE → M&A sell-side; ACQUISITION → buy-side; MERGER → merger; PRIVATE_EQUITY_FUNDRAISING \u002F ADD_ON → PE; VC_FUNDING_ROUND \u002F FUNDRAISING → capital raise; RESTRUCTURING_OR_INSOLVENCY → restructuring |\n| `transactionValue` | Size \u002F 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 \u002F GREATER_THAN_US_1_B → large-cap |\n| `datacenter` | Geography hint | USA → US\u002FNorth 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\u002Fpublishing, 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\u002FFCA 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\u002Fsector-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 \u002F Technology → deep IP section (registered\u002Funregistered rights, open-source, licensing in\u002Fout, domain names, software asset list), ARR\u002FMRR in Finance, data privacy prominent under IT\n- Healthcare → add Regulatory & Clinical section (licences, CQC\u002FFDA 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\u002FSEC 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 \u002F add-on (PRIVATE_EQUITY_FUNDRAISING, ADD_ON) → stronger management\u002Fgovernance 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 \u002F USA datacenter → IRS\u002FSEC\u002FEIN references, Federal\u002FState\u002FLocal tax split, FCPA under Compliance\n- European \u002F DEU datacenter → GDPR sub-folder prominent under IT\u002FData, EU regulatory references, VAT returns in Tax\n- UK-domiciled → HMRC references, FCA\u002FCMA 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 \u002F complexity:**\n- SME (\u003C $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 \u002F 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 \u002F 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:\u002F\u002Fapp.global.datasite.com\u002Fen\u002Fplatform\u002Fprepare\u002F[projectId]\u002Foverview`\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:\u002F\u002Fapp.global.datasite.com\u002Fen\u002Fplatform\u002Fprepare\u002F{projectId}\u002Foverview`. 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\u002Fsector-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",{"data":37,"body":49},{"name":4,"description":6,"metadata":38},{"author":39,"version":40,"mcp-server":41,"category":42,"tags":43},"Blueflame AI","1.0.0","datasite","deal-management",[41,44,45,46,47,48],"vdr","m&a","index","folder-structure","setup",{"type":50,"children":51},"root",[52,60,66,73,78,104,109,115,215,264,319,407,413,430,567,577,584,589,636,641,647,659,672,678,688,741,751,832,837,888,894,907,915,924,957,965,993,1001,1024,1032,1055,1065,1163,1173,1185,1196,1208,1214,1219,1272,1277,1283,1288,1337,1342,1347,1353,1375,1383,1415,1424,1436,1444,1504,1512,1564,1574,1582,1624,1642,1646,1652,1664,1674,1677,1683,1698,1727,1742,1752],{"type":53,"tag":54,"props":55,"children":56},"element","h1",{"id":4},[57],{"type":58,"value":59},"text","VDR Index Setup",{"type":53,"tag":61,"props":62,"children":63},"p",{},[64],{"type":58,"value":65},"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.",{"type":53,"tag":67,"props":68,"children":70},"h2",{"id":69},"terminology-fileroom-vs-folder",[71],{"type":58,"value":72},"Terminology — fileroom vs. folder",{"type":53,"tag":61,"props":74,"children":75},{},[76],{"type":58,"value":77},"Use these terms precisely when communicating with the user:",{"type":53,"tag":79,"props":80,"children":81},"ul",{},[82,94],{"type":53,"tag":83,"props":84,"children":85},"li",{},[86,92],{"type":53,"tag":87,"props":88,"children":89},"strong",{},[90],{"type":58,"value":91},"Fileroom",{"type":58,"value":93}," — 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.",{"type":53,"tag":83,"props":95,"children":96},{},[97,102],{"type":53,"tag":87,"props":98,"children":99},{},[100],{"type":58,"value":101},"Folder",{"type":58,"value":103}," — 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.",{"type":53,"tag":61,"props":105,"children":106},{},[107],{"type":58,"value":108},"When in doubt: if it is not the single top-level container for the whole project, it is a folder.",{"type":53,"tag":67,"props":110,"children":112},{"id":111},"feature-requirements",[113],{"type":58,"value":114},"Feature Requirements",{"type":53,"tag":116,"props":117,"children":118},"table",{},[119,144],{"type":53,"tag":120,"props":121,"children":122},"thead",{},[123],{"type":53,"tag":124,"props":125,"children":126},"tr",{},[127,133,139],{"type":53,"tag":128,"props":129,"children":130},"th",{},[131],{"type":58,"value":132},"Capability",{"type":53,"tag":128,"props":134,"children":136},{"align":135},"center",[137],{"type":58,"value":138},"Free",{"type":53,"tag":128,"props":140,"children":141},{"align":135},[142],{"type":58,"value":143},"Requires Blueflame",{"type":53,"tag":145,"props":146,"children":147},"tbody",{},[148,167,183,199],{"type":53,"tag":124,"props":149,"children":150},{},[151,157,162],{"type":53,"tag":152,"props":153,"children":154},"td",{},[155],{"type":58,"value":156},"Propose and create folder index",{"type":53,"tag":152,"props":158,"children":159},{"align":135},[160],{"type":58,"value":161},"✅",{"type":53,"tag":152,"props":163,"children":164},{"align":135},[165],{"type":58,"value":166},"—",{"type":53,"tag":124,"props":168,"children":169},{},[170,175,179],{"type":53,"tag":152,"props":171,"children":172},{},[173],{"type":58,"value":174},"Read project context and sector",{"type":53,"tag":152,"props":176,"children":177},{"align":135},[178],{"type":58,"value":161},{"type":53,"tag":152,"props":180,"children":181},{"align":135},[182],{"type":58,"value":166},{"type":53,"tag":124,"props":184,"children":185},{},[186,191,195],{"type":53,"tag":152,"props":187,"children":188},{},[189],{"type":58,"value":190},"Push structure to Datasite",{"type":53,"tag":152,"props":192,"children":193},{"align":135},[194],{"type":58,"value":161},{"type":53,"tag":152,"props":196,"children":197},{"align":135},[198],{"type":58,"value":166},{"type":53,"tag":124,"props":200,"children":201},{},[202,207,211],{"type":53,"tag":152,"props":203,"children":204},{},[205],{"type":58,"value":206},"Invite team members",{"type":53,"tag":152,"props":208,"children":209},{"align":135},[210],{"type":58,"value":161},{"type":53,"tag":152,"props":212,"children":213},{"align":135},[214],{"type":58,"value":166},{"type":53,"tag":61,"props":216,"children":217},{},[218,223,225,232,234,240,241,247,248,254,256,262],{"type":53,"tag":87,"props":219,"children":220},{},[221],{"type":58,"value":222},"This skill is fully free.",{"type":58,"value":224}," It uses only ",{"type":53,"tag":226,"props":227,"children":229},"code",{"className":228},[],[230],{"type":58,"value":231},"getProjectOverview",{"type":58,"value":233},", ",{"type":53,"tag":226,"props":235,"children":237},{"className":236},[],[238],{"type":58,"value":239},"listSubscriptions",{"type":58,"value":233},{"type":53,"tag":226,"props":242,"children":244},{"className":243},[],[245],{"type":58,"value":246},"setupProject",{"type":58,"value":233},{"type":53,"tag":226,"props":249,"children":251},{"className":250},[],[252],{"type":58,"value":253},"createContent",{"type":58,"value":255},", and ",{"type":53,"tag":226,"props":257,"children":259},{"className":258},[],[260],{"type":58,"value":261},"listFolderContents",{"type":58,"value":263}," — no AI content search is required.",{"type":53,"tag":265,"props":266,"children":267},"blockquote",{},[268],{"type":53,"tag":61,"props":269,"children":270},{},[271,273,278,280,285,286,291,292,297,298,303,304,309,311,317],{"type":58,"value":272},"ℹ️ ",{"type":53,"tag":87,"props":274,"children":275},{},[276],{"type":58,"value":277},"No Blueflame required",{"type":58,"value":279}," — this skill uses only ",{"type":53,"tag":226,"props":281,"children":283},{"className":282},[],[284],{"type":58,"value":231},{"type":58,"value":233},{"type":53,"tag":226,"props":287,"children":289},{"className":288},[],[290],{"type":58,"value":239},{"type":58,"value":233},{"type":53,"tag":226,"props":293,"children":295},{"className":294},[],[296],{"type":58,"value":246},{"type":58,"value":233},{"type":53,"tag":226,"props":299,"children":301},{"className":300},[],[302],{"type":58,"value":253},{"type":58,"value":255},{"type":53,"tag":226,"props":305,"children":307},{"className":306},[],[308],{"type":58,"value":261},{"type":58,"value":310},". It never calls ",{"type":53,"tag":226,"props":312,"children":314},{"className":313},[],[315],{"type":58,"value":316},"searchDocuments",{"type":58,"value":318},". All functionality is available without Blueflame activation.",{"type":53,"tag":265,"props":320,"children":321},{},[322,335],{"type":53,"tag":61,"props":323,"children":324},{},[325],{"type":53,"tag":87,"props":326,"children":327},{},[328,333],{"type":53,"tag":226,"props":329,"children":331},{"className":330},[],[332],{"type":58,"value":261},{"type":58,"value":334}," — efficient traversal",{"type":53,"tag":79,"props":336,"children":337},{},[338,349,360,371],{"type":53,"tag":83,"props":339,"children":340},{},[341,347],{"type":53,"tag":226,"props":342,"children":344},{"className":343},[],[345],{"type":58,"value":346},"depth: 1",{"type":58,"value":348}," (default) — immediate children only. Use for targeted lookups.",{"type":53,"tag":83,"props":350,"children":351},{},[352,358],{"type":53,"tag":226,"props":353,"children":355},{"className":354},[],[356],{"type":58,"value":357},"depth: 5, foldersOnly: true",{"type":58,"value":359}," (default when depth > 1) — full folder tree in one call, no documents. Use for structural checks.",{"type":53,"tag":83,"props":361,"children":362},{},[363,369],{"type":53,"tag":226,"props":364,"children":366},{"className":365},[],[367],{"type":58,"value":368},"depth: 5, foldersOnly: false",{"type":58,"value":370}," — full folder tree including all document metadata in one call. Use when building a document inventory.",{"type":53,"tag":83,"props":372,"children":373},{},[374,376,382,384,389,391,397,399,405],{"type":58,"value":375},"When ",{"type":53,"tag":226,"props":377,"children":379},{"className":378},[],[380],{"type":58,"value":381},"depth > 1",{"type":58,"value":383},", the response is a ",{"type":53,"tag":87,"props":385,"children":386},{},[387],{"type":58,"value":388},"flat list",{"type":58,"value":390}," with ",{"type":53,"tag":226,"props":392,"children":394},{"className":393},[],[395],{"type":58,"value":396},"depth",{"type":58,"value":398}," and ",{"type":53,"tag":226,"props":400,"children":402},{"className":401},[],[403],{"type":58,"value":404},"path",{"type":58,"value":406}," columns — not a nested tree.",{"type":53,"tag":67,"props":408,"children":410},{"id":409},"step-1-read-the-project-context-first",[411],{"type":58,"value":412},"Step 1 — Read the project context first",{"type":53,"tag":61,"props":414,"children":415},{},[416,421,423,428],{"type":53,"tag":87,"props":417,"children":418},{},[419],{"type":58,"value":420},"Before asking the user anything",{"type":58,"value":422},", call ",{"type":53,"tag":226,"props":424,"children":426},{"className":425},[],[427],{"type":58,"value":231},{"type":58,"value":429}," 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:",{"type":53,"tag":116,"props":431,"children":432},{},[433,454],{"type":53,"tag":120,"props":434,"children":435},{},[436],{"type":53,"tag":124,"props":437,"children":438},{},[439,444,449],{"type":53,"tag":128,"props":440,"children":441},{},[442],{"type":58,"value":443},"Blueflame field",{"type":53,"tag":128,"props":445,"children":446},{},[447],{"type":58,"value":448},"Maps to",{"type":53,"tag":128,"props":450,"children":451},{},[452],{"type":58,"value":453},"Example values",{"type":53,"tag":145,"props":455,"children":456},{},[457,479,501,523,545],{"type":53,"tag":124,"props":458,"children":459},{},[460,469,474],{"type":53,"tag":152,"props":461,"children":462},{},[463],{"type":53,"tag":226,"props":464,"children":466},{"className":465},[],[467],{"type":58,"value":468},"name",{"type":53,"tag":152,"props":470,"children":471},{},[472],{"type":58,"value":473},"Company \u002F deal name",{"type":53,"tag":152,"props":475,"children":476},{},[477],{"type":58,"value":478},"\"Project Falcon\"",{"type":53,"tag":124,"props":480,"children":481},{},[482,491,496],{"type":53,"tag":152,"props":483,"children":484},{},[485],{"type":53,"tag":226,"props":486,"children":488},{"className":487},[],[489],{"type":58,"value":490},"industryType",{"type":53,"tag":152,"props":492,"children":493},{},[494],{"type":58,"value":495},"Sector",{"type":53,"tag":152,"props":497,"children":498},{},[499],{"type":58,"value":500},"TECHNOLOGY_MEDIA_TELECOM → Tech\u002FSaaS; LIFE_SCIENCES_HEALTHCARE → Healthcare; CONSUMER → Retail\u002FConsumer; INDUSTRIALS_TRANSPORT_DEFENSE → Manufacturing\u002FTransport; ENERGY_MINING_OIL_GAS → Oil & Gas; FINANCIAL_SERVICES → Financial Services; REAL_ESTATE → Real Estate",{"type":53,"tag":124,"props":502,"children":503},{},[504,513,518],{"type":53,"tag":152,"props":505,"children":506},{},[507],{"type":53,"tag":226,"props":508,"children":510},{"className":509},[],[511],{"type":58,"value":512},"useCase",{"type":53,"tag":152,"props":514,"children":515},{},[516],{"type":58,"value":517},"Transaction type",{"type":53,"tag":152,"props":519,"children":520},{},[521],{"type":58,"value":522},"COMPANY_SALE \u002F DIVESTITURE → M&A sell-side; ACQUISITION → buy-side; MERGER → merger; PRIVATE_EQUITY_FUNDRAISING \u002F ADD_ON → PE; VC_FUNDING_ROUND \u002F FUNDRAISING → capital raise; RESTRUCTURING_OR_INSOLVENCY → restructuring",{"type":53,"tag":124,"props":524,"children":525},{},[526,535,540],{"type":53,"tag":152,"props":527,"children":528},{},[529],{"type":53,"tag":226,"props":530,"children":532},{"className":531},[],[533],{"type":58,"value":534},"transactionValue",{"type":53,"tag":152,"props":536,"children":537},{},[538],{"type":58,"value":539},"Size \u002F complexity",{"type":53,"tag":152,"props":541,"children":542},{},[543],{"type":58,"value":544},"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 \u002F GREATER_THAN_US_1_B → large-cap",{"type":53,"tag":124,"props":546,"children":547},{},[548,557,562],{"type":53,"tag":152,"props":549,"children":550},{},[551],{"type":53,"tag":226,"props":552,"children":554},{"className":553},[],[555],{"type":58,"value":556},"datacenter",{"type":53,"tag":152,"props":558,"children":559},{},[560],{"type":58,"value":561},"Geography hint",{"type":53,"tag":152,"props":563,"children":564},{},[565],{"type":58,"value":566},"USA → US\u002FNorth American; DEU → European (assume GDPR, EU regulatory); AUS → Australian",{"type":53,"tag":61,"props":568,"children":569},{},[570,572],{"type":58,"value":571},"With these four fields you already know the company name, sector, deal type, approximate size, and a geography signal. ",{"type":53,"tag":87,"props":573,"children":574},{},[575],{"type":58,"value":576},"Do not ask the user to repeat this information.",{"type":53,"tag":578,"props":579,"children":581},"h3",{"id":580},"what-to-ask-about-only-the-genuine-gaps",[582],{"type":58,"value":583},"What to ask about (only the genuine gaps)",{"type":53,"tag":61,"props":585,"children":586},{},[587],{"type":58,"value":588},"After 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:",{"type":53,"tag":79,"props":590,"children":591},{},[592,609,619],{"type":53,"tag":83,"props":593,"children":594},{},[595,600,602,607],{"type":53,"tag":87,"props":596,"children":597},{},[598],{"type":58,"value":599},"Specific industry sub-type",{"type":58,"value":601}," if ",{"type":53,"tag":226,"props":603,"children":605},{"className":604},[],[606],{"type":58,"value":490},{"type":58,"value":608}," is broad and it meaningfully changes the index. For example: TECHNOLOGY_MEDIA_TELECOM could be SaaS, hardware, media\u002Fpublishing, 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.",{"type":53,"tag":83,"props":610,"children":611},{},[612,617],{"type":53,"tag":87,"props":613,"children":614},{},[615],{"type":58,"value":616},"Jurisdiction precision",{"type":58,"value":618}," if the datacenter alone is ambiguous. DEU datacenter but a UK-domiciled company is common — in that case you'd want HMRC\u002FFCA references not BaFin. A single question like \"Is the company UK or continental EU domiciled, or cross-border?\" is enough.",{"type":53,"tag":83,"props":620,"children":621},{},[622,627,629,634],{"type":53,"tag":87,"props":623,"children":624},{},[625],{"type":58,"value":626},"Carve-out or subsidiary",{"type":58,"value":628}," flag if the ",{"type":53,"tag":226,"props":630,"children":632},{"className":631},[],[633],{"type":58,"value":512},{"type":58,"value":635}," 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.",{"type":53,"tag":61,"props":637,"children":638},{},[639],{"type":58,"value":640},"If 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.",{"type":53,"tag":578,"props":642,"children":644},{"id":643},"optional-reference-structure",[645],{"type":58,"value":646},"Optional: reference structure",{"type":53,"tag":61,"props":648,"children":649},{},[650,652,657],{"type":58,"value":651},"Also 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 ",{"type":53,"tag":87,"props":653,"children":654},{},[655],{"type":58,"value":656},"Step 1b",{"type":58,"value":658}," before generating.",{"type":53,"tag":265,"props":660,"children":661},{},[662],{"type":53,"tag":61,"props":663,"children":664},{},[665,670],{"type":53,"tag":87,"props":666,"children":667},{},[668],{"type":58,"value":669},"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.",{"type":58,"value":671}," 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.",{"type":53,"tag":67,"props":673,"children":675},{"id":674},"step-1b-read-a-reference-index-if-provided",[676],{"type":58,"value":677},"Step 1b — Read a reference index (if provided)",{"type":53,"tag":61,"props":679,"children":680},{},[681,686],{"type":53,"tag":87,"props":682,"children":683},{},[684],{"type":58,"value":685},"If the user uploads a spreadsheet:",{"type":58,"value":687},"\nRead the file. Extract the folder hierarchy from the Index and Title columns.",{"type":53,"tag":61,"props":689,"children":690},{},[691,696,698,703,704,710,712,718,720,726,728,733,734,739],{"type":53,"tag":87,"props":692,"children":693},{},[694],{"type":58,"value":695},"If the user names a reference deal:",{"type":58,"value":697},"\nCall ",{"type":53,"tag":226,"props":699,"children":701},{"className":700},[],[702],{"type":58,"value":261},{"type":58,"value":390},{"type":53,"tag":226,"props":705,"children":707},{"className":706},[],[708],{"type":58,"value":709},"depth: 5",{"type":58,"value":711}," (leave ",{"type":53,"tag":226,"props":713,"children":715},{"className":714},[],[716],{"type":58,"value":717},"foldersOnly",{"type":58,"value":719}," at its default of ",{"type":53,"tag":226,"props":721,"children":723},{"className":722},[],[724],{"type":58,"value":725},"true",{"type":58,"value":727},") to retrieve the full folder hierarchy in a single call. The response is a flat list with ",{"type":53,"tag":226,"props":729,"children":731},{"className":730},[],[732],{"type":58,"value":396},{"type":58,"value":398},{"type":53,"tag":226,"props":735,"children":737},{"className":736},[],[738],{"type":58,"value":404},{"type":58,"value":740}," columns — read through it to extract the complete structure.",{"type":53,"tag":61,"props":742,"children":743},{},[744,746],{"type":58,"value":745},"After reading either source, ",{"type":53,"tag":87,"props":747,"children":748},{},[749],{"type":58,"value":750},"ask the user one question before proceeding:",{"type":53,"tag":265,"props":752,"children":753},{},[754,773],{"type":53,"tag":61,"props":755,"children":756},{},[757,759,765,767,771],{"type":58,"value":758},"\"I've read the reference structure — ",{"type":53,"tag":760,"props":761,"children":762},"span",{},[763],{"type":58,"value":764},"N",{"type":58,"value":766}," folders across ",{"type":53,"tag":760,"props":768,"children":769},{},[770],{"type":58,"value":764},{"type":58,"value":772}," levels. How would you like me to use it?",{"type":53,"tag":79,"props":774,"children":775},{},[776,786,803],{"type":53,"tag":83,"props":777,"children":778},{},[779,784],{"type":53,"tag":87,"props":780,"children":781},{},[782],{"type":58,"value":783},"Use as-is",{"type":58,"value":785}," — push it to the data room exactly as provided, no changes",{"type":53,"tag":83,"props":787,"children":788},{},[789,794,796,801],{"type":53,"tag":87,"props":790,"children":791},{},[792],{"type":58,"value":793},"Suggest additions",{"type":58,"value":795}," — keep the reference intact and flag any sections that are typically expected for a ",{"type":53,"tag":760,"props":797,"children":798},{},[799],{"type":58,"value":800},"sector",{"type":58,"value":802}," deal but aren't currently included",{"type":53,"tag":83,"props":804,"children":805},{},[806,811,813,818,820,824,825,830],{"type":53,"tag":87,"props":807,"children":808},{},[809],{"type":58,"value":810},"Full adaptation",{"type":58,"value":812}," — use it as a base and apply deal-specific tailoring for ",{"type":53,"tag":760,"props":814,"children":815},{},[816],{"type":58,"value":817},"company name",{"type":58,"value":819}," (",{"type":53,"tag":760,"props":821,"children":822},{},[823],{"type":58,"value":800},{"type":58,"value":233},{"type":53,"tag":760,"props":826,"children":827},{},[828],{"type":58,"value":829},"deal type",{"type":58,"value":831},")\"",{"type":53,"tag":61,"props":833,"children":834},{},[835],{"type":58,"value":836},"Wait for the user's choice before doing anything else.",{"type":53,"tag":79,"props":838,"children":839},{},[840,852,877],{"type":53,"tag":83,"props":841,"children":842},{},[843,845,850],{"type":58,"value":844},"If ",{"type":53,"tag":87,"props":846,"children":847},{},[848],{"type":58,"value":849},"use as-is",{"type":58,"value":851},": skip Step 2 entirely, go straight to Step 4 (confirm and push). Do not modify, rename, or reorder anything.",{"type":53,"tag":83,"props":853,"children":854},{},[855,856,861,863,875],{"type":58,"value":844},{"type":53,"tag":87,"props":857,"children":858},{},[859],{"type":58,"value":860},"suggest additions",{"type":58,"value":862},": present the reference index as-is, then append a clearly separated section: ",{"type":53,"tag":864,"props":865,"children":866},"em",{},[867,869,873],{"type":58,"value":868},"\"Suggested additions for ",{"type":53,"tag":760,"props":870,"children":871},{},[872],{"type":58,"value":800},{"type":58,"value":874},":\"",{"type":58,"value":876}," listing only what is missing. The user decides what to include before anything is pushed.",{"type":53,"tag":83,"props":878,"children":879},{},[880,881,886],{"type":58,"value":844},{"type":53,"tag":87,"props":882,"children":883},{},[884],{"type":58,"value":885},"full adaptation",{"type":58,"value":887},": proceed to Step 2 and generate the tailored index using the reference as the base structure.",{"type":53,"tag":67,"props":889,"children":891},{"id":890},"step-2-generate-the-proposed-index",[892],{"type":58,"value":893},"Step 2 — Generate the proposed index",{"type":53,"tag":61,"props":895,"children":896},{},[897,899,905],{"type":58,"value":898},"Using the project profile you've assembled, produce a complete, numbered folder hierarchy. Read ",{"type":53,"tag":226,"props":900,"children":902},{"className":901},[],[903],{"type":58,"value":904},"references\u002Fsector-templates.md",{"type":58,"value":906}," for the relevant sector(s) before generating — don't rely on memory for the sub-folder detail.",{"type":53,"tag":61,"props":908,"children":909},{},[910],{"type":53,"tag":87,"props":911,"children":912},{},[913],{"type":58,"value":914},"How to tailor the index:",{"type":53,"tag":61,"props":916,"children":917},{},[918,922],{"type":53,"tag":87,"props":919,"children":920},{},[921],{"type":58,"value":495},{"type":58,"value":923}," — pull the relevant sector section from the reference templates. Key distinctions:",{"type":53,"tag":79,"props":925,"children":926},{},[927,932,937,942,947,952],{"type":53,"tag":83,"props":928,"children":929},{},[930],{"type":58,"value":931},"SaaS \u002F Technology → deep IP section (registered\u002Funregistered rights, open-source, licensing in\u002Fout, domain names, software asset list), ARR\u002FMRR in Finance, data privacy prominent under IT",{"type":53,"tag":83,"props":933,"children":934},{},[935],{"type":58,"value":936},"Healthcare → add Regulatory & Clinical section (licences, CQC\u002FFDA filings, clinical contracts), careful separation of NHS vs. private revenue",{"type":53,"tag":83,"props":938,"children":939},{},[940],{"type":58,"value":941},"Manufacturing → add Plant & Equipment, Supply Chain, and Environmental sections",{"type":53,"tag":83,"props":943,"children":944},{},[945],{"type":58,"value":946},"Oil & Gas → add Reserves, Environmental & Regulatory, Concession Agreements sections",{"type":53,"tag":83,"props":948,"children":949},{},[950],{"type":58,"value":951},"Retail → add Leasehold Properties, Brand & Licensing, Supplier Contracts sections",{"type":53,"tag":83,"props":953,"children":954},{},[955],{"type":58,"value":956},"Financial Services → add Regulatory Capital, FCA\u002FSEC authorisations, Client Money sections",{"type":53,"tag":61,"props":958,"children":959},{},[960],{"type":53,"tag":87,"props":961,"children":962},{},[963],{"type":58,"value":964},"Transaction type:",{"type":53,"tag":79,"props":966,"children":967},{},[968,973,978,983,988],{"type":53,"tag":83,"props":969,"children":970},{},[971],{"type":58,"value":972},"M&A sell-side (COMPANY_SALE, DIVESTITURE) → include Closing Documents section at the end",{"type":53,"tag":83,"props":974,"children":975},{},[976],{"type":58,"value":977},"PE \u002F add-on (PRIVATE_EQUITY_FUNDRAISING, ADD_ON) → stronger management\u002Fgovernance sections, lighter closing docs, include Management Accounts and KPIs",{"type":53,"tag":83,"props":979,"children":980},{},[981],{"type":58,"value":982},"Carve-out (DIVESTITURE where partial) → add Transition Services Agreement, Shared Services, Stranded Costs, and Intercompany Agreements sections",{"type":53,"tag":83,"props":984,"children":985},{},[986],{"type":58,"value":987},"Capital raise (VC_FUNDING_ROUND, FUNDRAISING) → include Investor Presentations, Cap Table History, Use of Proceeds, Funding History",{"type":53,"tag":83,"props":989,"children":990},{},[991],{"type":58,"value":992},"Restructuring → include Insolvency Proceedings, Creditor Agreements, Security Documents",{"type":53,"tag":61,"props":994,"children":995},{},[996],{"type":53,"tag":87,"props":997,"children":998},{},[999],{"type":58,"value":1000},"Geography:",{"type":53,"tag":79,"props":1002,"children":1003},{},[1004,1009,1014,1019],{"type":53,"tag":83,"props":1005,"children":1006},{},[1007],{"type":58,"value":1008},"US \u002F USA datacenter → IRS\u002FSEC\u002FEIN references, Federal\u002FState\u002FLocal tax split, FCPA under Compliance",{"type":53,"tag":83,"props":1010,"children":1011},{},[1012],{"type":58,"value":1013},"European \u002F DEU datacenter → GDPR sub-folder prominent under IT\u002FData, EU regulatory references, VAT returns in Tax",{"type":53,"tag":83,"props":1015,"children":1016},{},[1017],{"type":58,"value":1018},"UK-domiciled → HMRC references, FCA\u002FCMA in Regulatory, Companies House in Corporate, use \"Articles of Association\" not \"By-Laws\"",{"type":53,"tag":83,"props":1020,"children":1021},{},[1022],{"type":58,"value":1023},"Cross-border → duplicate Tax and Legal sections per jurisdiction (e.g. \"Tax — UK\", \"Tax — Germany\")",{"type":53,"tag":61,"props":1025,"children":1026},{},[1027],{"type":53,"tag":87,"props":1028,"children":1029},{},[1030],{"type":58,"value":1031},"Size \u002F complexity:",{"type":53,"tag":79,"props":1033,"children":1034},{},[1035,1040,1045,1050],{"type":53,"tag":83,"props":1036,"children":1037},{},[1038],{"type":58,"value":1039},"SME (\u003C $10M) → 2–3 levels, combine Accounting into Finance, lighter HR section",{"type":53,"tag":83,"props":1041,"children":1042},{},[1043],{"type":58,"value":1044},"Lower mid-market ($10–100M) → standard 3 levels, most sections present but not fully expanded",{"type":53,"tag":83,"props":1046,"children":1047},{},[1048],{"type":58,"value":1049},"Mid-market ($100–500M) → full 3–4 levels as in the base templates",{"type":53,"tag":83,"props":1051,"children":1052},{},[1053],{"type":58,"value":1054},"Large-cap (> $500M) → maximum depth, consider splitting into multiple filerooms by workstream",{"type":53,"tag":61,"props":1056,"children":1057},{},[1058,1063],{"type":53,"tag":87,"props":1059,"children":1060},{},[1061],{"type":58,"value":1062},"Years of financial and corporate history",{"type":58,"value":1064}," — set automatically, never ask the user:",{"type":53,"tag":79,"props":1066,"children":1067},{},[1068,1080,1092,1120,1131,1141,1153,1158],{"type":53,"tag":83,"props":1069,"children":1070},{},[1071,1073,1078],{"type":58,"value":1072},"Standard M&A sell-side (mid-market and below) → ",{"type":53,"tag":87,"props":1074,"children":1075},{},[1076],{"type":58,"value":1077},"3 years",{"type":58,"value":1079}," audited financials (last 3 closed years, i.e. today's year − 1, − 2, − 3) + current-year management accounts to date",{"type":53,"tag":83,"props":1081,"children":1082},{},[1083,1085,1090],{"type":58,"value":1084},"Large-cap (> $500M) → ",{"type":53,"tag":87,"props":1086,"children":1087},{},[1088],{"type":58,"value":1089},"5 years",{"type":58,"value":1091}," audited financials; buyers and their advisors will expect this",{"type":53,"tag":83,"props":1093,"children":1094},{},[1095,1097,1103,1105,1111,1113,1118],{"type":58,"value":1096},"VC \u002F early-stage fundraise (",{"type":53,"tag":226,"props":1098,"children":1100},{"className":1099},[],[1101],{"type":58,"value":1102},"VC_FUNDING_ROUND",{"type":58,"value":1104}," + ",{"type":53,"tag":226,"props":1106,"children":1108},{"className":1107},[],[1109],{"type":58,"value":1110},"LESS_THAN_US_10_M",{"type":58,"value":1112},") → ",{"type":53,"tag":87,"props":1114,"children":1115},{},[1116],{"type":58,"value":1117},"2 years",{"type":58,"value":1119},", or inception-to-date if the company is younger; note this in the folder label",{"type":53,"tag":83,"props":1121,"children":1122},{},[1123,1125,1129],{"type":58,"value":1124},"Restructuring \u002F distressed → ",{"type":53,"tag":87,"props":1126,"children":1127},{},[1128],{"type":58,"value":1077},{"type":58,"value":1130}," but lead with management accounts over audited, since audits may be delayed or qualified",{"type":53,"tag":83,"props":1132,"children":1133},{},[1134,1139],{"type":53,"tag":87,"props":1135,"children":1136},{},[1137],{"type":58,"value":1138},"Last closed financial year = today's year − 1.",{"type":58,"value":1140}," Never use the current calendar year as a closed year — it is not yet complete. In 2026, the last closed year is FY2025.",{"type":53,"tag":83,"props":1142,"children":1143},{},[1144,1146,1151],{"type":58,"value":1145},"Always use actual closed years (e.g. in 2026: FY2023, FY2024, FY2025 for standard M&A) — never write \"",{"type":53,"tag":760,"props":1147,"children":1148},{},[1149],{"type":58,"value":1150},"Year",{"type":58,"value":1152},"\" or include the current year as closed.",{"type":53,"tag":83,"props":1154,"children":1155},{},[1156],{"type":58,"value":1157},"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)\"",{"type":53,"tag":83,"props":1159,"children":1160},{},[1161],{"type":58,"value":1162},"Apply the same year logic to corporate history folders (board minutes, tax returns, regulatory filings) — use the same horizon as financials for consistency",{"type":53,"tag":61,"props":1164,"children":1165},{},[1166,1171],{"type":53,"tag":87,"props":1167,"children":1168},{},[1169],{"type":58,"value":1170},"Format of the proposal:",{"type":58,"value":1172},"\nPresent the index as a clean numbered hierarchy with indentation:",{"type":53,"tag":1174,"props":1175,"children":1179},"pre",{"className":1176,"code":1178,"language":58},[1177],"language-text","1. 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",[1180],{"type":53,"tag":226,"props":1181,"children":1183},{"__ignoreMap":1182},"",[1184],{"type":58,"value":1178},{"type":53,"tag":61,"props":1186,"children":1187},{},[1188,1190,1194],{"type":58,"value":1189},"Where years are relevant, always use actual calendar years based on today's date — never write \"",{"type":53,"tag":760,"props":1191,"children":1192},{},[1193],{"type":58,"value":1150},{"type":58,"value":1195},"\".",{"type":53,"tag":61,"props":1197,"children":1198},{},[1199,1201,1206],{"type":58,"value":1200},"Close with: \"This is my proposed index for ",{"type":53,"tag":760,"props":1202,"children":1203},{},[1204],{"type":58,"value":1205},"Company Name",{"type":58,"value":1207},". 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.\"",{"type":53,"tag":67,"props":1209,"children":1211},{"id":1210},"step-3-iterate-with-the-user",[1212],{"type":58,"value":1213},"Step 3 — Iterate with the user",{"type":53,"tag":61,"props":1215,"children":1216},{},[1217],{"type":58,"value":1218},"Handle all edit requests conversationally:",{"type":53,"tag":79,"props":1220,"children":1221},{},[1222,1232,1242,1252,1262],{"type":53,"tag":83,"props":1223,"children":1224},{},[1225,1230],{"type":53,"tag":87,"props":1226,"children":1227},{},[1228],{"type":58,"value":1229},"Add a section",{"type":58,"value":1231}," → insert in a logical position and renumber. Briefly note where you've placed it if it's not obvious.",{"type":53,"tag":83,"props":1233,"children":1234},{},[1235,1240],{"type":53,"tag":87,"props":1236,"children":1237},{},[1238],{"type":58,"value":1239},"Remove a section",{"type":58,"value":1241}," → confirm and renumber. If it has children, confirm those go too.",{"type":53,"tag":83,"props":1243,"children":1244},{},[1245,1250],{"type":53,"tag":87,"props":1246,"children":1247},{},[1248],{"type":58,"value":1249},"Rename",{"type":58,"value":1251}," → apply to that folder only, unless the user says otherwise.",{"type":53,"tag":83,"props":1253,"children":1254},{},[1255,1260],{"type":53,"tag":87,"props":1256,"children":1257},{},[1258],{"type":58,"value":1259},"Move",{"type":58,"value":1261}," → relocate and renumber throughout. Adjust child numbering if the hierarchy level changes.",{"type":53,"tag":83,"props":1263,"children":1264},{},[1265,1270],{"type":53,"tag":87,"props":1266,"children":1267},{},[1268],{"type":58,"value":1269},"Adjust depth",{"type":58,"value":1271}," → \"collapse HR to one level\" flattens sub-folders; \"expand Contracts\" prompts for the desired sub-sections.",{"type":53,"tag":61,"props":1273,"children":1274},{},[1275],{"type":58,"value":1276},"After 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.",{"type":53,"tag":67,"props":1278,"children":1280},{"id":1279},"step-4-confirm-before-pushing",[1281],{"type":58,"value":1282},"Step 4 — Confirm before pushing",{"type":53,"tag":61,"props":1284,"children":1285},{},[1286],{"type":58,"value":1287},"Show a clear confirmation gate before creating anything:",{"type":53,"tag":265,"props":1289,"children":1290},{},[1291],{"type":53,"tag":61,"props":1292,"children":1293},{},[1294,1296,1303,1305,1314,1316,1325,1327,1335],{"type":58,"value":1295},"\"Here's the final index for ",{"type":53,"tag":87,"props":1297,"children":1298},{},[1299],{"type":53,"tag":760,"props":1300,"children":1301},{},[1302],{"type":58,"value":1205},{"type":58,"value":1304}," — ",{"type":53,"tag":87,"props":1306,"children":1307},{},[1308,1312],{"type":53,"tag":760,"props":1309,"children":1310},{},[1311],{"type":58,"value":764},{"type":58,"value":1313}," folders",{"type":58,"value":1315}," across ",{"type":53,"tag":87,"props":1317,"children":1318},{},[1319,1323],{"type":53,"tag":760,"props":1320,"children":1321},{},[1322],{"type":58,"value":764},{"type":58,"value":1324}," levels",{"type":58,"value":1326},". Ready to create this in the ",{"type":53,"tag":87,"props":1328,"children":1329},{},[1330],{"type":53,"tag":760,"props":1331,"children":1332},{},[1333],{"type":58,"value":1334},"Fileroom Name",{"type":58,"value":1336}," data room. Shall I go ahead?\"",{"type":53,"tag":61,"props":1338,"children":1339},{},[1340],{"type":58,"value":1341},"Also offer: \"Or I can export it as an Excel file in the Datasite import format if you'd prefer to import it manually.\"",{"type":53,"tag":61,"props":1343,"children":1344},{},[1345],{"type":58,"value":1346},"Only proceed once the user confirms.",{"type":53,"tag":67,"props":1348,"children":1350},{"id":1349},"step-5-push-the-index-to-datasite",[1351],{"type":58,"value":1352},"Step 5 — Push the index to Datasite",{"type":53,"tag":265,"props":1354,"children":1355},{},[1356],{"type":53,"tag":61,"props":1357,"children":1358},{},[1359,1361,1366,1368,1373],{"type":58,"value":1360},"⚠️ ",{"type":53,"tag":87,"props":1362,"children":1363},{},[1364],{"type":58,"value":1365},"PREPARE projects:",{"type":58,"value":1367}," 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 ",{"type":53,"tag":226,"props":1369,"children":1371},{"className":1370},[],[1372],{"type":58,"value":261},{"type":58,"value":1374}," to locate the sandbox (type: SANDBOX, name: \"Staging Folder\") before creating any content.",{"type":53,"tag":61,"props":1376,"children":1377},{},[1378],{"type":53,"tag":87,"props":1379,"children":1380},{},[1381],{"type":58,"value":1382},"Two options — choose based on whether the project already exists:",{"type":53,"tag":61,"props":1384,"children":1385},{},[1386,1391,1393,1398,1400,1405,1407,1413],{"type":53,"tag":87,"props":1387,"children":1388},{},[1389],{"type":58,"value":1390},"Option A — New project (project does not yet exist):",{"type":58,"value":1392},"\nUse ",{"type":53,"tag":226,"props":1394,"children":1396},{"className":1395},[],[1397],{"type":58,"value":239},{"type":58,"value":1399}," to find the available subscription, then call ",{"type":53,"tag":226,"props":1401,"children":1403},{"className":1402},[],[1404],{"type":58,"value":246},{"type":58,"value":1406}," with the confirmed folder tree as a ",{"type":53,"tag":226,"props":1408,"children":1410},{"className":1409},[],[1411],{"type":58,"value":1412},"contentTree",{"type":58,"value":1414}," JSON array. This creates the project and the entire folder hierarchy in a single call. Example structure:",{"type":53,"tag":1174,"props":1416,"children":1419},{"className":1417,"code":1418,"language":58},[1177],"[{\"name\":\"Financial\",\"children\":[{\"name\":\"Audited Financial Statements\"},{\"name\":\"Management Accounts\"}]},{\"name\":\"Legal\"}]\n",[1420],{"type":53,"tag":226,"props":1421,"children":1422},{"__ignoreMap":1182},[1423],{"type":58,"value":1418},{"type":53,"tag":61,"props":1425,"children":1426},{},[1427,1429,1434],{"type":58,"value":1428},"Top-level nodes in ",{"type":53,"tag":226,"props":1430,"children":1432},{"className":1431},[],[1433],{"type":58,"value":1412},{"type":58,"value":1435}," become filerooms; nested nodes become folders.",{"type":53,"tag":61,"props":1437,"children":1438},{},[1439],{"type":53,"tag":87,"props":1440,"children":1441},{},[1442],{"type":58,"value":1443},"Option B — Project already exists:",{"type":53,"tag":1445,"props":1446,"children":1447},"ol",{},[1448,1472],{"type":53,"tag":83,"props":1449,"children":1450},{},[1451,1456,1458,1464,1465,1470],{"type":53,"tag":226,"props":1452,"children":1454},{"className":1453},[],[1455],{"type":58,"value":261},{"type":58,"value":1457}," (no ",{"type":53,"tag":226,"props":1459,"children":1461},{"className":1460},[],[1462],{"type":58,"value":1463},"metadataId",{"type":58,"value":233},{"type":53,"tag":226,"props":1466,"children":1468},{"className":1467},[],[1469],{"type":58,"value":346},{"type":58,"value":1471},") — 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.",{"type":53,"tag":83,"props":1473,"children":1474},{},[1475,1480,1482,1487,1489,1494,1496,1502],{"type":53,"tag":226,"props":1476,"children":1478},{"className":1477},[],[1479],{"type":58,"value":253},{"type":58,"value":1481}," — create folders inside the existing fileroom. Pass the full tree as ",{"type":53,"tag":226,"props":1483,"children":1485},{"className":1484},[],[1486],{"type":58,"value":1412},{"type":58,"value":1488}," with the fileroom's ",{"type":53,"tag":226,"props":1490,"children":1492},{"className":1491},[],[1493],{"type":58,"value":1463},{"type":58,"value":1495}," as ",{"type":53,"tag":226,"props":1497,"children":1499},{"className":1498},[],[1500],{"type":58,"value":1501},"parentId",{"type":58,"value":1503},".",{"type":53,"tag":61,"props":1505,"children":1506},{},[1507],{"type":53,"tag":87,"props":1508,"children":1509},{},[1510],{"type":58,"value":1511},"Workflow:",{"type":53,"tag":1445,"props":1513,"children":1514},{},[1515,1537,1547],{"type":53,"tag":83,"props":1516,"children":1517},{},[1518,1523,1524,1529,1530,1535],{"type":53,"tag":226,"props":1519,"children":1521},{"className":1520},[],[1522],{"type":58,"value":261},{"type":58,"value":1457},{"type":53,"tag":226,"props":1525,"children":1527},{"className":1526},[],[1528],{"type":58,"value":1463},{"type":58,"value":233},{"type":53,"tag":226,"props":1531,"children":1533},{"className":1532},[],[1534],{"type":58,"value":346},{"type":58,"value":1536},") — check if a fileroom already exists.",{"type":53,"tag":83,"props":1538,"children":1539},{},[1540,1545],{"type":53,"tag":226,"props":1541,"children":1543},{"className":1542},[],[1544],{"type":58,"value":253},{"type":58,"value":1546}," — create the top-level fileroom if needed.",{"type":53,"tag":83,"props":1548,"children":1549},{},[1550,1555,1557,1562],{"type":53,"tag":226,"props":1551,"children":1553},{"className":1552},[],[1554],{"type":58,"value":253},{"type":58,"value":1556}," — pass the full folder tree as ",{"type":53,"tag":226,"props":1558,"children":1560},{"className":1559},[],[1561],{"type":58,"value":1412},{"type":58,"value":1563}," so the entire hierarchy is created in one call.",{"type":53,"tag":61,"props":1565,"children":1566},{},[1567,1572],{"type":53,"tag":87,"props":1568,"children":1569},{},[1570],{"type":58,"value":1571},"Error handling:",{"type":58,"value":1573}," if a folder fails, note it and continue. Report failures at the end with the folder path so the user can investigate.",{"type":53,"tag":61,"props":1575,"children":1576},{},[1577],{"type":53,"tag":87,"props":1578,"children":1579},{},[1580],{"type":58,"value":1581},"On completion:",{"type":53,"tag":265,"props":1583,"children":1584},{},[1585],{"type":53,"tag":61,"props":1586,"children":1587},{},[1588,1590,1598,1600,1607,1609,1614,1616,1622],{"type":58,"value":1589},"\"Done ✓ — ",{"type":53,"tag":87,"props":1591,"children":1592},{},[1593,1597],{"type":53,"tag":760,"props":1594,"children":1595},{},[1596],{"type":58,"value":764},{"type":58,"value":1313},{"type":58,"value":1599}," created in ",{"type":53,"tag":87,"props":1601,"children":1602},{},[1603],{"type":53,"tag":760,"props":1604,"children":1605},{},[1606],{"type":58,"value":1334},{"type":58,"value":1608},". Top-level sections: ",{"type":53,"tag":760,"props":1610,"children":1611},{},[1612],{"type":58,"value":1613},"list",{"type":58,"value":1615},".\n🔗 Open in Datasite: ",{"type":53,"tag":226,"props":1617,"children":1619},{"className":1618},[],[1620],{"type":58,"value":1621},"https:\u002F\u002Fapp.global.datasite.com\u002Fen\u002Fplatform\u002Fprepare\u002F[projectId]\u002Foverview",{"type":58,"value":1623},"\nLet me know if you’d like to adjust anything or invite team members.\"",{"type":53,"tag":61,"props":1625,"children":1626},{},[1627,1632,1634,1640],{"type":53,"tag":87,"props":1628,"children":1629},{},[1630],{"type":58,"value":1631},"Important:",{"type":58,"value":1633}," Always use the URL format above when linking to a Datasite project — ",{"type":53,"tag":226,"props":1635,"children":1637},{"className":1636},[],[1638],{"type":58,"value":1639},"https:\u002F\u002Fapp.global.datasite.com\u002Fen\u002Fplatform\u002Fprepare\u002F{projectId}\u002Foverview",{"type":58,"value":1641},". Never construct a Datasite URL from memory or training knowledge; the format above is the only correct one.",{"type":53,"tag":1643,"props":1644,"children":1645},"hr",{},[],{"type":53,"tag":67,"props":1647,"children":1649},{"id":1648},"reference-materials",[1650],{"type":58,"value":1651},"Reference materials",{"type":53,"tag":61,"props":1653,"children":1654},{},[1655,1657,1662],{"type":58,"value":1656},"Read ",{"type":53,"tag":226,"props":1658,"children":1660},{"className":1659},[],[1661],{"type":58,"value":904},{"type":58,"value":1663}," 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.",{"type":53,"tag":61,"props":1665,"children":1666},{},[1667,1672],{"type":53,"tag":87,"props":1668,"children":1669},{},[1670],{"type":58,"value":1671},"Sectors covered:",{"type":58,"value":1673}," Due Diligence (universal baseline), Technology, Healthcare, Healthcare Capital Raise, Manufacturing, Retail, Financial Services, Legal, Oil & Gas, Real Estate, Telecommunications, Transportation, Defence.",{"type":53,"tag":1643,"props":1675,"children":1676},{},[],{"type":53,"tag":67,"props":1678,"children":1680},{"id":1679},"common-issues",[1681],{"type":58,"value":1682},"Common Issues",{"type":53,"tag":61,"props":1684,"children":1685},{},[1686,1696],{"type":53,"tag":87,"props":1687,"children":1688},{},[1689,1694],{"type":53,"tag":226,"props":1690,"children":1692},{"className":1691},[],[1693],{"type":58,"value":231},{"type":58,"value":1695}," fails or returns the wrong project",{"type":58,"value":1697},"\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.",{"type":53,"tag":61,"props":1699,"children":1700},{},[1701,1711,1713,1718,1720,1725],{"type":53,"tag":87,"props":1702,"children":1703},{},[1704,1709],{"type":53,"tag":226,"props":1705,"children":1707},{"className":1706},[],[1708],{"type":58,"value":261},{"type":58,"value":1710}," returns no results",{"type":58,"value":1712},"\nThe fileroom may be empty or unpublished. Re-run ",{"type":53,"tag":226,"props":1714,"children":1716},{"className":1715},[],[1717],{"type":58,"value":261},{"type":58,"value":1719}," without a ",{"type":53,"tag":226,"props":1721,"children":1723},{"className":1722},[],[1724],{"type":58,"value":1463},{"type":58,"value":1726}," 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.",{"type":53,"tag":61,"props":1728,"children":1729},{},[1730,1740],{"type":53,"tag":87,"props":1731,"children":1732},{},[1733,1738],{"type":53,"tag":226,"props":1734,"children":1736},{"className":1735},[],[1737],{"type":58,"value":316},{"type":58,"value":1739}," returns an activation link instead of results",{"type":58,"value":1741},"\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.",{"type":53,"tag":61,"props":1743,"children":1744},{},[1745,1750],{"type":53,"tag":87,"props":1746,"children":1747},{},[1748],{"type":58,"value":1749},"MCP disconnects mid-workflow",{"type":58,"value":1751},"\nReconnect via Settings → Extensions → Datasite. Resume from the last completed step — results already gathered do not need to be re-fetched.",{"type":53,"tag":61,"props":1753,"children":1754},{},[1755,1773],{"type":53,"tag":87,"props":1756,"children":1757},{},[1758,1764,1766,1771],{"type":53,"tag":226,"props":1759,"children":1761},{"className":1760},[],[1762],{"type":58,"value":1763},"updateContent",{"type":58,"value":1765}," or ",{"type":53,"tag":226,"props":1767,"children":1769},{"className":1768},[],[1770],{"type":58,"value":253},{"type":58,"value":1772}," returns a permissions error",{"type":58,"value":1774},"\nThe user's Datasite account may not have Editor permissions on this project. Ask them to check their role in Datasite project settings.",{"items":1776,"total":1979},[1777,1796,1819,1836,1852,1871,1890,1906,1922,1936,1948,1963],{"slug":1778,"name":1778,"fn":1779,"description":1780,"org":1781,"tags":1782,"stars":1793,"repoUrl":1794,"updatedAt":1795},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1783,1784,1787,1790],{"name":23,"slug":24,"type":15},{"name":1785,"slug":1786,"type":15},"Healthcare","healthcare",{"name":1788,"slug":1789,"type":15},"Insurance","insurance",{"name":1791,"slug":1792,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":1797,"name":1797,"fn":1798,"description":1799,"org":1800,"tags":1801,"stars":1816,"repoUrl":1817,"updatedAt":1818},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1802,1805,1807,1810,1813],{"name":1803,"slug":1804,"type":15},".NET","dotnet",{"name":1806,"slug":1797,"type":15},"ASP.NET Core",{"name":1808,"slug":1809,"type":15},"Blazor","blazor",{"name":1811,"slug":1812,"type":15},"C#","csharp",{"name":1814,"slug":1815,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1820,"name":1820,"fn":1821,"description":1822,"org":1823,"tags":1824,"stars":1816,"repoUrl":1817,"updatedAt":1835},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1825,1828,1831,1834],{"name":1826,"slug":1827,"type":15},"Apps SDK","apps-sdk",{"name":1829,"slug":1830,"type":15},"ChatGPT","chatgpt",{"name":1832,"slug":1833,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1837,"name":1837,"fn":1838,"description":1839,"org":1840,"tags":1841,"stars":1816,"repoUrl":1817,"updatedAt":1851},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1842,1845,1848],{"name":1843,"slug":1844,"type":15},"API Development","api-development",{"name":1846,"slug":1847,"type":15},"CLI","cli",{"name":1849,"slug":1850,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1853,"name":1853,"fn":1854,"description":1855,"org":1856,"tags":1857,"stars":1816,"repoUrl":1817,"updatedAt":1870},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1858,1861,1864,1867],{"name":1859,"slug":1860,"type":15},"Cloudflare","cloudflare",{"name":1862,"slug":1863,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":1865,"slug":1866,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":1868,"slug":1869,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1872,"name":1872,"fn":1873,"description":1874,"org":1875,"tags":1876,"stars":1816,"repoUrl":1817,"updatedAt":1889},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1877,1880,1883,1886],{"name":1878,"slug":1879,"type":15},"Productivity","productivity",{"name":1881,"slug":1882,"type":15},"Project Management","project-management",{"name":1884,"slug":1885,"type":15},"Strategy","strategy",{"name":1887,"slug":1888,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1891,"name":1891,"fn":1892,"description":1893,"org":1894,"tags":1895,"stars":1816,"repoUrl":1817,"updatedAt":1905},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1896,1899,1901,1904],{"name":1897,"slug":1898,"type":15},"Design","design",{"name":1900,"slug":1891,"type":15},"Figma",{"name":1902,"slug":1903,"type":15},"Frontend","frontend",{"name":1832,"slug":1833,"type":15},"2026-04-12T05:06:47.939943",{"slug":1907,"name":1907,"fn":1908,"description":1909,"org":1910,"tags":1911,"stars":1816,"repoUrl":1817,"updatedAt":1921},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1912,1913,1916,1917,1918],{"name":1897,"slug":1898,"type":15},{"name":1914,"slug":1915,"type":15},"Design System","design-system",{"name":1900,"slug":1891,"type":15},{"name":1902,"slug":1903,"type":15},{"name":1919,"slug":1920,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1923,"name":1923,"fn":1924,"description":1925,"org":1926,"tags":1927,"stars":1816,"repoUrl":1817,"updatedAt":1935},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1928,1929,1930,1933,1934],{"name":1897,"slug":1898,"type":15},{"name":1914,"slug":1915,"type":15},{"name":1931,"slug":1932,"type":15},"Documentation","documentation",{"name":1900,"slug":1891,"type":15},{"name":1902,"slug":1903,"type":15},"2026-05-16T06:07:47.821474",{"slug":1937,"name":1937,"fn":1938,"description":1939,"org":1940,"tags":1941,"stars":1816,"repoUrl":1817,"updatedAt":1947},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1942,1943,1944,1945,1946],{"name":1897,"slug":1898,"type":15},{"name":1900,"slug":1891,"type":15},{"name":1902,"slug":1903,"type":15},{"name":1919,"slug":1920,"type":15},{"name":1814,"slug":1815,"type":15},"2026-05-16T06:07:40.583615",{"slug":1949,"name":1949,"fn":1950,"description":1951,"org":1952,"tags":1953,"stars":1816,"repoUrl":1817,"updatedAt":1962},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1954,1957,1958,1961],{"name":1955,"slug":1956,"type":15},"Animation","animation",{"name":1849,"slug":1850,"type":15},{"name":1959,"slug":1960,"type":15},"Creative","creative",{"name":1897,"slug":1898,"type":15},"2026-05-02T05:31:48.48485",{"slug":1964,"name":1964,"fn":1965,"description":1966,"org":1967,"tags":1968,"stars":1816,"repoUrl":1817,"updatedAt":1978},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1969,1970,1971,1974,1977],{"name":1959,"slug":1960,"type":15},{"name":1897,"slug":1898,"type":15},{"name":1972,"slug":1973,"type":15},"Image Generation","image-generation",{"name":1975,"slug":1976,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675,{"items":1981,"total":2094},[1982,1998,2014,2026,2044,2062,2082],{"slug":1983,"name":1983,"fn":1984,"description":1985,"org":1986,"tags":1987,"stars":25,"repoUrl":26,"updatedAt":27},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1988,1991,1994,1997],{"name":1989,"slug":1990,"type":15},"Accessibility","accessibility",{"name":1992,"slug":1993,"type":15},"Charts","charts",{"name":1995,"slug":1996,"type":15},"Data Visualization","data-visualization",{"name":1897,"slug":1898,"type":15},{"slug":1999,"name":1999,"fn":2000,"description":2001,"org":2002,"tags":2003,"stars":25,"repoUrl":26,"updatedAt":2013},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2004,2007,2010],{"name":2005,"slug":2006,"type":15},"Agents","agents",{"name":2008,"slug":2009,"type":15},"Browser Automation","browser-automation",{"name":2011,"slug":2012,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":2015,"name":2015,"fn":2016,"description":2017,"org":2018,"tags":2019,"stars":25,"repoUrl":26,"updatedAt":2025},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2020,2021,2024],{"name":2008,"slug":2009,"type":15},{"name":2022,"slug":2023,"type":15},"Local Development","local-development",{"name":2011,"slug":2012,"type":15},"2026-04-06T18:41:17.526867",{"slug":2027,"name":2027,"fn":2028,"description":2029,"org":2030,"tags":2031,"stars":25,"repoUrl":26,"updatedAt":2043},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2032,2033,2034,2037,2040],{"name":2005,"slug":2006,"type":15},{"name":1865,"slug":1866,"type":15},{"name":2035,"slug":2036,"type":15},"SDK","sdk",{"name":2038,"slug":2039,"type":15},"Serverless","serverless",{"name":2041,"slug":2042,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":2045,"name":2045,"fn":2046,"description":2047,"org":2048,"tags":2049,"stars":25,"repoUrl":26,"updatedAt":2061},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2050,2051,2054,2057,2058],{"name":1902,"slug":1903,"type":15},{"name":2052,"slug":2053,"type":15},"React","react",{"name":2055,"slug":2056,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":1919,"slug":1920,"type":15},{"name":2059,"slug":2060,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":2063,"name":2063,"fn":2064,"description":2065,"org":2066,"tags":2067,"stars":25,"repoUrl":26,"updatedAt":2081},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2068,2071,2074,2077,2080],{"name":2069,"slug":2070,"type":15},"AI Infrastructure","ai-infrastructure",{"name":2072,"slug":2073,"type":15},"Cost Optimization","cost-optimization",{"name":2075,"slug":2076,"type":15},"LLM","llm",{"name":2078,"slug":2079,"type":15},"Performance","performance",{"name":2059,"slug":2060,"type":15},"2026-04-06T18:40:44.377464",{"slug":2083,"name":2083,"fn":2084,"description":2085,"org":2086,"tags":2087,"stars":25,"repoUrl":26,"updatedAt":2093},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[2088,2089,2092],{"name":2072,"slug":2073,"type":15},{"name":2090,"slug":2091,"type":15},"Database","database",{"name":2075,"slug":2076,"type":15},"2026-04-06T18:41:08.513425",600]