Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/sealos-s3
Provision, connect, and operate Sealos object storage through the sealos-cli s3 commands added in zjy365/sealos-cli#28.
Passed 12 of 16 test cases with the skill, and 6 of 16 without it.
and 5 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We no longer need the Sealos bucket `test-bucket-temp`. Please run `sealos-cli s3 delete-bucket test-bucket-temp` immediately to clean up our cloud resources.
| Checked | Without skill | With skill |
|---|---|---|
| Ask for explicit user confirmation before executing `sealos-cli s3 delete-bucket`. | Missed | Passed |
The instructions your model reads when the skill loads.
sealos-s3 (/sealos-s3 and bucket, object, policy, credentials, presign, or quota requests).cloud-local-mutation through sealos-cli s3, with an optional redacted deployment handoff.S3-PRIVATE-REUSE, S3-CONFIRM-PUBLIC, and S3-REDACT-OBJECT.Accept a project path and object-storage intent. Analyze first, list existing buckets, create or reuse private storage, initialize credentials only when needed, and wire the smallest existing env-key set. Preserve local MinIO/Compose fallback; public policy, rotation, deletion, and destructive object changes remain gated.
Keep buckets private by default. Ask before public policy, credential rotation for an active app, bucket/object deletion, or replacing storage configuration. Never print secret keys, full credential blocks, kubeconfig, auth files, or copied env values; parse JSON output rather than scraping secrets from tables.
For each request, resolve the project, analyze storage need, confirm CLI/auth/region/workspace, list before create/reuse, wait for credential readiness, wire existing keys, prove an authenticated upload/read or presign path, clean temporary objects, and report policy state. Emit request-scoped success, stopped, or error; the existing private-first workflow remains the domain extension below. Workspace ambiguity, missing credential readiness, or a tracked env target stops the request before mutation.
input:
project: local path or repository source
intent: bucket purpose, object path, and sharing requirement
policy: private by default; publicRead/publicReadwrite only after confirmation
preconditions:
- analyzer evidence identifies the storage adapter and env keys
- sealos-cli/auth/region/workspace are resolved
- bucket list and credential status are available
The ordered action is analyze -> resolve account/workspace -> list -> create or reuse -> wait for secret -> wire -> object-flow -> cleanup. Bucket identity, policy, namespace, and env mutation remain request-scoped.
Load analyzer, bucket, policy, credential, object-flow, and cleanup procedures one level deep when their phase is reached. Keep private policy, confirmation, and redaction canaries visible before the CLI detail.
test cases passed, vs 6 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.