Agent skill
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in `.☁️` runbooks.
Install this agent skill to your Project
npx add-skill https://github.com/elasticdotventures/_b00t_/tree/main/skills/aws-cli
SKILL.md
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
datum-system
Helps work with the b00t datum system - TOML-based configuration for AI models, providers, and services. Datums are stored in ~/.dotfiles/_b00t_/ and specify WHICH environment variables are required (not the values). Enables DRY approach by centralizing configuration in Rust, exposed to Python via PyO3.
dry-philosophy
Don't Repeat Yourself (DRY) and Never Reinvent the Wheel (NRtW) - core b00t principles. Use existing libraries, leverage Rust via PyO3 instead of duplicating logic in Python, and contribute to upstream projects rather than fork privately.
direnv-pattern
Implements the b00t environment management pattern: direnv → .envrc → dotenv → .env where datums specify WHICH environment variables are required and .env contains the actual secret VALUES. Ensures automatic environment loading per-project.
executive-role
Defines the shared role, responsibilities, and operating principles for an Executive agent in the b00t hive. This skill uses Rhai scripting to provide model-specific directives.
b00t
model-routing
Select the right model for the task. Maps task cognitive tier to optimal model. Reads _b00t_ datums for available models. Prefer local/cheap for deterministic work; frontier for reasoning.
Didn't find tool you were looking for?