Create and manage a sorted directory structure in AWS S3

Upload many files to S3 with automatic organization by first-character prefixes.

This skill appears to do exactly what it claims, but review these practical safety steps before installing or running it: 1) Use least-privilege AWS credentials — grant only the S3 permissions needed (PutObject, List, optionally Delete) and scope them to the target bucket(s). 2) Test with --dry-run and/or a disposable test bucket first to verify behavior. 3) Be aware the staging flow follows symlinks (it creates symlinks to real file paths), so if SOURCE_DIR contains symlinks to sensitive files outside the directory those files may be uploaded — ensure SOURCE_DIR contains only intended files. 4) Confirm the bucket name you pass is correct to avoid accidental data exfiltration. 5) Inspect the script locally before running it in an automated agent context. If you need the agent to run this skill autonomously, consider providing credentials with limited scope and monitoring uploads.

Type: OpenClaw Skill Name: s3-sort Version: 1.0.1 The OpenClaw skill 's3-bulk-upload' is designed to upload files to S3 with automatic prefix organization. Both the `SKILL.md` documentation and the `s3-bulk-upload.sh` script align with this stated purpose. The skill correctly uses `aws s3 cp` and `aws s3 sync` commands, requires appropriate AWS credentials, and employs standard shell scripting practices including temporary directories and symlinks for efficient bulk uploads. There is no evidence of prompt injection attempts in the markdown, nor any malicious code such as data exfiltration to unauthorized endpoints, persistence mechanisms, or obfuscation in the script. The use of `realpath` for symlink resolution is a standard practice for `aws s3 sync` and is not indicative of malicious intent within the context of uploading files from a specified source directory.