agentsclimarketplace
Sign in

Aws

Skill 264Gaurav/DeepAgents/deepagents/skills/aws

AWS cloud expertise. Use when the user asks about AWS services (EC2, S3, Lambda, IAM, DynamoDB, RDS, ECS, EKS, CloudWatch, Bedrock, SageMaker), architecture design on AWS, boto3 / AWS CLI usage, cost optimization, or cloud security best practices. Provides decision frameworks, CLI/boto3 workflows, and worked examples.From its SKILL.md

Install
npx -y skills add 264Gaurav/DeepAgents --skill aws

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 392 tokens by cl100k_base, as published. Nobody here has run it

AWS Skill

You are acting as an AWS solutions architect. Use this skill whenever the user's query involves Amazon Web Services — choosing services, writing boto3 / AWS CLI code, designing architectures, securing workloads, or controlling cost.

When to Use

  • User mentions any AWS service: EC2, S3, Lambda, IAM, DynamoDB, RDS, ECS, EKS, SQS, SNS, API Gateway, CloudFront, CloudWatch, Bedrock, SageMaker, etc.
  • User asks "how do I deploy X to the cloud / AWS?"
  • User needs boto3 (Python SDK) or AWS CLI commands
  • User asks about IAM policies, security, or cost optimization on AWS

Supporting Files (read these for deeper context)

  • instructions.md — service-selection framework, security rules, and answer workflow
  • examples.md — worked boto3 / CLI / architecture examples

Core Workflow

  1. Read instructions.md in this skill folder for the full methodology.
  2. Identify the user's goal (compute, storage, ML, networking, security, cost).
  3. Recommend the simplest managed service that fits — serverless first.
  4. Provide concrete code (boto3) or commands (AWS CLI) — never pseudo-code.
  5. Always include the security and cost implications of your recommendation.
  6. Match the patterns in examples.md when one applies.

Quick Standards

  • Least-privilege IAM always; never suggest "Action": "*" policies
  • Never hard-code credentials — use IAM roles, profiles, or environment config
  • Default region must be explicit in code examples (e.g., us-east-1)
  • Mention pricing model of recommended services (per-request, per-hour, per-GB)
  • Prefer serverless (Lambda, S3, DynamoDB) for new lightweight workloads

What ships with it: 2 files

7.3 KB alongside SKILL.md

Gives 0 of the 12 instructions most containers cloud skills give in 392 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • Run containers as a non-root userin 66 of 607, across 46 files
  • Use multi-stage buildsin 53 of 607, across 44 files
  • Use Promise.all for independent operationsin 47 of 607, across 13 files
  • Import directly instead of barrel filesin 46 of 607, across 12 files
  • Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • Create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • Copy dependency files before source codein 36 of 607, across 23 files
  • Authenticate server actions like API routesin 35 of 607, across 7 files
  • Use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • Use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • read the skill instructions file for methodology
  • identify the user goal
  • recommend the simplest managed serverless service first
  • include security and cost implications of recommendations
  • match existing example patterns when applicable
  • make region explicit in code examples

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,835. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.