What does this skill do, and when should you use it?
This skill is for developers and cloud engineers who need practical Cloud SQL setup guidance. It covers Cloud SQL resources for MySQL, PostgreSQL, and SQL Server, including the service’s managed backups, high availability, and secure connectivity. Its quick start uses PostgreSQL and walks through enabling the API, creating an instance and database, setting the default user password, and connecting through the Cloud SQL Auth Proxy. Additional references cover CLI usage, client libraries, MCP, Terraform, IAM, and security configuration.
Supplies commands for enabling the Cloud SQL Admin API, creating a PostgreSQL instance, setting the default postgres user password, creating a database, retrieving an instance connection name, starting the Cloud SQL Auth Proxy, and connecting with psql. It also points to reference material on instance architecture, high availability, supported engines, client libraries, remote MCP usage, Terraform, IAM, SSL/TLS certificates, and Auth Proxy configuration.
- A Google Cloud developer who needs a PostgreSQL Cloud SQL instance can follow the quick-start commands for initial setup.
- A cloud engineer managing MySQL, PostgreSQL, or SQL Server resources can use the instance, database, and user management references.
- An application developer connecting locally to Cloud SQL can follow the connection-name, proxy, and psql workflow.
- A platform team managing database infrastructure with Terraform can consult the infrastructure-as-code reference.
- A cloud administrator configuring permissions and secure connectivity can use the IAM, certificate, and Auth Proxy guidance.
How do you install this skill?
- Do not copy the plaintext-password, sslmode=disable, or --quiet examples directly into production; use Secret Manager, IAM database authentication, or a secure interactive credential flow.
- MCP capabilities for arbitrary SQL, import, update, and cloning can have substantial external effects; restrict permissions, disclose data flow, require confirmation, and prepare backup and recovery procedures.
- Some product versions, command flags, and dependency versions are not locally tested; verify them against current official documentation for the target engine.
- Shell / CLI
- Network access
- Local filesystem
- MCP Server
gcloud CLICloud SQL Auth Proxypsql
Run npx skills add google/skills and select skills/cloud/cloud-sql-basics during installation. The source describes selecting an individual skill from the repository but does not document version pinning or another installation method.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/google/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/cloud/cloud-sql-basics" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Create a Cloud SQL PostgreSQL instance and database
Use a request such as “Create a Cloud SQL PostgreSQL instance and database” to invoke the guidance. Follow the documented sequence: enable sqladmin.googleapis.com, run gcloud sql instances create, gcloud sql users set-password, and gcloud sql databases create, retrieve the connection name, start ./cloud-sql-proxy, and connect with psql. Appropriate IAM permissions are required; consult the linked references for advanced configuration.
What are this skill's strengths and limitations?
- Covers MySQL, PostgreSQL, and SQL Server.
- Includes copyable PostgreSQL quick-start commands.
- Links to CLI, client-library, Terraform, MCP, IAM, and security references.
- The collection is Apache-2.0 licensed and described as under active development.
- The quick start fully demonstrates PostgreSQL only, not MySQL or SQL Server.
- The workflow depends on the gcloud CLI, Cloud SQL Auth Proxy, and psql, and requires Cloud SQL permissions.
- The supplied source does not provide a test suite, version compatibility matrix, or cost guidance.
- This profile covers only Cloud SQL Basics and does not attribute sibling-skill capabilities to it.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Cloud SQL Essentials this page ✓ Google · Official | 45 · Not recommended | ★ 21k | 12d ago | Apache-2.0 |
| AlloyDB Database Manager ✓ Google · Official | 48 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Agent Platform Model Registry Manager ✓ Google · Official | 48 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Analytics Data Reporting Assistant ✓ Google · Official | 50 · Use with care | ★ 21k | 12d ago | Apache-2.0 |
| Google Cloud Borderless Lakehouse Architect ✓ Google · Official | 45 · Not recommended | ★ 21k | 12d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill discloses IAM roles, Auth Proxy, private networking, encryption, and service-account concepts, but the quick start asks for the full Cloud SQL Admin role, uses --quiet, places passwords directly in commands and connection strings, and sets sslmode=disable. The MCP section also describes arbitrary SQL execution, data import, and instance updates. Least-privilege defaults, per-action confirmation, data-flow disclosure, secret handling, and rollback guidance are incomplete, so points are deducted.
The command paths and connection approaches are broadly coherent, with coverage for CLI, client libraries, Terraform, and MCP. However, there are no tests, CI evidence, execution results, pinned versions, abnormal-input handling, or complete proxy setup and troubleshooting guidance. Static evidence cannot establish reproducible key paths, so the score is limited and reduced.
The trigger scenario is clear: creating or explaining Cloud SQL resources for MySQL, PostgreSQL, or SQL Server, with several usage paths provided. Input constraints, output expectations, non-fit scenarios, and semantic trigger boundaries are under-specified. Chinese-language support and mainland-China reachability are also not addressed, so points are deducted.
The main document and reference directory provide basic progressive disclosure, with installation guidance, examples, IAM security, Terraform, MCP, licensing, and an issue-reporting path. Explicit versioning, changelog policy, named maintenance responsibility, dependency governance, FAQs, and systematic limitation disclosure are missing, preventing a high score.
The quick start and references cover instances, databases, users, connectivity, and basic infrastructure as code, supporting the core onboarding task. Nevertheless, examples require substantial environment substitution and security correction, and no representative outputs are verified. Comparative value over manual documentation lookup is therefore only partially supported.
The material links to official documentation, Terraform Provider resources, MCP integrations, and installation instructions, providing some traceability. It contains no committed tests, CI coverage, execution logs, or independent reproduction evidence, and some factual and version claims cannot be verified from the supplied files alone. Static review therefore stays at or below 5.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →