Repository navigation
Add upload-to-dropbox skill for Codex plugin - #12
Conversation
This change adds a new skill to improve upload workflow guidance for ChatGPT/Codex when users want to save generated content or upload files to Dropbox. This addresses feedback that @mentioning the plugin and providing clear skill-based routing (similar to Google Drive's approach) significantly improves action selection and performance. Changes: - New skill: upload-to-dropbox for saving/uploading content to Dropbox - Uses create_file tool with proper confirmation workflow - Clear differentiation from collect-files-with-request (which is for collecting uploads FROM others, not uploading BY the user) - Updated README.md with new skill documentation and examples - Bumped plugin version to 1.1.0 - Updated defaultPrompt to include upload example - Enhanced collect-files-with-request skill to route upload requests to the new upload-to-dropbox skill The new skill follows existing patterns with proper safety confirmations, clear routing rules, and comprehensive workflow guidance. Related: Slack discussion on improving upload performance through better skill-based routing (similar to OpenAI's Google Drive plugin). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Updates the upload-to-dropbox skill to leverage the non-public upload_file tool, which provides better support for various file types and upload scenarios compared to the text-oriented create_file. Changes: - Replace create_file with upload_file in skill tools list - Update workflow step references to upload_file - Adjust safety notes to reflect broader file type support - Add upload_file to OAuth scope mapping documentation for all MCP hosts The upload_file tool uses the same files.content.write OAuth scope. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
| "Create a shareable link for this PDF", | ||
| "Save this chat to Dropbox" | ||
| "Save this content to Dropbox", | ||
| "Create a shareable link for this PDF" |
There was a problem hiding this comment.
Just curious, is there a reason we are changing the order here?
There was a problem hiding this comment.
Yes, the intent was to surface the new save/upload workflow more prominently in the suggested prompts, since that’s the primary capability this PR adds. There isn’t a functional dependency on the order, though, so I’m happy to keep the original ordering if we’d prefer to minimize the change.
Recognize upload_file as a supported tool, expect the Codex-only upload-to-dropbox skill, and allow collect-files routing notes to differ when hosts do not share the same sibling skills. Co-authored-by: Cursor <cursoragent@cursor.com>
|
|
||
| # Skills that may intentionally diverge across MCP hosts when one host has | ||
| # extra sibling skills (for example Codex-only upload routing notes). | ||
| HOST_SPECIFIC_SKILL_CONTENT = { |
There was a problem hiding this comment.
Can we rename this to CODEX_SPECIFIC_SKILL_CONTENT? I imagine we might have some other skills in the future that are host specific, and it would benefit to have them bucketed by host!
There was a problem hiding this comment.
- rename this to CODEX_SPECIFIC_SKILL_CONTENT
lbeck-dropbox
left a comment
There was a problem hiding this comment.
lgtm! just added one suggestion!
Address review feedback to name the allowlist by host so future host-specific skill content can be bucketed clearly. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
upload-to-dropboxskill to guide ChatGPT/Codex upload workflowsupload_filetool for better file type supportChanges
upload-to-dropboxskill with comprehensive workflow guidanceupload_filetool instead of text-onlycreate_filecollect-files-with-request(upload BY user vs. collect FROM others)collect-files-with-requestto route upload requests to new skilldefaultPromptsuggestions to include upload exampleupload_fileto OAuth scope mapping documentationKey Features
Testing Plan
Notes
upload_fileuses samefiles.content.writeOAuth scope