dbxcli
/dbxcli
Safely operate Dropbox through a locally installed dbxcli command, using its JSON manifest and schema-backed machine contract. Use for Dropbox file, shared-link, team, or account work; do not call the Dropbox API directly.
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Safely operate Dropbox through a locally installed dbxcli command, using its JSON manifest and schema-backed machine contract. Use for Dropbox file, shared-link, team, or account work; do not call the Dropbox API directly.
Original author description
Safely operate Dropbox through a locally installed dbxcli command, using its JSON manifest and schema-backed machine contract. Use for Dropbox file, shared-link, team, or account work; do not call the Dropbox API directly.
How it works
- Start safely
- Execution contract
- Large listings, search, and multi-step work
- Boundaries
SKILL.md preview
--- name: dbxcli description: Safely operate Dropbox through a locally installed dbxcli command, using its JSON manifest and schema-backed machine contract. Use for Dropbox file, shared-link, team, or account work; do not call the Dropbox API directly. --- # dbxcli Use the local `dbxcli` executable as the only Dropbox integration. Do not reimplement Dropbox API calls, scrape text help, or maintain a command catalog in this skill. The CLI's JSON help manifest is authoritative for the installed version. ## Start safely 1. Check availability with `command -v dbxcli`, then run `dbxcli version --output=json`. If it is unavailable, say so and give installation guidance for the user's operating system, using the [dbxcli releases](https://github.com/dropbox/dbxcli/releases) page. Do not download or install it unless the user authorizes that action. 2. Before a command you have not already discovered in the current task, run `dbxcli [command path] --help --output=json`. Begin with `dbxcli --help --output=json` when the command path is unknown. 3. Read the manifest's `supports_structured_output`, `input_schema`, `stdin_stdout`, `destructive_level`, `flags`, and `args`. Do not infer a command or flag from memory. 4. Represent the intended arguments and flags as JSON-shaped input and validate it against that command's `input_schema` before building the shell command. Map fields to command-line names using each field's `x-cli-name`. Read [tool-integration.md](references/tool-integration.md) for the discovery, validation, result, and error protocol. Read [automation.md](references/automation.md) for writes and confirmation behavior. Read [safety.md](references/safety.md) before handling credentials, transfers, deletion, replacement, or sharing. ## Execution contract For normal command execution, always pass `--output=json` and parse stdout as a single JSON envelope. Treat stderr as diagnostics only. Check both the process exit code and `.ok`: - If `.ok` is `true`, use documented `results[].status`, `results[].kind`, and `warnings`; do not rely on prose or undocumented fields. - If `.ok` is `false`, branch on stable `.error.code`, not `.error.message`. Surface a concise, redacted explanation and use structured `.error.details` only when relevant. Do not blindly retry writes or auth errors. - If the manifest says `supports_structured_output: false`, do not run that command as a machine-action. Explain the limitation or use a safe supported alternative. JSON help itself remains available. For destructive or externally visible actions, first discover the command and validate inputs, then prefer `--dry-run` if the manifest exposes it. Use an explicit `--if-exists` policy whenever it is available; never assume that a default overwrite or conflict policy matches the user's intent. A successful dry-run does not authorize execution; obtain explicit user confirmation before the real destructive action. When a command exposes `--yes`, use it only after that confirmation to prevent an interactive prompt from blocking automation. ## Large listings, search, and multi-step work The CLI follows Dropbox pagination internally; agents must not invent or pass cursors. For a broad `ls` or `search`, discover the command and use its `--limit` flag to bound the result delivered to the tool. Start with the narrowest sensible folder or search path; do not recursively enumerate a whole Dropbox when a scoped query will answer the request. A limited result is a selection, not proof that no additional matches exist. For search requests about text *inside* files, inspect the `search` manifest and pass `--content` only when it is available and the user requested a content search. Otherwise search is filename-oriented. Scope the search path and limit whenever practical. For a search → get → process task: discover and validate `search`, select the exact result path from its JSON metadata, then discover and validate `get`. Download to a named local file (never stdout), process that local file, and report the output path or a concise result. A later upload, share-link, or replacement is a separate externally visible action and needs its own discovery, safety policy, and authorization. ## Boundaries - Never put tokens, auth codes, app secrets, environment dumps, or auth-file contents in prompts, commands, logs, JSON fixtures, tool results, commits, or artifacts. Refer to secret names and paths only when needed. - Do not use `DBXCLI_ACCESS_TOKEN=value` inline. Pass an already-provisioned secret through the execution environment. Keep `DBXCLI_AUTH_FILE` outside the repository and do not read, upload, or commit it. - Never send binary file data through a tool result. For `get` or `share-link download`, download to a local file and report its path and metadata. `local operand -` is a byte stream and cannot be combined with JSON output. - Do not use this skill to expose shared links, alter permissions, overwrite, move, restore, or delete without user-authorized scope.
Files in this package (5)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
- references/automation.md 2 KB
- references/safety.md 2 KB
- references/tool-integration.md 3 KB
Versions
The database has no other skills named dbxcli.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 7d57b712bad4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90share-dropbox-content
Share Dropbox files or folders by creating shared links, inspecting existing shared links, or explaining current shared-link state. Use only when the user explicitly asks to create a shared link, check access, or inspect a Dropbox shared link. - 90inspect-dropbox-file
Inspect a Dropbox file or folder by checking metadata, shared links, and file content when needed. Use when the user asks what a file is, whether it is shared, when it changed, what access links exist, or asks to read/analyze a Dropbox file. - 100agentio-dropbox
Use when interacting with Dropbox via the agentio CLI - list, search, download, upload, move, copy, delete, share links. - 90dropbox
Dropbox API integration with managed OAuth. Files, folders, search, metadata, and cloud storage. Use this skill when users want to manage files and folders in Dropbox, search content, or work with file metadata. For other third party apps, use the api-gateway skill… - 91dropbox
Search, read, upload, organize, and share files and folders in the user's Dropbox cloud storage. Use to upload or download files, collect client uploads with file requests, inspect or create shared links, and create, copy, move, or delete content through Dropbox's official APIs. - 100dropbox-webhooks
Receive and verify Dropbox API webhooks. Use when setting up Dropbox webhook handlers, answering the Dropbox challenge verification request, debugging X-Dropbox-Signature verification, or handling list_folder change notifications and fetching changes with /files/list_folder/continue.