Update to Dropbox

{
  "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.",
  "included_files": [],
  "name": "collect-files-with-request",
  "skill_md_contents": "---\nname: collect-files-with-request\ndescription: 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.\ndisable-model-invocation: false\n---\n\n# Collect Files With Request\n\nUse this skill to help users collect files from others through Dropbox file requests.\n\n## Tools\n\n- `create_file_request`\n- `get_file_request`\n- `list_file_requests`\n- `create_folder`\n- `get_file_metadata`\n- `list_folder`\n\n## Workflow\n\n1. Determine whether the user wants to create a new file request, inspect one request, or list existing requests.\n2. For a new request, identify the destination folder.\n3. 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`.\n4. 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.\n5. If the destination folder does not exist and the user wants it created, use `create_folder` only after explicit confirmation.\n6. 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.\n7. Use `get_file_request` for a known raw request ID.\n8. Use `list_file_requests` when the user asks for existing requests or cannot identify one.\n9. After creating or finding a request, explain the request URL and where uploaded files will land.\n\n## Confirmation Required\n\nBefore creating a file request, confirm:\n\n- Request title\n- Destination folder, confirmed to be a child folder under any requested team root or the user's personal root\n- Deadline, if requested\n- Any access or open/closed setting supported by the tool\n\nBefore creating a destination folder, confirm:\n\n- Exact folder path\n- Whether parent folders already exist\n- That the folder is not a team root, such as `/`, or the user's personal root\n\n## Output\n\nReturn:\n\n- File request title\n- Request URL or identifier\n- Destination folder\n- Status\n- Deadline, if any\n- Any action the user still needs to take\n\n## Safety\n\nDo 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.\n\n## Good Triggers\n\n- \"Create a Dropbox file request for vendor invoices.\"\n- \"Make an upload link for candidates to submit portfolios.\"\n- \"Show my open file requests.\"\n- \"Check the status of this file request.\"\n\n## Do Not Use When\n\n- The user wants to upload or save their own content to Dropbox. Use `upload-to-dropbox`.\n- The user wants to share existing content. Use `share-dropbox-content`.\n- The user wants to organize existing files. Use `organize-dropbox-folder`.\n- The user wants to recover deleted files. Explain that recovery is unavailable until the Dropbox restore tool is exposed.\n"
}