Dropbox

View saved version →

---
name: clean-up-dropbox-content
description: Clean up Dropbox content by identifying obsolete, duplicate, temporary, or unwanted files and deleting only after explicit review. Use when the user explicitly asks to delete, remove, or clean up Dropbox files or folders.
---

# Clean Up Dropbox Content

Use this skill for careful deletion workflows in Dropbox.

## Tools

- `search`
- `list_folder`
- `get_file_metadata`
- `list_shared_links`
- `copy`
- `delete`
- `check_job_status`

## Workflow

1. Confirm the cleanup goal and scope.
2. Use `search` or `list_folder` to identify candidate content.
3. Use `get_file_metadata` to verify each deletion candidate.
4. Use `list_shared_links` when deleting shared content could affect others.
5. If the user may need rollback context, explain that the current Dropbox MCP tools do not expose revision listing or restore operations.
6. If the user wants to preserve a copy first, confirm the exact destination, call `copy`, and use `check_job_status` for any asynchronous copy job until it completes successfully.
7. After any requested copy has completed successfully, present a deletion review list and ask for explicit confirmation.
8. Call `delete` only for the exact confirmed items.
9. Use `check_job_status` for any asynchronous copy or deletion job until it completes or must be reported as pending.
10. Report every copied, deleted, skipped, pending, or failed item.

## Confirmation Required

Before deleting anything, confirm:

- Exact paths or stable identifiers
- Whether each item is a file or folder
- Whether the item appears shared
- Why it is safe to delete
- Exact copy destination, if the user wants to preserve a copy first

## Output

Before deletion, present:

- Candidate path
- Type
- Modified time when available
- Sharing status when relevant
- Copy destination when preserving a copy first
- Reason it appears safe to delete

After deletion, present:

- Copied items when relevant
- Deleted items
- Pending items and job status when relevant
- Failed items and reason
- Items skipped because they were ambiguous or risky

## Safety

Never delete based only on a broad pattern like "old files" or "duplicates" without listing exact targets. Never delete a parent folder when the user confirmed only child files. If confidence is not high, stop and ask the user to choose.

## Good Triggers

- "Delete these Dropbox files."
- "Clean up duplicate PDFs in this folder."
- "Remove obsolete draft files."
- "Delete temporary exports from Dropbox."

## Do Not Use When

- The user wants to move content to an archive. Use `organize-dropbox-folder`.
- The user wants to recover content. Explain that recovery is unavailable until the Dropbox restore tool is exposed.
- The user only wants a list of cleanup candidates and no deletion. Use `find-dropbox-content` or `inspect-dropbox-file`.

View saved version →

---
name: collect-files-with-request
description: Create, inspect, and manage Dropbox file requests for collecting uploads from other people. Use when the user asks to collect files, request uploads, create an upload portal, check a file request, or list existing file requests.
---

# Collect Files With Request

Use this skill to help users collect files from others through Dropbox file requests.

## Tools

- `create_file_request`
- `get_file_request`
- `list_file_requests`
- `create_folder`
- `get_file_metadata`
- `list_folder`

## Workflow

1. Determine whether the user wants to create a new file request, inspect one request, or list existing requests.
2. For a new request, identify the destination folder.
3. Do not use a team root, such as `/`, or the user's personal root, such as `/FirstName LastName`, as the destination. Dropbox requires the file request destination to be a child folder under that folder, such as `/FirstName LastName/Invoices`.
4. If the requested destination is a team root or the user's personal root, ask the user to confirm a child folder under that folder.
5. If the destination folder does not exist and the user wants it created, use `create_folder` only after explicit confirmation.
6. Before calling `create_file_request`, confirm the title, destination folder, deadline if applicable, and whether the request should be open or closed if that option is available.
7. Use `get_file_request` for a known raw request ID.
8. Use `list_file_requests` when the user asks for existing requests or cannot identify one.
9. After creating or finding a request, explain the request URL and where uploaded files will land.

## Confirmation Required

Before creating a file request, confirm:

- Request title
- Destination folder, confirmed to be a child folder under any requested team root or the user's personal root
- Deadline, if requested
- Any access or open/closed setting supported by the tool

Before creating a destination folder, confirm:

- Exact folder path
- Whether parent folders already exist
- That the folder is not a team root, such as `/`, or the user's personal root

## Output

Return:

- File request title
- Request URL or identifier
- Destination folder
- Status
- Deadline, if any
- Any action the user still needs to take

## Safety

Do not create folders or file requests without explicit confirmation. Do not assume uploaded files are private or reviewed; describe the destination and access implications clearly. Dropbox does not allow file requests at a team root, such as `/`, or the user's personal root; ask the user to confirm a child folder under that folder and do not retry with a guessed folder.

## Good Triggers

- "Create a Dropbox file request for vendor invoices."
- "Make an upload link for candidates to submit portfolios."
- "Show my open file requests."
- "Check the status of this file request."

## Do Not Use When

- The user wants to share existing content. Use `share-dropbox-content`.
- The user wants to organize existing files. Use `organize-dropbox-folder`.
- The user wants to recover deleted files. Explain that recovery is unavailable until the Dropbox restore tool is exposed.

View saved version →

---
name: find-dropbox-content
description: Find Dropbox files and folders relevant to a user request. Use when the user asks to search Dropbox, find a document, locate recent files, browse a folder, identify likely source files, or narrow down where content lives before reading, sharing, organizing, or restoring it.
---

# Find Dropbox Content

Use this skill to locate relevant Dropbox files and folders without changing anything.

## Tools

- `search`
- `list_folder`
- `get_file_metadata`

## Workflow

1. Clarify the search target only if the user request is too broad to act on.
2. Use `search` for broad keyword, title, file type, or natural-language searches.
3. When `search` returns a cursor and more results are needed, continue with `search` using the cursor only.
4. Use `list_folder` with `recursive=false` when the user names a folder or wants to browse a location.
5. When `list_folder` returns a cursor and more folder results are needed, continue with `list_folder` using the cursor only.
6. Use `get_file_metadata` for strong candidates before presenting a final recommendation.

## Output

Return the best matches first. For each result, include:

- Name
- Object type: file or folder
- Path or stable identifier
- Modified time when available
- Why it matched the request
- Any ambiguity or confidence caveat

## Safety

Do not create, copy, move, delete, restore, download, or share content. If the user asks to take one of those actions after finding content, switch to the relevant Dropbox skill.

## Good Triggers

- "Find the Q4 planning deck in Dropbox."
- "Search Dropbox for onboarding docs."
- "What files are in this folder?"
- "Find recent PDFs about the launch plan."
- "Where is the customer contract?"

## Do Not Use When

- The user already provided an exact file and wants its content inspected. Use `inspect-dropbox-file`.
- The user explicitly asks to create a shared link. Use `share-dropbox-content`.
- The user asks to add viewers or share directly with named recipients. Explain that recipient-sharing is unavailable until the required MCP tools are exposed.
- The user asks to restore or recover content. Explain that recovery is unavailable until the Dropbox restore tool is exposed.

View saved version →

---
name: inspect-dropbox-file
description: Inspect a Dropbox file or folder by checking metadata, shared links, and file content when needed. Use when the user asks what a file is, whether it is shared, when it changed, what access links exist, or asks to read/analyze a Dropbox file.
---

# Inspect Dropbox File

Use this skill to understand a Dropbox file or folder before summarizing, comparing, sharing, restoring, or organizing it.

## Tools

- `get_file_metadata`
- `fetch`
- `list_shared_links`
- `get_shared_link_metadata`
- `search`
- `list_folder`

## Workflow

1. Identify the target file or folder from the user request.
2. If the target is ambiguous, use `search` or `list_folder` to find likely matches.
3. Call `get_file_metadata` for the chosen item.
4. If the user asks about content, summary, extraction, or analysis, use `fetch` for files.
5. If the user asks about version history or rollback options, explain that the current Dropbox MCP tools do not expose revision listing or restore operations.
6. If the user asks about sharing or access, use `list_shared_links`; continue while the response indicates has_more or returns a cursor before claiming the shared-link listing is complete.
7. If the user provides a Dropbox shared link or asks about a specific link, use `get_shared_link_metadata`.

## Output

Summarize only the details relevant to the user request. Include:

- Name and path
- File or folder type
- Size and modified time when available
- Sharing/link status when relevant, including whether shared-link pagination is complete
- Version-history limitation when relevant
- Fetched content summary when relevant
- Recommended next action, if the user asked for one

## Safety

This is a read-only workflow. Do not create links, change sharing, copy, move, delete, or restore content. If the user asks for a mutation, explain the intended action and switch to the relevant Dropbox skill.

## Good Triggers

- "What is this Dropbox file?"
- "Summarize this file."
- "Check whether this folder is shared."
- "Show me the revision history."
- "When was this document last updated?"

## Do Not Use When

- The user only wants to search or browse. Use `find-dropbox-content`.
- The user wants to create a shared link or inspect shared-link state. Use `share-dropbox-content`.
- The user wants to add viewers or share directly with named recipients. Explain that recipient-sharing is unavailable until the required MCP tools are exposed.
- The user wants to restore a revision. Explain that recovery is unavailable until the Dropbox restore tool is exposed.

View saved version →

---
name: organize-dropbox-folder
description: Organize Dropbox files and folders by creating folders, copying content, or moving content into a cleaner structure. Use when the user asks to organize, archive, consolidate, restructure, copy, or move Dropbox content.
---

# Organize Dropbox Folder

Use this skill to safely organize Dropbox content through folder creation, copying, and moving.

## Tools

- `list_folder`
- `search`
- `get_file_metadata`
- `create_folder`
- `copy`
- `move`
- `check_job_status`

## Workflow

1. Understand the desired organization goal and target scope.
2. Use `list_folder` or `search` to inventory the relevant content.
3. Use `get_file_metadata` for items that may be moved or copied.
4. Draft a proposed change plan before any mutation.
5. If needed, create destination folders with `create_folder` after confirmation.
6. Use `copy` when preserving the original location matters or when the user says copy/duplicate.
7. Use `move` only when the user explicitly wants content relocated or archived.
8. Use `check_job_status` for any asynchronous copy or move job until it completes or must be reported as pending.
9. After changes, summarize all created, copied, moved, and pending paths.

## Confirmation Required

Before any mutation, confirm:

- Source paths
- Destination paths
- Whether the operation is copy or move
- Whether destination folders should be created
- Expected result after the operation

## Output

Before mutation, present a plan:

- Folders to create
- Files or folders to copy
- Files or folders to move
- Items that need clarification

After mutation, report:

- Successfully created folders
- Successfully copied items
- Successfully moved items
- Pending jobs and current status when relevant
- Any failures or skipped items

## Safety

Prefer copy over move when the user intent is ambiguous. Do not move shared folders or high-level team folders without extra confirmation. Do not delete anything; use `clean-up-dropbox-content` only when deletion is explicitly requested.

## Good Triggers

- "Organize these files into folders by client."
- "Archive last year's project folder."
- "Copy these assets into the launch folder."
- "Move all final PDFs into the Final folder."

## Do Not Use When

- The user only wants to search or inspect content. Use `find-dropbox-content` or `inspect-dropbox-file`.
- The user asks to delete content. Use `clean-up-dropbox-content`.
- The user asks to restore content. Explain that recovery is unavailable until the Dropbox restore tool is exposed.

View saved version →

---
name: share-dropbox-content
description: Share Dropbox files or folders by creating shared links, inspecting existing shared links, or explaining current shared-link state. Use only when the user explicitly asks to create a shared link, check access, or inspect a Dropbox shared link.
---

# Share Dropbox Content

Use this skill to create or inspect Dropbox shared links and explain shared-link state.

## Tools

- `create_shared_link`
- `list_shared_links`
- `get_shared_link_metadata`
- `get_file_metadata`
- `search`
- `list_folder`

## Workflow

1. Identify the target file or folder.
2. If the target is ambiguous, use `search` or `list_folder` and ask the user to choose.
3. Use `get_file_metadata` to confirm the exact target.
4. Use `list_shared_links` when checking current sharing state or before creating a new link if existing links matter; continue while the response indicates has_more or returns a cursor before treating the existing-link state as complete.
5. Use `get_shared_link_metadata` when the user provides or asks about a specific shared link.
6. Before calling `create_shared_link`, summarize the exact sharing plan and ask for explicit confirmation.
7. After sharing, report the resulting URL, effective access settings, and any warnings or partial failures.
8. If the user asks to add viewers, add recipients, or share directly with named people, explain that recipient-sharing is unavailable until those MCP tools are available. Offer to create a shared link instead when appropriate.

## Confirmation Required

Before creating a shared link, confirm:

- Exact target file or folder
- Link/access settings requested by the user
- Expiration, password, or download settings when supported

## Output

After a successful action, include:

- Shared link URL
- Whether the link was newly created or reused
- Effective access settings
- Any warning that existing link settings differ from requested settings
- Whether shared-link pagination was complete when existing links were checked

## Safety

Never create a link automatically after finding, downloading, or creating content. Do not claim access was granted to named recipients or viewers; recipient-sharing tools are not available.

## Good Triggers

- "Create a share link for this Dropbox folder."
- "Create a link to this file."
- "Check who can access this Dropbox link."
- "Send me a share link for the launch deck."

## Do Not Use When

- The user only wants to find a file. Use `find-dropbox-content`.
- The user only wants metadata or content summary. Use `inspect-dropbox-file`.
- The user wants to collect uploads from others. Use `collect-files-with-request`.
- The user wants to add viewers or share directly with named recipients. Explain that recipient-sharing is unavailable until the required MCP tools are exposed.