How do I install the GCP Deployment skill?

Run npx skillmds@latest add mayarid/gcp-deployment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is GCP Deployment safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with GCP Deployment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is GCP Deployment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published GCP Deployment?

mayarid (@mayarid) published this skill. Their other Agent Skills are listed on their SkillMD profile.

GCP Deployment by mayarid — Agent Skill

Name: GCP Deployment
Author: mayarid

File contents

Context

Deploying {{project_name}} ({{project_type}}) to Google Cloud Platform (GCP). You will follow a strict 6-phase Deployment Lifecycle Contract.

Instructions

Execute the following phases in order:

Phase 1: Authentication

Ensure the GOOGLE_APPLICATION_CREDENTIALS environment variable is set to a valid service account key JSON file, or configure Workload Identity Federation (if inside CI/CD).
Authenticate the gcloud CLI: gcloud auth activate-service-account --key-file=$GOOGLE_APPLICATION_CREDENTIALS.
Set the default project: gcloud config set project <PROJECT_ID>.

Phase 2: Build

Prepare the artifacts for deployment.
If Cloud Run or GKE: build your Docker image (e.g., docker build -t gcr.io/<PROJECT_ID>/<APP_NAME> . or gcloud builds submit --tag gcr.io/<PROJECT_ID>/<APP_NAME>).
If App Engine: prepare app.yaml.
If Static Site (Cloud Storage): run npm run build.

Phase 3: Install / Provisioning

Ensure the target GCP resources (Cloud Run services, Buckets, Compute Instances) exist and you have permissions to write to them.
If Cloud Storage: gsutil ls gs://<bucket-name>.
Enable necessary APIs (e.g., gcloud services enable run.googleapis.com if using Cloud Run).

Phase 4: Deploy

Ship the artifact to GCP.
Cloud Run: gcloud run deploy <SERVICE_NAME> --image gcr.io/<PROJECT_ID>/<APP_NAME> --region <REGION> --platform managed.
App Engine: gcloud app deploy.
Cloud Storage: gsutil rsync -R dist/ gs://<bucket-name>.

Phase 5: Checking

Verify the deployment was successful.
Cloud Run: Check the returned service URL via curl and inspect gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>" if it fails.
App Engine: Check the target URL.
Ensure the service returns HTTP 200.

Phase 6: Update / Rollback

If Phase 5 fails, immediately initiate a rollback.
Cloud Run: Route 100% of traffic to the previous revision (gcloud run services update-traffic <SERVICE_NAME> --to-revisions=<PREVIOUS_REVISION_NAME>=100 --region <REGION>).
App Engine: Roll back traffic to an older version via gcloud app services set-traffic.
Note the failure in the progress log.

Validation

GCP authentication succeeds.
Build succeeds.
Artifacts are deployed.
Health check (curl) returns 200 OK.

---name: gcp-deploymentdescription: Deep knowledge about deploying applications to Google Cloud Platform (Cloud Run, App Engine, Compute Engine).---## ContextDeploying {{project_name}} ({{project_type}}) to Google Cloud Platform (GCP).You will follow a strict 6-phase Deployment Lifecycle Contract. ## InstructionsExecute the following phases in order:### Phase 1: Authentication1. Ensure the `GOOGLE_APPLICATION_CREDENTIALS` environment variable is set to a valid service account key JSON file, or configure Workload Identity Federation (if inside CI/CD).2. Authenticate the gcloud CLI: `gcloud auth activate-service-account --key-file=$GOOGLE_APPLICATION_CREDENTIALS`.3. Set the default project: `gcloud config set project <PROJECT_ID>`.### Phase 2: Build1. Prepare the artifacts for deployment.2. If Cloud Run or GKE: build your Docker image (e.g., `docker build -t gcr.io/<PROJECT_ID>/<APP_NAME> .` or `gcloud builds submit --tag gcr.io/<PROJECT_ID>/<APP_NAME>`).3. If App Engine: prepare `app.yaml`.4. If Static Site (Cloud Storage): run `npm run build`.### Phase 3: Install / Provisioning1. Ensure the target GCP resources (Cloud Run services, Buckets, Compute Instances) exist and you have permissions to write to them.2. If Cloud Storage: `gsutil ls gs://<bucket-name>`.3. Enable necessary APIs (e.g., `gcloud services enable run.googleapis.com` if using Cloud Run).### Phase 4: Deploy1. Ship the artifact to GCP.2. Cloud Run: `gcloud run deploy <SERVICE_NAME> --image gcr.io/<PROJECT_ID>/<APP_NAME> --region <REGION> --platform managed`.3. App Engine: `gcloud app deploy`.4. Cloud Storage: `gsutil rsync -R dist/ gs://<bucket-name>`.### Phase 5: Checking1. Verify the deployment was successful.2. Cloud Run: Check the returned service URL via `curl` and inspect `gcloud logging read "resource.type=cloud_run_revision AND resource.labels.service_name=<SERVICE_NAME>"` if it fails.3. App Engine: Check the target URL.4. Ensure the service returns HTTP 200.### Phase 6: Update / Rollback1. If Phase 5 fails, immediately initiate a rollback.2. Cloud Run: Route 100% of traffic to the previous revision (`gcloud run services update-traffic <SERVICE_NAME> --to-revisions=<PREVIOUS_REVISION_NAME>=100 --region <REGION>`).3. App Engine: Roll back traffic to an older version via `gcloud app services set-traffic`.4. Note the failure in the progress log.## Validation- [ ] GCP authentication succeeds.- [ ] Build succeeds.- [ ] Artifacts are deployed.- [ ] Health check (curl) returns 200 OK.

Frequently asked questions

GCP Deployment