GCP Organization Policy constraints
Enforce org-level guardrails on GCP via gcloud and Terraform — dry-run before enforcement
- What
- Enforce org-level guardrails on GCP via gcloud and Terraform — dry-run before enforcement
- Cost
- Free
- Needs
- a GCP Organization with Organization Administrator role (org-level, not just a project); gcloud CLI and/or Terraform installed and authenticated
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a skill for implementing GCP Organization Policy constraints via gcloud and Terraform: restrict external IPs, resource locations, default service accounts and service account keys across the org/folder/project hierarchy, with dry-run testing of policy impact before enforcement. Use when enforcing security guardrails across an org's resource hierarchy or hardening GCP config at org, folder or project level. By @mukul975, listed here with credit to its creator. Honest caveats: it needs a GCP Organization with Organization Administrator role — not a plain project; policy changes take up to 15 minutes to propagate, and constraints can break existing workloads, so the dry-run step is the point, not a formality. Not verified. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
GCP Organization Policy constraints is a free Muse skill that enforces org-level guardrails on GCP via gcloud and Terraform, restricting external IPs, resource locations, default service accounts and service account keys across the org, folder and project hierarchy, with dry-run testing of the policy impact before any enforcement.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 54a7988Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a GCP Organization with Organization Administrator role (org-level, not just a project); gcloud CLI and/or Terraform installed and authenticated Install "GCP Organization Policy constraints" for me. Give my agent the skill for implementing GCP Organization Policy constraints — external IP restrictions, location constraints, service account controls — with dry-run impact testing before enforcement Repository: https://raw.githubusercontent.com/mukul975/anthropic-cybersecurity-skills/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-gcp-organization-policy-constraints/SKILL.md Pinned version: install the code at commit 54a798831d2266a3ca61ce68a7acb80b81160d57 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the mukul975-anthropic-cybersecurity-skills-implementing-gcp-organization-policy-constraints skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mukul975-anthropic-cybersecurity-skills-implementing-gcp-organization-policy-constraints". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the org admin role, authenticate gcloud/Terraform). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 54a7988 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.