zeekayandHanzo Dev c2063c83e9 docs(skills): stop teaching MinIO, document the SDK that actually ships ...

Both storage skills described a product we do not run. Hanzo S3 is
hanzoai/s3, a SeaweedFS fork (Apache-2.0) -- not a MinIO fork, not AGPL.

hanzo-storage installed the `minio` pip client and built every example on
it. Converted to boto3: correct method names and argument order
(fput_object -> upload_file flips path/bucket), Metadata without the
manual x-amz-meta- prefix boto3 adds itself, paginated list_objects_v2,
and path-style addressing + sigv4, which a self-hosted endpoint requires.

hanzo-s3 was worse than stale. It claimed to wrap the MinIO Python client
and documented S3Admin, DeleteObject, fput_object, fget_object,
put_object, get_object, bucket_exists, remove_objects and
presigned_put_object -- none of which exist. The package has shipped on
boto3 since python-sdk c07f98de and exports seven methods. Documented
those, and pointed uploads and downloads at boto3 where they belong.

Dropped the minioadmin/minioadmin default credentials both files handed
out, the 9001 web console (there is none), and the competitor API mapping
table. Credentials now read from the environment, injected from KMS.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-03 10:01:11 -07:00

..

SKILL.md

docs(skills): stop teaching MinIO, document the SDK that actually ships

2026-08-03 10:01:11 -07:00