← DropboxCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Dropbox
Snapshot Sep 30, 2026 · 22:44 UTC · version 6.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [],
"skill_md_contents": "---\nname: organize-dropbox-folder\ndescription: 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.\n---\n\n# Organize Dropbox Folder\n\nUse this skill to safely organize Dropbox content through folder creation, copying, and moving.\n\n## Tools\n\n- `list_folder`\n- `search`\n- `get_file_metadata`\n- `create_folder`\n- `copy`\n- `move`\n- `check_job_status`\n\n## Workflow\n\n1. Understand the desired organization goal and target scope.\n2. Use `list_folder` or `search` to inventory the relevant content.\n3. Use `get_file_metadata` for items that may be moved or copied.\n4. Draft a proposed change plan before any mutation.\n5. If needed, create destination folders with `create_folder` after confirmation.\n6. Use `copy` when preserving the original location matters or when the user says copy/duplicate.\n7. Use `move` only when the user explicitly wants content relocated or archived.\n8. Use `check_job_status` for any asynchronous copy or move job until it completes or must be reported as pending.\n9. After changes, summarize all created, copied, moved, and pending paths.\n\n## Confirmation Required\n\nBefore any mutation, confirm:\n\n- Source paths\n- Destination paths\n- Whether the operation is copy or move\n- Whether destination folders should be created\n- Expected result after the operation\n\n## Output\n\nBefore mutation, present a plan:\n\n- Folders to create\n- Files or folders to copy\n- Files or folders to move\n- Items that need clarification\n\nAfter mutation, report:\n\n- Successfully created folders\n- Successfully copied items\n- Successfully moved items\n- Pending jobs and current status when relevant\n- Any failures or skipped items\n\n## Safety\n\nPrefer 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.\n\n## Good Triggers\n\n- \"Organize these files into folders by client.\"\n- \"Archive last year's project folder.\"\n- \"Copy these assets into the launch folder.\"\n- \"Move all final PDFs into the Final folder.\"\n\n## Do Not Use When\n\n- The user only wants to search or inspect content. Use `find-dropbox-content` or `inspect-dropbox-file`.\n- The user asks to delete content. Use `clean-up-dropbox-content`.\n- The user asks to restore content. Explain that recovery is unavailable until the Dropbox restore tool is exposed.\n"
}SHA-256: 163e46cb67993a08f60739cc941680af5136d2ca124ccf7b4e5e9adbaa7c7853