Take a stack that already works under `flisk up` to Google Cloud with that host's own tooling - Cloud Run, GKE, App Engine or Compute Engine. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Google Cloud. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Gcp?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-gcp)
---
name: flisk-deploy-gcp
description: Take a stack that already works under `flisk up` to Google Cloud with that host's own tooling - Cloud Run, GKE, App Engine or Compute Engine. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Google Cloud. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. gcloud CLI recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Google Cloud
Flisk is local-only. This skill covers taking a validated local stack to GCP.
## Workflow
1. Confirm the stack works locally: `flisk doctor && flisk up <stack>`.
2. Extract the contract from service.json.
3. Preferred target: Cloud Run for containers, or GKE for more complex stacks.
4. Build and push the production image to Artifact Registry.
5. Deploy with Cloud Run service YAML or `gcloud run deploy`, mapping env and secrets from Secret Manager.
6. Verify the health endpoint.
## Guardrails
- Do not deploy local generated files.
- Use production-grade images and secret management.
