iam-helper-for-troubleshooting

Diagnoses and remediates IAM access denials on Google Cloud through structured troubleshooting workflows.

23.7k|2.0k|Updated Mar 31, 2026
Ready to run
npx skills add https://github.com/google/skills --skill iam-helper-for-troubleshooting-google
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: iam-helper-for-troubleshooting
Source: https://github.com/google/skills/tree/main/skills/cloud/iam-helper-for-troubleshooting
Command: npx skills add https://github.com/google/skills --skill iam-helper-for-troubleshooting-google

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Developers and administrators waste hours troubleshooting cryptic IAM permission errors without clear visibility into why access was denied. This Skill eliminates guesswork by diagnosing the exact root cause—whether a deny policy blocks access, an allow policy is missing, or a Principal Access Boundary boundary restricts access—then guiding the appropriate remediation path based on the caller's privileges. ## Core Features & Use Cases - Two-Mode Operation: Requester Flow for developers to self-diagnose and activate Privileged Access Manager (PAM) JIT grants, or Resolver Flow for administrators to authoritatively analyze policies and provision access. - Root Cause Analysis: Uses Google Cloud's Policy Troubleshooter API and MCP to evaluate allow policies, deny policies, and PAB boundaries across the resource hierarchy. - Structured Remediation: Guides users through creating deny exemptions, updating PAB policies, discovering least-privileged roles, or provisioning time-bound PAM access. - Use Case: A developer encounters error 403 when creating a BigQuery dataset. This Skill captures the error ID, invokes Policy Troubleshooter, discovers that a deny policy blocks the bigquery.datasets.create permission, and escalates the issue with structured ticket details to an administrator for deny exemption. ## Quick Start Provide an error ID or specify the principal email, resource URI, and missing IAM permission, and the Skill will run Policy Troubleshooter to diagnose whether access is blocked by deny policies, missing allow policies, or PAB boundaries.

Frequently Asked Questions about iam-helper-for-troubleshooting

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

FAQPage Schema
How do I troubleshoot a 403 access denied error on Google Cloud?▼

Extract the error ID from the 403 response or provide your email, the resource URI, and the missing permission. The Skill uses Policy Troubleshooter to determine whether a deny policy blocks access, an allow policy is missing, or a Principal Access Boundary restricts your access.

What is the difference between Requester Flow and Resolver Flow?▼

Requester Flow guides developers encountering access denials to activate PAM JIT grants or escalate to administrators. Resolver Flow guides privileged administrators through authoritative policy analysis, deny exemption creation, least-privileged role discovery, and IAM provisioning.

Can this Skill automatically grant me access to a Google Cloud resource?▼

The Skill can activate time-bound PAM entitlements if pre-approved entitlements exist, or provision permanent role bindings if you hold project IAM admin rights. All provisioning operations require explicit human approval before execution.

What happens if an IAM deny policy blocks my access?▼

The Skill diagnoses the blocking deny policy and escalates to an administrator, who can add you as an exception principal or modify the policy scope. Developers cannot directly modify deny policies; only administrators with `roles/iam.denyAdmin` can grant exemptions.

How does the Skill find the least-privileged role for a missing permission?▼

The Skill runs the `least_privileged_role.py` script to query predefined and project custom roles, filtering for those that include the required permission and sorting by role scope and permission count to surface the minimal role needed.

Why does the Skill terminate troubleshooting when access state is UNKNOWN?▼

UNKNOWN access state indicates missing permissions to expand group memberships (requires `roles/browser`) or read parent project policies. The Skill cannot diagnose further without these permissions, so it halts to prevent misleading conclusions.