ericrisco/rsc-harness / skills/gcp-essentials
gcp-essentials
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.6 KB |
| evals/README.md | markdown | 788 B |
| evals/cases.yaml | config | 2.5 KB |
| references/deploy-recipes.md | markdown | 2.7 KB |
| references/iam-and-auth.md | markdown | 3.7 KB |
| references/networking-and-sql.md | markdown | 3.2 KB |
| scripts/verify.shexecutable | script | 5.5 KB |
evals/cases.yaml
View on GitHubskill: gcp-essentials
should_trigger:
- prompt: "Deploy this container to Cloud Run with the gcloud CLI and keep it private."
why: "Cloud Run deployment with gcloud is the core GCP runtime path this skill owns."
- prompt: "Set up a small GCP project with Cloud SQL Postgres and a storage bucket."
why: "Project bootstrap plus Cloud SQL and Cloud Storage are core primitives in the skill."
- prompt: "Why is my Cloud Run service using the default compute service account?"
why: "Avoiding the default compute service account is a named IAM footgun this skill handles."
- prompt: "Connect Cloud Run to Cloud SQL without exposing the database publicly."
why: "Cloud Run to Cloud SQL with private/safe connectivity is a central workflow."
- prompt: "Crear un bucket en GCP bloqueando acceso publico y usando IAM correctamente."
why: "Spanish GCP bucket setup with public access prevention and IAM maps directly to Cloud Storage guidance."
should_not_trigger:
- prompt: "Deploy this app to AWS Lambda with S3 and RDS."
route_to: "aws-essentials"
why: "AWS services belong to the AWS cloud skill, not GCP."
- prompt: "Tune this Postgres query and choose indexes after EXPLAIN ANALYZE."
route_to: "postgresdb"
why: "Postgres schema/query tuning is the database skill; GCP only owns Cloud SQL operations."
- prompt: "Create a Dockerfile and GitHub Actions workflow to build my image."
route_to: "deployment"
why: "Container build and CI/CD mechanics are deployment work, not GCP service setup."
- prompt: "Review this authentication code for injection and broken authorization."
route_to: "security-audit"
why: "Application security review belongs to security-audit."
capability:
- scenario: "A developer says: 'I need a private Cloud Run API connected to Cloud SQL and a bucket, with least-privilege IAM. Give me the safe gcloud shape.'"
must_include:
- "Creates or selects a GCP project and enables only required APIs."
- "Creates a dedicated runtime service account and explicitly avoids the default compute service account."
- "Deploys Cloud Run with --service-account and --no-allow-unauthenticated unless a public endpoint is intentional."
- "Creates Cloud Storage with uniform bucket-level access and public access prevention."
- "Uses Secret Manager for DB password/secrets, not plaintext env vars."
- "Connects Cloud Run to Cloud SQL with the proper instance attachment/socket guidance."
- "Keeps IAM grants narrow and uses predefined roles instead of Owner/Editor."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |