iam-helper-for-policy-management

Manages IAM allow and deny policies across Google Cloud resource hierarchies via gcloud CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing IAM allow policies (v1) and deny policies (v2) across organizations, folders, projects, and individual resources requires precise gcloud commands and careful safety checks, and mistakes can break live access controls. ## Core Features & Use Cases - Allow Policy Management: Add, remove, set, and inspect IAM v1 policy bindings at project, folder, organization, and service-specific resource levels. - Deny Policy Management: Create, update, list, and delete IAM v2 deny policies with YAML policy files, including long-running operation polling. - Safety Protocols: Enforces a plan-and-confirm workflow for mutating changes, post-execution verification steps, and refusal of public or blanket access grants. - Use Case: A platform engineer needs to grant a service account read access on a folder and simultaneously create a deny policy blocking role deletion at the organization level, with verification after each change. ## Quick Start Ask the assistant to add an IAM policy binding granting a user the viewer role on a specific Google Cloud project.

Frequently Asked Questions about iam-helper-for-policy-management

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

FAQPage Schema
How do I add an IAM policy binding to a Google Cloud project?▼

Use gcloud projects add-iam-policy-binding with the project ID, member identifier such as user:alice@example.com, and the role to grant. The skill formulates the exact command and asks for confirmation before applying it to the live environment.

How do I create an IAM deny policy with gcloud?▼

Run gcloud iam policies create with a policy name, the attachment point such as cloudresourcemanager.googleapis.com/projects/PROJECT_ID, --kind=denypolicies, and a YAML policy file defining denied principals and permissions.

What is the difference between IAM allow policies and deny policies?▼

Allow policies (v1) grant roles to principals on resources, while deny policies (v2) set guardrails blocking specified permissions regardless of granted roles. Deny rules are evaluated before allow rules.

Can I grant roles/owner to allUsers on a project?▼

No. The skill explicitly refuses to grant allUsers or allAuthenticatedUsers basic roles like owner, editor, or viewer due to severe security risks, and instead proposes scoped least-privilege bindings for specific identities.

How long do IAM policy changes take to propagate?▼

IAM allow and deny policy changes can take up to 7 minutes or longer to propagate across Google Cloud global infrastructure. Verification commands should be run after each mutating operation to confirm the active state.