Manage Dinox Storage

CRITICAL — Before doing anything else, first read ../dino-shared/SKILL.md. It contains shared auth, output, and write-safety rules.

Use this skill when the user wants to inspect custom storage configs, verify S3 connectivity, upload a file, or inspect storage usage.

Safety & Boundaries (Must Follow)

Treat storage credentials and endpoint details as sensitive data. Never echo secret_access_key back to the user.
dino storage test writes a tiny temporary object to S3. dino storage upload writes to both S3 and local Dinox metadata. Always show the exact command and get explicit confirmation before running the real write.
Prefer dino storage list --format json before uploading if the target storage config is ambiguous.
Do not ask the user to paste auth tokens into chat. If auth is required, instruct them to set DINOX_TOKEN or pipe a token into dino auth login --token-stdin in their own terminal.
If the user wants to upload to a specific config without changing the active storage in the app, prefer --storage-id.
An explicit --key refuses to replace an existing main object or derived image thumbnail by default. Use --overwrite only after the user explicitly confirms replacement of those exact keys.
Reject object keys and configured path prefixes containing dot-only . or .. segments; standard URL clients normalize those segments and can resolve the returned URL to a different object.