本文へ移動
cccskills
無料GitHub で公開

aws-database

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.

インストール方法を見る

含まれるファイル(21)

  • SKILL.md7.8 KB
  • assets/aurora-dsql.md1.4 KB
  • assets/aurora-mysql.md1.9 KB
  • assets/aurora-postgresql.md2.5 KB
  • assets/documentdb.md1.4 KB
  • assets/dynamodb.md2.9 KB
  • assets/elasticache.md3.4 KB
  • assets/keyspaces.md2.0 KB
  • assets/memorydb.md1.7 KB
  • assets/neptune.md2.1 KB
  • assets/odb-aws.md1.9 KB
  • assets/rds-db2.md1.1 KB
  • assets/rds-mariadb.md1.5 KB
  • assets/rds-mysql.md1.2 KB
  • assets/rds-oracle.md1.5 KB
  • assets/rds-postgresql.md1.4 KB
  • assets/rds-sqlserver.md1.3 KB
  • assets/timestream.md1.8 KB
  • references/handoff.md4.1 KB
  • references/report-issue.md3.9 KB
  • references/select.md19.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, I have an agent idea what do I build, move/migrate my agents to AWS, agent migration plan, add AgentCore services (memory, gateway, identity, policy, observability) to an agent already on AWS, Temporal on AWS (migrate/run Temporal workers on AWS, a service orchestrated by Temporal, Temporal Cloud vs self-hosted). Temporal Workflow code is never rewritten into Step Functions. Requires at least one agentic component — a purely non-agent system (plain services, batch jobs, HTTP endpoints, non-agent Temporal Activities) is out of scope, redirected to gcp-to-aws / heroku-to-aws / llm-to-bedrock. Not for: compute/data migration with no AI agent; pure LLM SDK rewrite (use llm-to-bedrock); per-model pricing.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "agent auth", "streaming", "VPC", "VPC connectivity", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "migration issue", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "add payments capability to my agent", "wire payments plugin", "integrate x402 payments with the agent I'm building", "add MPP payments", "Machine Payments Protocol". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI/dev-server errors: use agents-debug. Runtime x402/MPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: "agent not working", "wrong answer", "agent error", "tool call failing", "debug agent", "check logs", "read traces", "broken", "500 error", "424 error", "model access denied", "command not found", "stuck in DELETING", "maxVms exceeded", "cold start diagnosis", "cold start slow", "agentcore create error", "create failed", "exit code 7", "connection refused local dev". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK/IAM/quota error diagnosis, version management, rollback, and canary deployments. Triggers on: "deploy my agent", "agentcore deploy", "deploy failed", "CDK error", "rollback", "canary deploy", "pin version", "redeploy", "deploy stuck". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: "build an agent", "create an agent", "get started", "new project", "agentcore create", "which framework", "Strands vs LangGraph", "hello world agent", "first agent", "create MCP server", "host MCP server", "agentcore dev", "dev server", "what port", "local development". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.

日本語の概要は準備中です。原文の説明を表示しています。

aws/agent-toolkit-for-aws2,8442026年10月10日 更新

aws のスキルをすべて見る

このスキルの問題を報告する