google-cloud-recipe-foundation-builder

Deploys a Google Cloud landing zone foundation with organization policies, folders, projects, and centralized logging.

Updated May 11, 2026
One-click install
npx skills add https://github.com/alon3153/upe-social-publisher --skill google-cloud-recipe-foundation-builder-alon3153
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: google-cloud-recipe-foundation-builder
Source: https://github.com/alon3153/upe-social-publisher/tree/main/.agents/skills/google-cloud-recipe-foundation-builder
Command: npx skills add https://github.com/alon3153/upe-social-publisher --skill google-cloud-recipe-foundation-builder-alon3153

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a new Google Cloud Organization securely requires manually configuring dozens of organization policies, building a resource hierarchy, linking billing, and wiring centralized audit logging — a slow, error-prone process that often skips critical security guardrails. ## Core Features & Use Cases - Baseline Security Guardrails: Enforces 17 recommended Organization Policies (13 Boolean, 4 List constraints) covering public access prevention, service account key restrictions, OS Login, and domain restrictions. - Resource Hierarchy Provisioning: Creates 4 folders (Common, Production, Non-Production, Development) and 4 billing-linked projects with required APIs enabled. - Centralized Logging & Monitoring: Deploys a global log bucket with 30-day retention, an organization-wide audit log sink, and a cross-project monitoring metrics scope. - Lazy IAM Remediation: Detects Permission Denied failures and self-remediates by granting the appropriate administrative role group, halting for manual intervention if remediation fails. - Use Case: A platform engineer setting up a brand-new Google Cloud Organization can run this recipe to establish a secure, enterprise-grade landing zone in one guided session instead of weeks of manual console work. ## Quick Start Ask the agent to set up a secure Google Cloud landing zone foundation for your organization, providing your Organization ID and billing account when prompted.

Frequently Asked Questions about google-cloud-recipe-foundation-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Google Cloud landing zone foundation?▼

Run this recipe with the gcloud CLI to enforce 17 baseline organization policies, create 4 folders and 4 billing-linked projects, and configure centralized audit logging with a 30-day retention log bucket. The agent gathers your Organization ID and Billing Account ID before deploying.

What organization policies does a Google Cloud foundation need?▼

This recipe enforces 17 baseline policies including public access prevention for storage, uniform bucket-level access, disabled service account key creation, required OS Login, restricted Cloud SQL public IPs, and domain-restricted IAM policy members.

What permissions are required to deploy a Google Cloud landing zone?▼

The deploying identity needs roles from four administrative groups: Organization Admin, Billing Admin, Logging/Monitoring Admin, and Security Admin. The recipe uses lazy remediation, granting missing role groups automatically when a Permission Denied error occurs.

Why does gcloud org-policies set-policy fail with Permission Denied?▼

The deploying identity lacks the Organization Policy Administrator role. The recipe self-remediates by granting the full Organization Admin role group via gcloud organizations add-iam-policy-binding, then retries the failed command.

Can this recipe be used for individual project onboarding?▼

No. This recipe is designed only for initial organization-level foundation setup. For onboarding individual projects into an existing foundation, use the google-cloud-recipe-onboarding skill or product-specific skills instead.

How do I set up centralized audit logging across Google Cloud projects?▼

The recipe creates a global log bucket with 30-day retention, an organization-level log sink routing cloud audit logs to that bucket, and a monitoring metrics scope linking the dev, non-prod, and prod projects to the central logging project.