majiayu000 Why This Skill Exists
Early proto helpers (b00t-aws-tools) duplicated SDK logic yet shipped no usable tools. This skill re-centers AWS work on the official aws CLI plus the canonical _b00t_/clouds.云☁️/aws.🦉.云☁️ sketches, ensuring every agent follows the same ceremony.
When To Load
- Deploy/invoke a Lambda (
lambda.invoke.sketch.sh). - Publish an image to ECR and run it on ECS/Fargate (
ecs.fargate.sketch.sh). - Inspect/download objects from S3 buckets (
s3.bucket.sketch.sh). - Bridge into AWS MCP servers after credentials are verified.
Operating Instructions
b00t learn aws→ review the.☁️README for prerequisites and environment variables.- Export account-specific env vars (bucket names, subnet IDs, function names). Never hardcode them.
- Run the appropriate sketch script; capture JSON receipts/log output for the Operator and stash sensitive artifacts in the secure storage path, not git.
- If an official AWS MCP server suffices, configure it per https://github.com/awslabs/mcp instead of writing new helpers.
Melvins (🤓)
- CLI SSOT:
aws sts get-caller-identityis the authoritative source for Account/ARN context. - .☁️ Canon: All cloud runbooks live under
_b00t_/clouds.云☁️/…; keep additions there. - No stray secrets: env vars or datums supply parameters; scripts stay generic.
- Verify outputs: Lambda/ECS scripts emit receipts—read them before declaring success.
References
_b00t_/clouds.云☁️/aws.🦉.云☁️/README.md_b00t_/clouds.云☁️/aws.🦉.云☁️/lambda.invoke.sketch.sh_b00t_/clouds.云☁️/aws.🦉.云☁️/ecs.fargate.sketch.sh_b00t_/clouds.云☁️/aws.🦉.云☁️/s3.bucket.sketch.sh- https://github.com/awslabs/mcp