2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill day253-volcengine-storage-tos- _meta.json303 B
- SKILL.md4.1 KB
Overview
This skill provides command-line object storage operations for Volcengine TOS (Tinder Object Storage). It enables bucket management and common object workflows like upload, download, listing, deletion, presigned URLs, and basic troubleshooting. Use it to automate or script storage tasks with the official TOS Python SDK.
How this skill works
The script is a thin CLI wrapper around the TOS Python SDK that exposes subcommands for list-buckets, create-bucket, delete-bucket, list-objects, upload, download, delete, head, presign, and copy. It reads credentials and endpoint settings from environment variables or an optional .env, performs a minimal read-only check to confirm connectivity, then runs the requested operation and saves logs/results to the output directory. Safety checks (like --confirm for destructive ops) and basic verifications (content-type inference, download size check) are applied.
When to use it
- Manage buckets and objects on Volcengine TOS from scripts or CI/CD pipelines
- Upload or download files between local disk and TOS buckets
- Generate presigned URLs for temporary object access
- Audit or list objects with prefix and pagination controls
- Troubleshoot permission or connectivity issues to TOS endpoints
Best practices
- Set VOLCENGINE_ACCESS_KEY, VOLCENGINE_SECRET_KEY, VOLCENGINE_TOS_ENDPOINT, and VOLCENGINE_TOS_REGION before running
- Run a read-only verification (list-buckets or head) to validate credentials and permissions first
- Always use --confirm for delete and delete-bucket to prevent accidental data loss
- Prefer SDK-managed multipart uploads for large files; this script is optimized for small-to-medium files
- Save operation outputs and logs to the configured output directory for audit and debugging
Example use cases
- List all buckets in an account to verify environment and access
- Upload a report.pdf to my-bucket at key data/report.pdf in automation
- Download a stored object to a local file and verify content length
- Create a presigned URL valid for 1 hour to share a private object
- Delete an empty bucket after confirming intent with --confirm
FAQ
Set VOLCENGINE_ACCESS_KEY, VOLCENGINE_SECRET_KEY, VOLCENGINE_TOS_ENDPOINT, and VOLCENGINE_TOS_REGION. A .env file at repo root is optionally auto-loaded.
How are large files handled?
The underlying SDK supports multipart uploads. The script uses put_object_from_file for small-to-medium files; for very large files ensure the SDK multipart behavior is enabled or use the SDK directly.