cloud-databases-onboarding

Recommends Google Cloud databases from requirements and drafts validated Terraform provisioning code.

19.1k|1.5k|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/google/skills --skill cloud-databases-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-databases-onboarding
Source: https://github.com/google/skills/tree/main/skills/cloud/cloud-databases-onboarding
Command: npx skills add https://github.com/google/skills --skill cloud-databases-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Choosing the right Google Cloud database from a large portfolio (Cloud SQL, AlloyDB, Spanner, Bigtable, Firestore, Memorystore, and more) is difficult, and picking the wrong one leads to failed migrations and costly re-architecting. This Skill guides users through structured requirement discovery, recommends the optimal database using a curated recommendation matrix, and drafts validated infrastructure code for provisioning.

Core Features & Use Cases

  • Guided Requirement Discovery: Asks user-friendly questions about data model, workload type (OLTP/OLAP/HTAP), scale, latency, and migration context, enforcing a 90% confidence rule before recommending anything.
  • Matrix-Based Recommendation: Consults a detailed recommendation matrix covering migrations from MySQL, PostgreSQL, SQL Server, Oracle, HBase, DynamoDB, Cassandra, Redis, MongoDB, and more, mapping destination codes to plain-English product names.
  • Plan-Validate-Execute Provisioning: Drafts Terraform configuration with stamped headers and tracking tags, validates the code, and creates a Pull Request for review instead of applying changes directly.
  • Use Case: A team migrating a sharded MySQL deployment asks which database to use; the Skill gathers requirements, recommends Cloud Spanner with reasoning, then drafts and validates Terraform files and opens a PR for review.

Quick Start

Ask the agent: "Help me pick a Google Cloud database for my application" and answer the discovery questions to receive a recommendation and starter provisioning code.

Frequently Asked Questions about cloud-databases-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Google Cloud database for my application?

Start a discovery conversation describing your data model, workload type (OLTP, OLAP, or HTAP), scale, and latency requirements. The Skill asks targeted follow-up questions and recommends one Google Cloud database from its recommendation matrix once it reaches 90% confidence.

What databases can I migrate to Google Cloud with this guidance?

The recommendation matrix covers migrations from MySQL, PostgreSQL, SQL Server, Oracle, HBase, DynamoDB, Cassandra, Redis, Memcached, Aerospike, MongoDB, and graph databases like Neo4j. Destinations include Cloud SQL, AlloyDB, Spanner, Bigtable, Firestore, and Memorystore.

Does the Skill create database instances directly in Google Cloud?

No, it follows a Plan-Validate-Execute pattern that only drafts and validates Terraform configuration files, then creates a Pull Request for review. Live infrastructure changes like terraform apply or gcloud commands are left to human review or CI/CD pipelines.

How do I verify the database onboarding skill files are intact?

Run python3 scripts/database_onboarding_skill.py --verify from the skill directory. The script checks that all reference files exist and that prompt template formatting succeeds, reporting descriptive errors if anything is missing.

When should I not use this database selection workflow?

Do not use it for general Google Cloud maintenance, managing existing databases, or executing database migrations. It is designed only for new database selection and drafting starter provisioning code.