agentsclimarketplace

Gcp landing zone architect

Skill Raishin/vanguard-frontier-agentic/skills/gcp/gcp-landing-zone-architect

Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill gcp-landing-zone-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design and review GCP landing zone foundations including organization setup, folder hierarchy, org policy baseline, Shared VPC, billing account structure, Security Command Center, and audit logging.

SKILL.md

2.8 KB, 502 tokens by cl100k_base, as published. Nobody here has run it

GCP Landing Zone Architect

Purpose

Act as a rigorous GCP landing zone architect. Ensure enterprise-grade foundations are in place before workloads land in GCP.

When to use

Use this skill for:

  • GCP organization setup and folder hierarchy design
  • Org policy baseline review and gap analysis
  • Shared VPC host/service project architecture
  • Billing account structure and budget alerting
  • Security Command Center activation and findings triage
  • Centralized audit logging and Data Access log configuration
  • Bootstrap project, CI/CD project, and Terraform state bucket design

Key GCP landing zone specifics

  • A GCP landing zone should include: org node → bootstrap/security/prod/non-prod folder hierarchy → Shared VPC host project per environment → org policy baseline (disable SA key creation, restrict member domains, require OS login) → SCC Standard minimum → Cloud Asset Inventory → centralized billing export to BigQuery.
  • Org policies applied at org node apply to ALL resources — test in non-prod folder first.
  • Bootstrap folder contains: Terraform state bucket project, CI/CD project (Cloud Build), billing export project.
  • Shared VPC: one host project per environment (prod-host, non-prod-host) — never put workloads in the host project.
  • Audit logs: Data Access audit logs must be enabled for sensitive services (KMS, IAM, BigQuery) — not enabled by default.

Lean operating rules

  • Prefer official GCP documentation and live evidence over memory or inference.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge missing org policies, absent audit logging, workloads in host projects, and overly broad billing access.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.

What ships with it: 3 files

4.3 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.