Implement
dynamodb-toolbox/dynamodb-toolbox
Implement a planned DynamoDB-Toolbox feature end-to-end and open a pull request.
Routes any task involving AWS databases — choosing, comparing, recommending, getting started with, or operating a database — to the correct service-specific skill.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .claude/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-databaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/core-skills/aws-database .agents/skills/aws-database && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .agents/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/core-skills/aws-database .cursor/skills/aws-database && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .cursor/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/agent-toolkit-for-aws.git --path skills/core-skills/aws-database--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/core-skills/aws-database .gemini/skills/aws-database && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .gemini/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/agent-toolkit-for-aws aws-databaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/core-skills/aws-database .github/skills/aws-database && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .github/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-database -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-database --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/core-skills/aws-database .opencode/skills/aws-database && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aws-database" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-database into .opencode/skills/aws-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-database", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
aws-databaseRoutes 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit bd49cc8. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.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.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.
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.
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.
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.
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.
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.
If a sub-skill matches — read references/{sub-skill-id}.md and follow its procedure.
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.
| ID | Name | Trigger Phrases | When to Route Here | Next Steps |
|---|---|---|---|---|
select | Database 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 service | handoff |
handoff | Service 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 service | User names a specific AWS database service and has an operational, advisory, or action question, including a workload-specific cost estimate | — |
report-issue | Report 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 | — |
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).
| Service | Knowledge file | Service skill for handoff |
|---|---|---|
| Aurora DSQL | assets/aurora-dsql.md | aurora-dsql |
| Aurora MySQL | assets/aurora-mysql.md | amazon-aurora-mysql |
| Aurora PostgreSQL | assets/aurora-postgresql.md | amazon-aurora-postgresql |
| DocumentDB | assets/documentdb.md | amazon-documentdb |
| DynamoDB | assets/dynamodb.md | amazon-dynamodb |
| ElastiCache | assets/elasticache.md | amazon-elasticache |
| Keyspaces | assets/keyspaces.md | amazon-keyspaces |
| MemoryDB | assets/memorydb.md | — |
| Neptune | assets/neptune.md | amazon-neptune |
| ODB @ AWS | assets/odb-aws.md | — |
| RDS for Db2 | assets/rds-db2.md | rds-db2 |
| RDS for MariaDB | assets/rds-mariadb.md | rds-oss |
| RDS for MySQL | assets/rds-mysql.md | rds-oss |
| RDS for Oracle | assets/rds-oracle.md | rds-oracle |
| RDS for PostgreSQL | assets/rds-postgresql.md | rds-oss |
| RDS for SQL Server | assets/rds-sqlserver.md | rds-sqlserver |
| Timestream for InfluxDB | assets/timestream.md | timestream-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
SKILL.md and 20 other files (references, assets) in skills/core-skills/aws-database of aws/agent-toolkit-for-aws.
Open the folder on GitHubat commit bd49cc8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AWS Database this skillaws/agent-toolkit-for-aws | 2.8k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Implementdynamodb-toolbox/dynamodb-toolbox | 2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Plandynamodb-toolbox/dynamodb-toolbox | 2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Specdynamodb-toolbox/dynamodb-toolbox | 2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Dynamodbitsmostafa/aws-agent-skills | 1.2k | — | ~2.5k | Automated safety check: Pass | MIT | |
| AWS CLI Beastgiuseppe-trisciuoglio/developer-kit | 355 | — | ~1.7k | Automated safety check: Notes | MIT |
dynamodb-toolbox/dynamodb-toolbox
Implement a planned DynamoDB-Toolbox feature end-to-end and open a pull request.
dynamodb-toolbox/dynamodb-toolbox
Write the technical implementation strategy for a spec'd DynamoDB-Toolbox task.
dynamodb-toolbox/dynamodb-toolbox
Formalise a product spec for a DynamoDB-Toolbox task — interview, codebase analysis, and Notion write-back.
itsmostafa/aws-agent-skills
AWS DynamoDB NoSQL database for scalable data storage. An agent skill from itsmostafa/aws-agent-skills.
giuseppe-trisciuoglio/developer-kit
Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.
yaalalabs/agent-kernel
Step-by-step guide for adding a new multimodal attachment storage backend to Agent Kernel.
aws/agent-toolkit-for-aws
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.
aws/agent-toolkit-for-aws
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.
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
aws/agent-toolkit-for-aws
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.
Works with
Categories
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.
AWS Database fits situations like: tasks that involve NoSQL databases; tasks that involve Forecasting and time series; tasks that involve Caching.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: AWS Database is instructions for the agent only.
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.
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.
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.
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.
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.
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.