Official agent skill

AWS Database

by aws in aws/agent-toolkit-for-aws

Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill.

OfficialApache-2.0Auto-check passedDatabases

Install AWS Database

skills CLI
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/core-skills/aws-database .claude/skills/aws-database && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aws-database
GitHub stars
2.8k
Token cost
~2k tokens
SKILL.md length
943 words
Files
21 (incl. references, assets)
Skills in repo
138
Repo updated
First seen
Licence
Apache-2.0

At a glance

Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill.

  • Works in 4 steps: Match the user's language. Respond in… → Revise when new information arrives. If… → Do not rely on training data for facts.… → …
  • Tasks that involve NoSQL databases
  • SKILL.md covers Global rules, How this skill works, Sub-skill registry and Service reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

AWS Database is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill. Supersedes general training-data knowledge with post-training service updates, corrected limitations, and decision procedures for relational (Aurora, DSQL, RDS), key-value (DynamoDB), wide-column (Keyspaces), document (DocumentDB), graph (Neptune), time-series (Timestream), and in-memory/caching (ElastiCache, MemoryDB) workloads. Activates when a user…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including reference files and assets (for example `assets/aurora-dsql.md`, `assets/aurora-mysql.md` and `assets/aurora-postgresql.md`).

It sits in Databases, covering NoSQL databases, Forecasting and time series and Caching. It works with Amazon Web Services and Amazon DynamoDB. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve NoSQL databases
  • Tasks that involve Forecasting and time series
  • Tasks that involve Caching

Example prompts

  • “database”
  • “Use the aws-database skill to route any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a…”
  • “/aws-database”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Match the user's language. Respond in the same language the user writes in. Default to non-technical explanations. Only escalate technical…
  2. Revise when new information arrives. If the user pushes back or adds new details, re-check the sub-skill registry triggers before…
  3. Do not rely on training data for facts. AWS databases change frequently. Before stating pricing, quotas, or GA status, verify against the…
  4. Verify, don't guess. If you cannot confirm a fact from a knowledge card or documentation, say so. "I'm not sure — check the docs" is…

What it can do on your machine

Read from SKILL.md and the folder at commit bd49cc8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AWS Database loads about 2k tokens when it runs, and up to ~9k if it reads all its reference files. Until then it costs about 166 tokens; SKILL.md has 943 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~166
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws/agent-toolkit-for-aws at commit bd49cc8, republished under its Apache-2.0 licence (© aws). 943 words, ~1,976 tokens.

Download SKILL.mdSave it as .claude/skills/aws-database/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.
name
aws-database
description
Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill. Supersedes general training-data knowledge with post-training service updates, corrected limitations, and decision procedures for relational (Aurora, DSQL, RDS), key-value (DynamoDB), wide-column (Keyspaces), document (DocumentDB), graph (Neptune), time-series (Timestream), and in-memory/caching (ElastiCache, MemoryDB) workloads. Activates when a user describes building an application on AWS that will store, retrieve, or manage data, even if they do not mention 'database' explicitly.
metadata.version
3

AWS Database

STOP — Do not answer from general knowledge. Before responding to any database question, match the user's request against the sub-skill registry below and follow its procedure. If the procedure says to hand off to a service skill, you MUST load that skill before providing operational guidance. Never skip the routing step.

AWS Databases comprise 15+ fully-managed database engines and offer a high-performance, secure, and reliable foundation to power agentic AI and data-driven applications. Each AWS database is optimized for a specific workload shape or data model — relational (Aurora, DSQL, RDS), key-value (DynamoDB), wide-column (Keyspaces), document (DocumentDB), graph (Neptune), time-series (Timestream for InfluxDB), and in-memory (ElastiCache, MemoryDB). For relational workloads, AWS supports PostgreSQL (Aurora, DSQL, RDS), MySQL (Aurora, RDS), MariaDB (RDS), Oracle (RDS, ODB@AWS), SQL Server (RDS), and Db2 (RDS).

Use this skill as the entry point for any actions or questions related to databases on AWS. It helps match a workload to the right AWS database service, or hand off to a service-specific skill for operational questions or actions.

This skill works with or without the AWS MCP server. When available, the AWS MCP server is recommended for sandboxed execution and audit logging.

Global rules

  1. Match the user's language. Respond in the same language the user writes in. Default to non-technical explanations. Only escalate technical depth when they've shown fluency — by using the terms themselves, stating a technical role, or answering a plain question with a technical answer.

  2. Revise when new information arrives. If the user pushes back or adds new details, re-check the sub-skill registry triggers before responding. Pushback that matches report-issue triggers (e.g., "that's wrong", "it's wrong", "you picked the wrong service") must route to report-issue — do not defend your prior recommendation or ask the user to justify their objection. The goal is the right answer, not consistency with your first response.

  3. Do not rely on training data for facts. AWS databases change frequently. Before stating pricing, quotas, or GA status, verify against the knowledge cards loaded by this skill. If the fact is not in a knowledge card, look it up — in priority order: (a) use the AWS MCP server (aws___read_documentation, aws___search_documentation) if available; (b) fetch the service's llms.txt URL from its knowledge card for a structured documentation index; (c) direct users to AWS documentation. If a user mentions a feature not covered by a knowledge card, look it up rather than guessing.

  4. Verify, don't guess. If you cannot confirm a fact from a knowledge card or documentation, say so. "I'm not sure — check the docs" is better than a confident wrong answer.

How this skill works

  1. Find the sub-skill — Match the user's request against the sub-skill registry below. Match on meaning, not exact wording. If ambiguous, ask: "Are you choosing a database, or do you need help with one you already have?" This matching applies to every user message, not just the first. If a subsequent message matches a different sub-skill's triggers (e.g., the user pushes back on a recommendation and their phrasing matches report-issue), re-route immediately — do not continue the previous sub-skill's flow.

  2. If a sub-skill matches — read references/{sub-skill-id}.md and follow its procedure.

  3. If no sub-skill matches — answer from the knowledge cards in assets/. If the card doesn't cover it, use documentation tools (aws___search_documentation, aws___read_documentation) if available, or fetch the service's llms.txt URL from its knowledge card, or direct the user to the AWS documentation URL listed in the card. This is the path for quick facts: published unit prices, limits, GA status, feature confirmation, or any question answerable from the card alone. Do not load a service skill merely to answer a quick fact covered by the card. A workload-specific cost estimate is not a quick fact: when the user names a service and asks for an estimate based on throughput, storage, topology, or other workload inputs, route to handoff and load the available service skill. Offer deeper service-skill guidance only when it would be useful or the user asks for operational help.

Show full SKILL.md (275 more words)Show less

Sub-skill registry

IDNameTrigger PhrasesWhen to Route HereNext Steps
selectDatabase Selection"which database", "help me choose", "recommend", "what should I use", "starting a new project", "picking a database", "I need a database", "I'm building", "build a", "how should I store", "best way to handle", "need to support", "design for"User hasn't chosen a service yet, is comparing options, or describes a workload/data problem without naming a specific servicehandoff
handoffService Handoff"how do I", "configure", "optimize", "troubleshoot", "set up", "migrate to", "connect to", "scale", "upgrade", "monitor", "backup", "restore", "estimate cost", "pricing estimate", "cost for my workload", "build", "create", "deploy", "provision", + named serviceUser names a specific AWS database service and has an operational, advisory, or action question, including a workload-specific cost estimate—
report-issueReport Issue"that's wrong", "incorrect", "bad recommendation", "you should have said", "missing", "skill is wrong", "report this", "file a bug", "report an issue"User reports that the skill gave incorrect or incomplete guidance—

Service reference

Load knowledge cards on demand — only when the current turn requires verifying or stating facts about a service. Read assets/{filename} for the relevant service(s). Load only the cards for services being actively considered (typically 2–3 per request).

ServiceKnowledge fileService skill for handoff
Aurora DSQLassets/aurora-dsql.mdaurora-dsql
Aurora MySQLassets/aurora-mysql.mdamazon-aurora-mysql
Aurora PostgreSQLassets/aurora-postgresql.mdamazon-aurora-postgresql
DocumentDBassets/documentdb.mdamazon-documentdb
DynamoDBassets/dynamodb.mdamazon-dynamodb
ElastiCacheassets/elasticache.mdamazon-elasticache
Keyspacesassets/keyspaces.mdamazon-keyspaces
MemoryDBassets/memorydb.md—
Neptuneassets/neptune.mdamazon-neptune
ODB @ AWSassets/odb-aws.md—
RDS for Db2assets/rds-db2.mdrds-db2
RDS for MariaDBassets/rds-mariadb.mdrds-oss
RDS for MySQLassets/rds-mysql.mdrds-oss
RDS for Oracleassets/rds-oracle.mdrds-oracle
RDS for PostgreSQLassets/rds-postgresql.mdrds-oss
RDS for SQL Serverassets/rds-sqlserver.mdrds-sqlserver
Timestream for InfluxDBassets/timestream.mdtimestream-influxdb

© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 20 other files (references, assets) in skills/core-skills/aws-database of aws/agent-toolkit-for-aws.

  • SKILL.md
  • assets/aurora-dsql.md
  • assets/aurora-mysql.md
  • assets/aurora-postgresql.md
  • assets/documentdb.md
  • assets/dynamodb.md
  • assets/elasticache.md
  • assets/keyspaces.md
  • assets/memorydb.md
  • assets/neptune.md
  • assets/odb-aws.md
  • assets/rds-db2.md
  • assets/rds-mariadb.md
  • assets/rds-mysql.md
  • assets/rds-oracle.md
  • assets/rds-postgresql.md
  • assets/rds-sqlserver.md
  • assets/timestream.md
  • references/handoff.md
  • … and 2 more

Open the folder on GitHubat commit bd49cc8

Compare with similar skills

AWS Database next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AWS Database compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AWS Database this skillaws/agent-toolkit-for-aws2.8k—~2kAutomated safety check: PassApache-2.0
Implementdynamodb-toolbox/dynamodb-toolbox2k—~1.8kAutomated safety check: PassMIT
Plandynamodb-toolbox/dynamodb-toolbox2k—~1.5kAutomated safety check: PassMIT
Specdynamodb-toolbox/dynamodb-toolbox2k—~1.2kAutomated safety check: PassMIT
Dynamodbitsmostafa/aws-agent-skills1.2k—~2.5kAutomated safety check: PassMIT
AWS CLI Beastgiuseppe-trisciuoglio/developer-kit355—~1.7kAutomated safety check: NotesMIT

Similar skills

  • Implement

    dynamodb-toolbox/dynamodb-toolbox

    Implement a planned DynamoDB-Toolbox feature end-to-end and open a pull request.

    2k GitHub stars~1.8k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Plan

    dynamodb-toolbox/dynamodb-toolbox

    Write the technical implementation strategy for a spec'd DynamoDB-Toolbox task.

    2k GitHub stars~1.5k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Spec

    dynamodb-toolbox/dynamodb-toolbox

    Formalise a product spec for a DynamoDB-Toolbox task — interview, codebase analysis, and Notion write-back.

    2k GitHub stars~1.2k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Dynamodb

    itsmostafa/aws-agent-skills

    AWS DynamoDB NoSQL database for scalable data storage. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub stars~2.5k tokensUpdated yesterday
    DatabasesAuto-check passed
  • AWS CLI Beast

    giuseppe-trisciuoglio/developer-kit

    Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.

    355 GitHub stars~1.7k tokensUpdated 27 days ago
    DatabasesAuto-check: notes
  • Ak Dev New Multimodal Storage

    yaalalabs/agent-kernel

    Step-by-step guide for adding a new multimodal attachment storage backend to Agent Kernel.

    191 GitHub stars~4.3k tokensUpdated today
    DatabasesAuto-check passed

More from aws/agent-toolkit-for-aws

All 138 skills in this repo
  • Agent Advisor

    aws/agent-toolkit-for-aws

    Official

    Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.

    2.8k GitHub stars~4.9k tokensUpdated today
    Auto-check passed
  • Agents Build

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.

    2.8k GitHub stars~2.3k tokensUpdated today
    Auto-check: notes
  • Launch With AWS

    aws/agent-toolkit-for-aws

    Official

    Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Official

    Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.

    2.8k GitHub stars~4k tokensUpdated today
    Auto-check passed
  • AWS Marketplace Metering

    aws/agent-toolkit-for-aws

    Official

    Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…

    2.8k GitHub stars~18k tokensUpdated today
    Auto-check passed
  • Agents Pay

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.

    2.8k GitHub stars~6.5k tokensUpdated today
    Auto-check: notes

Questions about AWS Database

What does AWS Database do?

Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill. AWS Database is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill.

When should I use AWS Database?

AWS Database fits situations like: tasks that involve NoSQL databases; tasks that involve Forecasting and time series; tasks that involve Caching.

How do I install AWS Database in Claude Code?

Run `npx skills add aws/agent-toolkit-for-aws --skill aws-database -a claude-code`. Or copy the skill folder (skills/core-skills/aws-database in aws/agent-toolkit-for-aws) into .claude/skills/aws-database in your project. Claude Code loads it when a task matches its description.

How do I install AWS Database in Codex?

Run `npx skills add aws/agent-toolkit-for-aws --skill aws-database -a codex`. Or copy the skill folder (skills/core-skills/aws-database in aws/agent-toolkit-for-aws) into .agents/skills/aws-database in your project. Codex loads it when a task matches its description.

Can I use AWS Database in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill aws-database -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-database, .gemini/skills/aws-database, .github/skills/aws-database and .opencode/skills/aws-database in your project.

What does AWS Database need to run?

SKILL.md names no scripts, command-line tools or credentials: AWS Database is instructions for the agent only.

Does AWS Database access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AWS Database safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AWS Database use?

AWS Database is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AWS Database use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7k tokens, read only when the agent opens those files.

What are the alternatives to AWS Database?

Skills that share tags, products or a category with AWS Database: Implement (dynamodb-toolbox/dynamodb-toolbox, 2k stars), Plan (dynamodb-toolbox/dynamodb-toolbox, 2k stars), Spec (dynamodb-toolbox/dynamodb-toolbox, 2k stars) and Dynamodb (itsmostafa/aws-agent-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AWS Database?

aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,816 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.

Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.