AWSBestPracticesSkill banner
ferdinandobons ferdinandobons

AWSBestPracticesSkill

DevOps community

Description

Unofficial source-linked AWS best practices for every AWS service, organized by Well-Architected pillar for Claude Code, OpenAI Codex, and AI coding agents.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

AWS Best Practices Skill

**Ask your AI coding agent "how should I secure my S3 bucket" and get sourced, locally cataloged AWS best practices, skipping both stale training data and costly live research.**

A skill for **Claude Code** and **OpenAI Codex** that collects the **best practices of every AWS service**, and nothing else. Find recommendations by **use case**: security, reliability, performance, cost, operations, sustainability, each one linked to its official AWS source.

**Project page:**

**Latest release:** [v0.1.5](https://github.com/ferdinandobons/AWSBestPracticesSkill/releases/tag/v0.1.5)

**Unofficial project:** this is an independent community-maintained skill. It is not an official AWS skill, AWS product, or AWS-maintained resource, and it is not affiliated with or endorsed by Amazon Web Services.

**Scope:** this skill contains **only best practices**. No service descriptions, no pricing, no tutorials, no code walkthroughs. Just what AWS recommends you do, organized so you can act on it, each item linked to its official AWS source.

Why this instead of just asking the model directly

There are three ways an AI agent can answer "what are the best practices for this AWS service":

  1. From memory: free and instant, but the model's training data goes stale the moment AWS ships a new feature, renames a service, or updates its Well-Architected guidance. It will still answer confidently even when it's wrong or out of date.
  2. Live research: the agent runs web searches or queries an AWS documentation MCP server on the spot, every time. This gets it right, but it's expensive: several search → fetch → read round-trips, burning tens of thousands of tokens, repeated for every question, even the same one asked twice.
  3. This skill: the research is already done, once, per service, and stored as a small, source-linked file. The agent opens exactly `