agentleFS
MihirokteMihirokte/agent-skills/skills/aws/SKILL.md

aws

Skill0 starsChanged 4 months agoMITView on GitHub

Uses the AWS CLI safely for account and infrastructure tasks. Use when the user invokes /aws or asks to inspect or manage AWS resources.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use azure, gcloud and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ffsshhttiikkSkill

    azure

    Microsoft Azure cloud services and best practices

    Also in 4 projects that use this

  • GoogleSkill

    gcloud

    Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services and infrastructure. Use when planning, generating, constructing, proposing, describing, or executing any gcloud CLI commands - including when answering questions about gcloud syntax, or formatting flags. Don't use when writing Google Cloud client library code or raw REST/gRPC API requests.

    Also in 4 projects that use this

  • hoodiniSkill

    mongodb

    Work with MongoDB databases using best practices. Use when designing schemas, writing queries, building aggregation pipelines, or optimizing performance. Triggers on MongoDB, Mongoose, NoSQL, aggregation pipeline, document database, MongoDB Atlas.

    Also in 3 projects that use this

  • Sorcha-PlatformSkill

    redis

    Implements Redis caching, session management, and distributed coordination for the Sorcha platform. Use when: Adding caching layers, token revocation, rate limiting, SignalR backplane, or distributed state.

    Also in 3 projects that use this

  • mjunaidcaSkill

    kubernetes

    Production-grade Kubernetes manifests and debugging for containerized applications. This skill should be used when users ask to deploy to Kubernetes, create K8s manifests, containerize for K8s, set up Deployments/Services/Jobs/StatefulSets/CronJobs, create namespaces with resource quotas, set up multi-team isolation, configure ResourceQuota/ LimitRange, secure with RBAC (ServiceAccount, Role, RoleBinding), configure init containers (model download, db wait, migrations), set up sidecars (logging, metrics), or debug pods (CrashLoopBackOff, logs, exec, describe, events). Auto-detects from Dockerfile/code, generates hardened manifests with educational comments. CKAD-aligned.

    Also in 4 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user says /aws or asks to run AWS commands, manage EC2 instances, or query their AWS account.

    line 10
  2. Very specific:

    Prefer the profile in AWS_PROFILE.

    line 15
  3. Distinctive:

    Never assume a profile's permissions or mutate resources without the user's request.

    line 16
  4. Distinctive:

    Credentials: Use the AWS CLI credential chain, ideally IAM Identity Center (SSO) or another short-lived provider.

    line 20
  5. Very specific:

    Use AWS_REGION / AWS_DEFAULT_REGION when configured.

    line 41
  6. Very specific:

    Start/stop only when requested: aws ec2 start-instances --instance-ids i-xxx (and stop-instances)

    line 48
  7. Very specific:

    Prefer AWS IAM Identity Center (SSO): run aws configure sso, then aws sso login --profile <name>.

    line 53
  8. Distinctive:

    If static credentials are unavoidable, keep them outside repositories and rotate them regularly.

    line 54
  9. Distinctive:

    Start with read-only identity/status commands when account context is unclear.

    line 58
  10. Distinctive:

    If the AWS CLI is missing, point to the official AWS CLI v2 installer.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AWS (CLI)

When to use

Use this skill when the user says /aws or asks to run AWS commands, manage EC2 instances, or query their AWS account.

How to run AWS

  • Always use the AWS CLI (run aws in the terminal). Do not use boto3 or SDK in code unless the user explicitly asks for a script.
  • Prefer the profile in AWS_PROFILE; otherwise ask which configured profile to use.
  • Never assume a profile's permissions or mutate resources without the user's request.

Profile

  • Credentials: Use the AWS CLI credential chain, ideally IAM Identity Center (SSO) or another short-lived provider. Do not embed keys in prompts or code.

Invocation

Option A — env (preferred)
Set the profile for the current shell, then run aws:

$env:AWS_PROFILE="my-profile"       # PowerShell
# or
export AWS_PROFILE=my-profile       # Bash
aws sts get-caller-identity

Option B — flag
Pass the profile on every command:

aws ec2 describe-instances --profile my-profile --region us-east-1

Use AWS_REGION / AWS_DEFAULT_REGION when configured. Otherwise ask before a region-specific operation.

Common commands

  • Identity check: aws sts get-caller-identity
  • List instances: aws ec2 describe-instances
  • Instance status: aws ec2 describe-instance-status
  • Start/stop only when requested: aws ec2 start-instances --instance-ids i-xxx (and stop-instances)
  • Output: add --output table or --output json as needed.

Credentials: keys vs SSO

  • Prefer AWS IAM Identity Center (SSO): run aws configure sso, then aws sso login --profile <name>.
  • If static credentials are unavoidable, keep them outside repositories and rotate them regularly.

Notes

  • Start with read-only identity/status commands when account context is unclear.
  • If the AWS CLI is missing, point to the official AWS CLI v2 installer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.