Cloud sql basics

Skill h3y6e/agent-skills/.vendor/skills/cloud-sql-basics

my agent skills

Install

npx -y skills add h3y6e/agent-skills --skill cloud-sql-basics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source MySQL instance, the resulting resource is a Cloud SQL for MySQL instance that Google Cloud manages. Cloud SQL handles backups, high availability, and secure connectivity for relational database workloads.

SKILL.md

4.0 KB, 750 tokens by cl100k_base, as published. Nobody here has run it

Cloud SQL Basics

Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server. It automates time-consuming tasks like patches, updates, backups, and replicas, while providing high performance and availability for your applications.

Prerequisites

Ensure you have the necessary IAM permissions to create and manage Cloud SQL instances. The Cloud SQL Admin (roles/cloudsql.admin) role provides full access to Cloud SQL resources.

Quick Start (PostgreSQL)

Enable the API:

gcloud services enable sqladmin.googleapis.com --quiet

Create an Instance:

gcloud sql instances create INSTANCE_NAME \
  --database-version=POSTGRES_18 \
  --cpu=2 \
  --memory=7680MiB \
  --region=REGION \
  --quiet

Set a password for the default user:

Because this is a Cloud SQL for PostgreSQL instance, the default admin user is postgres:
```
gcloud sql users set-password postgres \
  --instance=INSTANCE_NAME --password=PASSWORD \
  --quiet
```

Create a database:

gcloud sql databases create DATABASE_NAME \
  --instance=INSTANCE_NAME \
  --quiet

Get the instance connection name:

You need the instance connection name (which is formatted as PROJECT_ID:REGION:INSTANCE_NAME) to connect using the Cloud SQL Auth Proxy. Retrieve it with the following command:
```
gcloud sql instances describe INSTANCE_NAME \
  --format="value(connectionName)" \
  --quiet
```
Connect to the instance:

The Cloud SQL Auth Proxy must be running to be able to connect to the instance. In a separate terminal, start the proxy using the connection name:
```
./cloud-sql-proxy INSTANCE_CONNECTION_NAME
```
With the proxy running, connect using psql in another terminal:
```
psql "host=127.0.0.1 port=5432 user=postgres dbname=DATABASE_NAME password=PASSWORD sslmode=disable"
```

Reference Directory

Core Concepts: Cloud SQL editions (Enterprise & Enterprise Plus), instance architecture, read pools, high availability (HA), and supported database engines.
CLI Usage: Essential gcloud sql commands for instance, database, and user management.
Client Libraries & Connectors: Connecting to Cloud SQL using Python, Java, Node.js, and Go.
MCP Usage: Using the Cloud SQL remote MCP server and Gemini CLI extension.
Infrastructure as Code: Terraform configuration for instances, databases, and users.
IAM & Security: Predefined roles, SSL/TLS certificates, and Auth Proxy configuration.
Disaster Recovery & Backups: Backup types, Point-in-Time Recovery (PITR), replicas, read pools comparison, and Enterprise Plus Advanced DR.

If you need product information not found in these references, use the Developer Knowledge MCP server search_documents tool.

What ships with it: 7 files

37.4 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most databases sql skills give in 750 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

Use parameterized queriesin 37 of 589, across 34 files
Use timestamptz for timestampsin 30 of 589, across 14 files
Index foreign keysin 29 of 589, across 18 files
Create indexes concurrentlyin 29 of 589, across 24 files
Use numeric type for moneyin 25 of 589, across 8 files
Use cursor pagination instead of offsetin 24 of 589, across 17 files
Select only required columnsin 24 of 589, across 20 files
Add indexes manually on foreign key columnsin 22 of 589, across 12 files
Normalize to third normal formin 19 of 589, across 10 files
Configure connection poolingin 19 of 589, across 17 files
Put equality columns before range columns in indexesin 18 of 589, across 10 files
Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

enable the sqladmin.googleapis.com API
create the Cloud SQL instance
set the default user password
create the database on the instance
get the instance connection name
start the Cloud SQL Auth Proxy

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.