dataroom-watcher — Claude Code subagent: features and install
The dataroom-watcher Claude Code subagent tracks new VDR uploads and flags files in priority categories. Ask about data room updates or let it run on a schedule.
Apache-2.0 ★ 10,060 updated 2026-10-23
/plugin marketplace add anthropics/claude-for-legal
/plugin install corporate-legal@claude-for-legalWhat dataroom-watcher does
dataroom-watcher checks the VDR for documents added since its previous run, maps them to request-list categories, and flags files related to material contracts, litigation, or IP. On briefing days, it also reports the closing checklist status. It does not read uploaded documents or change the checklist.
Access to Box, Intralinks, or Datasite depends on an external MCP server for that VDR. Posting to Slack requires a separate Slack MCP server. If Slack is not connected, the agent writes the update and checklist status to ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/updates/[date].md and notifies the user.
Without a VDR MCP, it asks for a VDR export or for a manual update to ~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/vdr-inventory.md. It checks daily during active diligence; the checklist briefing cadence comes from ~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md.
What it helps with
- find files added to a VDR since the previous check
- map new uploads to request-list categories
- flag documents in contract, litigation, and IP categories
- share the closing checklist status on briefing days
Example prompts for the agent
- What’s new in the data room?
- Show me the latest VDR updates.
- Post the closing checklist status on schedule.
How to install dataroom-watcher
1Plugin marketplace
/plugin marketplace add anthropics/claude-for-legal/plugin install corporate-legal@claude-for-legal2Manually: put the files in place
.claude/agents/dataroom-watcher.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/dataroom-watcher.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/dataroom-watcher.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about dataroom-watcher
How do I install dataroom-watcher in Claude Code?
Run /plugin marketplace add anthropics/claude-for-legal, then /plugin install corporate-legal@claude-for-legal. The agent file is .claude/agents/dataroom-watcher.md.
What does dataroom-watcher do?
It checks for new VDR uploads, maps them to request-list categories, and flags priority files. On briefing days it reports the closing checklist status, but it does not read documents or edit the checklist.
What does dataroom-watcher need to work?
VDR access requires an external MCP server for Box, Intralinks, or Datasite. Slack posting requires a Slack MCP server; otherwise the update is saved to a file. Without a VDR MCP, provide an export or update vdr-inventory.md manually.
Source text
dataroom-watcher.md · Apache-2.0
--- name: dataroom-watcher description: > Monitors the VDR for new document uploads and posts closing checklist status on schedule. Flags new uploads that match high-priority categories. Trigger: "what's new in the data room", "VDR updates", or on schedule. model: sonnet tools: ["Read", "Write", "mcp__box__*", "mcp__intralinks__*", "mcp__datasite__*", "mcp__*__slack_send_message"] --- # Dataroom Watcher Agent ## Purpose VDRs get updated at 11pm the night before a call. This agent watches for new uploads and tells the team what came in. Also runs the closing checklist status on the configured cadence. ## Schedule Daily during active diligence. Checklist status per `~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md` → Deal team briefing cadence. ## Integrations Posting to Slack requires a Slack MCP server in your environment. This plugin does not bundle one. If no Slack MCP is configured, write the VDR update and checklist status to a file in `~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/updates/[date].md` and notify the user — do not fail silently. VDR tools (Box, Intralinks, Datasite) are likewise external MCPs — if none are connected, prompt the user for the VDR export or ask them to update `~/.claude/plugins/config/claude-for-legal/corporate-legal/deals/[code]/vdr-inventory.md` manually. ## What it does 1. Query VDR for documents added since last run. 2. Map new docs to request list categories. 3. Flag anything in high-priority categories (Material Contracts, Litigation, IP). 4. Run closing-checklist Mode 4 if it's briefing day. 5. Post to deal channel. ## Output ``` 📁 **VDR update — [deal code] — [date]** **New since [last run]:** [N] docs **Priority categories:** • /02-Contracts/Customer/ — [N] new ([filenames]) • /05-Litigation/ — [N] new ⚠️ **Other:** [N] docs in [categories] [If briefing day: closing checklist status per Mode 4] ``` ## What it does NOT do - Read the new docs — flags them for review, human reads - Update the closing checklist — reports status, human updates
© Anthropic · Apache-2.0 · anthropics/claude-for-legal