Skip to content

ericrisco/rsc-harness / skills/gcp-essentials

gcp-essentials

Verified

Use when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege IAM wiring them together. NOT AWS (that is `aws-essentials`), NOT the CI pipeline that ships the image (that is `deployment`), NOT Postgres schema/query tuning (that is `postgresdb`).

FileKindSize
SKILL.mdskill md14.6 KB
evals/README.mdmarkdown788 B
evals/cases.yamlconfig2.5 KB
references/deploy-recipes.mdmarkdown2.7 KB
references/iam-and-auth.mdmarkdown3.7 KB
references/networking-and-sql.mdmarkdown3.2 KB
scripts/verify.shexecutablescript5.5 KB

references/networking-and-sql.md

View on GitHub
# Networking & Cloud SQL

Depth for the Cloud SQL and VPC parts of SKILL.md.

## Cloud Run egress: Direct VPC egress, not the legacy connector

To reach private IPs (a Cloud SQL private instance, an internal service) from Cloud
Run, prefer **Direct VPC egress** over the older Serverless VPC Access connector —
fewer moving parts, lower latency, no connector VM to size or pay for.

```bash
gcloud run deploy api --region=europe-west1 \
  --service-account=api-sa@acme-prod.iam.gserviceaccount.com \
  --network=projects/acme-prod/global/networks/default \
  --subnet=projects/acme-prod/regions/europe-west1/subnetworks/default \
  --vpc-egress=all-traffic
```

- `--vpc-egress=all-traffic` routes all outbound through the VPC. The older explicit
  Direct-VPC-egress value is deprecated in favour of `all-traffic`.
- `--vpc-egress=private-ranges-only` sends only RFC-1918 traffic through the VPC and
  lets public traffic exit directly — use it when only the DB is private.

The legacy `--vpc-connector` still works but is no longer the default recommendation;
do not provision a new connector for greenfield work.

## Cloud SQL private IP

Disable the public IP and give the instance a private address on your VPC. This is the
single biggest attack-surface reduction for a database.

```bash
# One-time: allocate a range and peer it (Service Networking)
gcloud compute addresses create google-managed-services-default \
  --global --purpose=VPC_PEERING --prefix-length=16 \
  --network=projects/acme-prod/global/networks/default
gcloud services vpc-peerings connect \
  --service=servicenetworking.googleapis.com \
  --ranges=google-managed-services-default \
  --network=default --project=acme-prod

# Create the instance with private IP, no public IP.
# --edition=ENTERPRISE is required: POSTGRES_16+ defaults to Enterprise Plus, which
# cannot run the shared-core db-f1-micro tier, so the create fails without it.
gcloud sql instances create acme-db \
  --database-version=POSTGRES_16 --edition=ENTERPRISE \
  --region=europe-west1 --tier=db-f1-micro \
  --no-assign-ip \
  --network=projects/acme-prod/global/networks/default
```

PSC (Private Service Connect) is the alternative when you need the instance reachable
from multiple VPCs or projects; enable it with `--enable-private-service-connect` and
allow the consumer projects.

## Cloud SQL Auth Proxy (for outside-VPC connections)

The proxy gives short-lived client certs and TLS 1.3 without managing certificates. Use
it for **local dev** or any non-serverless host — Cloud Run does **not** need it (it
uses the `/cloudsql/...` socket via `--add-cloudsql-instances`).

```bash
# Local dev against a private-IP instance over the proxy
./cloud-sql-proxy --private-ip acme-prod:europe-west1:acme-db
# then connect your client to 127.0.0.1:5432
```

## Connection pooling

Cloud SQL has a hard `max_connections` ceiling and Cloud Run can fan out to many
instances, each opening its own pool — you will exhaust connections under load. Keep
each instance's pool small (e.g. a few connections) and, for high concurrency, front
the database with a pooler (PgBouncer / a managed proxy) rather than raising
`max_connections`. Schema and query tuning beyond this is `postgresdb` territory.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall