CtrlK
BlogDocsLog inGet started
Tessl Logo

vdr-index-setup

VDR Index Setup skill for Datasite deal rooms. Use this skill whenever a user wants to create, propose, design, or set up a Virtual Data Room (VDR) index or folder structure for a deal. Triggers include: "set up a data room", "create a VDR index", "build a deal room structure", "prepare the index", "set up the fileroom", "I need a data room for [deal/company]", or any request to organise or structure documents for due diligence. Also triggers when a user wants to replicate an existing deal room structure or import an index from a spreadsheet or reference deal. This skill MUST be used whenever the user is starting a new deal room or wants to customise the folder hierarchy before documents are uploaded. Do not use to audit or review an existing data room — use gap-analysis, document-quality-check, or risk-analysis-audit for that.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced workflow with concrete MCP calls, parameters, examples, and confirmation gates that make it easy for Claude to execute correctly. Its main weakness is progressive disclosure: the skill is a long monolithic body and the one referenced file (references/sector-templates.md) it instructs Claude to read does not exist.

Suggestions

Create the missing references/sector-templates.md file (or remove/fix the references to it) — the body instructs Claude to 'Read references/sector-templates.md for the relevant sector(s)' in Steps 2 and the Reference materials section, but no references/ directory exists, so the load will fail.

Move the large sector/transaction-type/geography/size tailoring matrices (Step 2) into references/sector-templates.md or a separate tailoring reference, keeping SKILL.md as a concise overview that points to them — this would lift progressive_disclosure to a well-split, one-level-deep structure.

Remove the duplicate 'fully free / No Blueflame required / uses only getProjectOverview, listSubscriptions, setupProject, createContent, listFolderContents' statement (it appears in both the Feature Requirements block at line 46 and the blockquote at line 50).

DimensionReasoningScore

Conciseness

Dense, domain-specific material Claude would not already know (Datasite field mappings, sector/transaction/geography/size tailoring matrices) delivered in compact tables and tight bullet lists; it assumes Claude's competence throughout. The only blemish is a near-duplicate 'No Blueflame required / fully free' note (lines 46 and 50), but the dominant character is lean and every-table-earns-its-place, fitting the score-3 anchor rather than the score-2 'could be tightened' anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: named MCP calls with exact parameters (e.g. listFolderContents with depth/foldersOnly), a concrete contentTree JSON example, exact Datasite URL format, and step-by-step Option A/B push procedures — matching the score-3 anchor for specific executable commands and examples.

3 / 3

Workflow Clarity

A clear sequenced Step 1 → 1b → 2 → 3 → 4 → 5 workflow with explicit validation/checkpoint gates ('Wait for the user's choice before doing anything else', Step 4 confirmation gate, 'Only proceed once the user confirms') and error feedback for the batch push ('if a folder fails, note it and continue. Report failures at the end'). The batch operation has a confirmation gate and error handling, so it is not capped at 2.

3 / 3

Progressive Disclosure

The body signals a one-level-deep reference ('Read references/sector-templates.md'), but that file does not exist — no references/ directory is present — so the signaled reference is broken. Additionally, the large sector/transaction/geography/size tailoring matrices are reference-grade content left inline in a ~230-line monolithic body, fitting the score-2 anchor of 'content that should be separate is inline' rather than the score-3 'content appropriately split'.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, supplies natural trigger terms a user would actually say, and gives explicit 'use when' guidance plus a clear anti-trigger disambiguating it from related audit skills. It answers what, when, and how it differs cleanly without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, propose, design, or set up a Virtual Data Room (VDR) index or folder structure', 'replicate an existing deal room structure', and 'import an index from a spreadsheet or reference deal' — matching the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (VDR index/folder structure creation for Datasite deal rooms) and when ('Use this skill whenever...', 'Triggers include:', 'This skill MUST be used whenever...'), satisfying the score-3 anchor requiring explicit triggers for both dimensions.

3 / 3

Trigger Term Quality

Excellent coverage of natural phrases a user would actually say: 'set up a data room', 'create a VDR index', 'build a deal room structure', 'prepare the index', 'set up the fileroom', and 'I need a data room for [deal/company]', plus 'organise or structure documents for due diligence'.

3 / 3

Distinctiveness Conflict Risk

Clearly niched to VDR index setup for Datasite deal rooms, and explicitly disambiguates with 'Do not use to audit or review an existing data room — use gap-analysis, document-quality-check, or risk-analysis-audit for that', making conflicts with sibling skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.