From 371376d76ffa42fae41b3035530d325581e7c47d Mon Sep 17 00:00:00 2001 From: Ryan Kara Date: Thu, 15 Oct 2026 16:02:22 -0400 Subject: [PATCH 1/2] Temporarily disable automatic upload file previews --- codex/skills/upload-to-dropbox/SKILL.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/codex/skills/upload-to-dropbox/SKILL.md b/codex/skills/upload-to-dropbox/SKILL.md index 923def4..c3a7a66 100644 --- a/codex/skills/upload-to-dropbox/SKILL.md +++ b/codex/skills/upload-to-dropbox/SKILL.md @@ -12,7 +12,6 @@ Use this skill to save generated content or upload files to Dropbox. - `upload_file` - `create_folder` -- `file_preview` - `list_folder` - `search` @@ -23,7 +22,7 @@ Use this skill to save generated content or upload files to Dropbox. 3. If the destination folder does not exist, confirm the path and create it with `create_folder`. `upload_file` does not create missing parent folders. `create_folder` only creates the last path segment, so create any missing parent first. 4. If the user did not name the file, propose one filename and extension. 5. Before calling `upload_file`, confirm the exact destination path, filename, and content summary with the user. -6. After a successful upload, report that the file was created, including the path and filename. Then call `file_preview` for that file. +6. After a successful upload, report that the file was created, including the path and filename. 7. If `upload_file` returns a name conflict, stop and ask the user before trying another name. 8. If the user wants a shared link, switch to `share-dropbox-content`. Do not create a shared link from this skill. @@ -48,7 +47,7 @@ If `upload_file` returns a name conflict, report the conflict and wait for the u ## Safety -Do not upload without explicit confirmation of the destination path, filename, and content. Do not create a destination folder without confirming the path. Do not assume the destination folder or filename without verifying with the user. Do not retry with a different filename after a name conflict until the user chooses one. Do not create a shared link from this skill. Call `file_preview` only after `upload_file` returns success. +Do not upload without explicit confirmation of the destination path, filename, and content. Do not create a destination folder without confirming the path. Do not assume the destination folder or filename without verifying with the user. Do not retry with a different filename after a name conflict until the user chooses one. Do not create a shared link from this skill. Automatic post-upload previews are temporarily disabled. Do not call `file_preview` as part of this upload workflow. Prefer specific destination folders over generic locations like the user's root folder. When the user's intent for folder structure is unclear, suggest organizing content into topic or project-specific folders. From 246d3ad8fe834770c80c3226aae76db4dde22e1f Mon Sep 17 00:00:00 2001 From: Ryan Kara Date: Thu, 15 Oct 2026 16:16:24 -0400 Subject: [PATCH 2/2] Remove temporary preview prohibition from upload skill --- codex/skills/upload-to-dropbox/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codex/skills/upload-to-dropbox/SKILL.md b/codex/skills/upload-to-dropbox/SKILL.md index c3a7a66..f624b86 100644 --- a/codex/skills/upload-to-dropbox/SKILL.md +++ b/codex/skills/upload-to-dropbox/SKILL.md @@ -47,7 +47,7 @@ If `upload_file` returns a name conflict, report the conflict and wait for the u ## Safety -Do not upload without explicit confirmation of the destination path, filename, and content. Do not create a destination folder without confirming the path. Do not assume the destination folder or filename without verifying with the user. Do not retry with a different filename after a name conflict until the user chooses one. Do not create a shared link from this skill. Automatic post-upload previews are temporarily disabled. Do not call `file_preview` as part of this upload workflow. +Do not upload without explicit confirmation of the destination path, filename, and content. Do not create a destination folder without confirming the path. Do not assume the destination folder or filename without verifying with the user. Do not retry with a different filename after a name conflict until the user chooses one. Do not create a shared link from this skill. Prefer specific destination folders over generic locations like the user's root folder. When the user's intent for folder structure is unclear, suggest organizing content into topic or project-specific folders.