🗑️clean-up-dropbox-content
- プラグイン
- Dropbox
- ソース
- GitHub で見る ↗
説明
Dropboxのコンテンツをクリーンアップします。古いファイル、重複したファイル、一時ファイル、または不要なファイルを特定し、明示的なレビュー後にのみ削除します。 次のような場合に使用: ユーザーがDropboxのファイルやフォルダを削除、削除、またはクリーンアップするよう明示的に要求している場合。
原文を表示
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
searchlist_folderget_file_metadatalist_shared_linkscopydeletecheck_job_status
Workflow
- Confirm the cleanup goal and scope.
- Use
searchorlist_folderto identify candidate content. - Use
get_file_metadatato verify each deletion candidate. - Use
list_shared_linkswhen deleting shared content could affect others. - If the user may need rollback context, explain that the current Dropbox MCP tools do not expose revision listing or restore operations.
- If the user wants to preserve a copy first, confirm the exact destination, call
copy, and usecheck_job_statusfor any asynchronous copy job until it completes successfully. - After any requested copy has completed successfully, present a deletion review list and ask for explicit confirmation.
- Call
deleteonly for the exact confirmed items. - Use
check_job_statusfor any asynchronous copy or deletion job until it completes or must be reported as pending. - 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-contentorinspect-dropbox-file.
原文・著作権は Anthropic および各プラグイン作者に帰属します。日本語訳は Claude API による自動翻訳です。