smithery/jpoutrin

gcp-cloud

Google Cloud Platform infrastructure patterns and best practices. Use when designing or implementing GCP solutions including Compute Engine, Cloud Functions, Cloud Storage, and BigQuery.

Installation

$ npx skills add smithery/jpoutrin --skill gcp-cloud

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/jpoutrin · top by installs.

npx skills add smithery/jpoutrin

Browse all from smithery/jpoutrin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,557 B
  • docs SUMMARY.md 203 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

GCP Cloud Skill

This skill provides GCP architecture patterns and best practices.

Core Services

Service Use Case
Compute Engine Virtual machines
Cloud Functions Serverless functions
Cloud Run Containers serverless
Cloud Storage Object storage
Cloud SQL Managed databases
BigQuery Data warehouse
GKE Kubernetes

Terraform Patterns

# GKE cluster
resource "google_container_cluster" "primary" {
  name     = "my-cluster"
  location = "us-central1"

  remove_default_node_pool = true
  initial_node_count       = 1

  workload_identity_config {
    workload_pool = "${var.project_id}.svc.id.goog"
  }
}

Security Best Practices

  • Use Workload Identity (not service account keys)
  • Enable VPC Service Controls
  • Use Cloud IAM for access management
  • Enable Cloud Audit Logs
  • Use Customer-Managed Encryption Keys
  • Enable Binary Authorization for GKE

BigQuery Patterns

-- Partitioned table for cost optimization
CREATE TABLE mydataset.events
PARTITION BY DATE(event_time)
CLUSTER BY user_id
AS SELECT * FROM staging.events;

Cost Optimization

  • Use Committed Use Discounts
  • Use Preemptible VMs for batch
  • Enable autoscaling
  • Use BigQuery slot reservations
  • Archive to Coldline/Archive storage