What problem does it solve?
Turning an access request into a safe, reviewable infrastructure change is error-prone: personal emails must be KMS-encrypted before entering a public repo, the correct grant surface must be identified, and changes must never be applied locally. This Skill guides the full workflow from request to PR without leaking plaintext principals.
Core Features & Use Cases
- Encrypted principal registry: Registers human emails as opaque
human-NNN IDs via iam_principal.py, keeping personal emails out of the public repository, commits, and PR bodies.
- Two grant surfaces: Handles shared project/resource IAM in
iam_data.yaml (project roles, buckets, secrets, Artifact Registry, service accounts) and deploy-target IAM/IAP viewer grants for Echo, EvalDash, Grafana, and Loom.
- GitHub issue workflow: Fetches access-request issues with
gh, asks for missing details instead of guessing, and opens a properly labeled PR assigned to grant approvers.
- Use Case: A teammate files an issue asking for read access to the eval record bucket. The Skill registers their encrypted principal, adds the narrowest storage role to
iam_data.yaml, runs pre-commit checks, and opens a PR titled by capability for a reviewer to apply with pulumi up.
Quick Start
Ask the agent to grant a specific person read access to a named GCP resource in marin-iac and open a review PR.