Claude
Skill
cloud-aws
Operate AWS with the aws CLI - EC2, EKS, S3, IAM, VPC, RDS, Lambda, costs. Read-first; mutations gated by approval.
Virus-scanned
Reviewed automatically before listing.
Download
navinspire-ia-navin-navin_skills_cloud-aws-e9c73a3.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/cloud-aws
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git
git clone https://github.com/Navinspire-ia/navin.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
AWS Cloud Operator
Overview
Drive AWS through the aws CLI (or the AWS MCP servers when configured). Always confirm account and region before acting.
Common commands
aws sts get-caller-identity
aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,State.Name,InstanceType]' --output table
aws eks list-clusters && aws eks update-kubeconfig --name <cluster>
aws s3 ls
aws iam list-roles --max-items 20
aws logs tail <log-group> --since 1h
aws ce get-cost-and-usage --time-period Start=<d1>,End=<d2> --granularity MONTHLY --metrics UnblendedCost
Workflow
- Identify account, region, and profile (
sts get-caller-identity); never assume. - Inspect before changing: describe the resource and its dependencies (security groups, IAM policies, subnets).
- Prefer IaC: if the resource is Terraform/CDK/CloudFormation-managed, change the code and plan/diff it, not the console state.
- After a mutation, re-describe the resource and check CloudWatch/logs for regressions.
Rules
- Terminating instances, deleting buckets/data, and any IAM or security-group change require
human-approval. - Never print or store credentials; use profiles and env vars.
- Flag cost-heavy actions (large instances, cross-region transfer, NAT) before running them.
Files (navin)
-
SKILL.md 1.5 KB
--- name: cloud-aws description: Operate AWS with the aws CLI - EC2, EKS, S3, IAM, VPC, RDS, Lambda, costs. Read-first; mutations gated by approval. metadata: {"navin":{"emoji":"🟠","category":"devops","requires":{"bins":["aws"]}}} --- # AWS Cloud Operator ## Overview Drive AWS through the `aws` CLI (or the AWS MCP servers when configured). Always confirm account and region before acting. ## Common commands ```bash aws sts get-caller-identity aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,State.Name,InstanceType]' --output table aws eks list-clusters && aws eks update-kubeconfig --name <cluster> aws s3 ls aws iam list-roles --max-items 20 aws logs tail <log-group> --since 1h aws ce get-cost-and-usage --time-period Start=<d1>,End=<d2> --granularity MONTHLY --metrics UnblendedCost ``` ## Workflow 1. Identify account, region, and profile (`sts get-caller-identity`); never assume. 2. Inspect before changing: describe the resource and its dependencies (security groups, IAM policies, subnets). 3. Prefer IaC: if the resource is Terraform/CDK/CloudFormation-managed, change the code and plan/diff it, not the console state. 4. After a mutation, re-describe the resource and check CloudWatch/logs for regressions. ## Rules - Terminating instances, deleting buckets/data, and any IAM or security-group change require `human-approval`. - Never print or store credentials; use profiles and env vars. - Flag cost-heavy actions (large instances, cross-region transfer, NAT) before running them.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.