aliyun-oss_skill

This skill helps securely upload files to Alibaba Cloud OSS with automatic large-file handling and pre-signed URL generation for temporary access.

Python

2.5k

GitHub Stars

12

Bundled Files

2 months ago

Catalog Refreshed

4 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 aliyun-oss

__init__.py90 B
__main__.py530 B
_meta.json276 B
aliyun_oss_uploader.py10.8 KB
example-config.json359 B
file_processor.py4.4 KB
handle_media.py1.6 KB
main.py2.1 KB
package.json360 B
security_validator.py4.2 KB
SKILL.md3.3 KB
sts_manager.py1.1 KB

Overview

This skill is a secure, efficient tool for uploading files to Alibaba Cloud OSS and generating temporary presigned links. It supports single and batch uploads, multipart transfers for large files, automatic renaming to avoid conflicts, and configurable expiration for shared links. The configuration keeps credentials out of code and enforces file size limits for safety.

How this skill works

The skill reads an external JSON config that contains endpoint, bucket, keys, size limits, and default prefixes. It uses the OSS SDK to perform single, batch, and multipart uploads, automatically switching to multipart when a file exceeds the large-file threshold. Presigned URLs are generated by the SDK with configurable expiry values, and a search feature lists or finds objects by name in the bucket.

When to use it

Upload single files from a local machine to an OSS bucket.
Perform batch migration or backup of multiple files to OSS.
Upload large files reliably using multipart/resumable upload.
Share temporary download links with expiry for limited access.
Automate uploads from chat or media pipelines via OpenClaw integration.

Best practices

Store credentials in the external config file and set file permissions to 600.
Use a dedicated RAM user with least privilege for uploads and listing only.
Set an appropriate large-file threshold and enforce a max file size to protect quotas.
Choose UUID or timestamp renaming to prevent name collisions in shared buckets.
Rotate AccessKey regularly and monitor OSS usage and access logs.

Example use cases

Share a log or report by uploading it and sending a 6-hour presigned URL to a teammate.
Migrate a set of assets to OSS via batch_upload for backup or archival.
Upload video or dataset using multipart upload to handle files >100MB reliably.
Integrate into chat workflows to upload attachments and return temporary links automatically.
Search for previously uploaded artifacts in the bucket to avoid duplicate uploads.

FAQ

The skill rejects files larger than the configured max (default 2GB) and uses multipart upload for files over the large-file threshold (default 100MB).

How are credentials protected?

Credentials live in an external JSON config file (path configurable) and should be owned by the service account with permissions set to 600; use a RAM user with minimal permissions for safety.