break-glass
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Emergency IAM elevation for oncall/debugging. Discovers GCP projects and guides through granting/revoking permissions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- multiples-hq/business-state-machine-mcptheir own version, first seen Sep 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- multiples-hq/business-state-machine-mcp★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claim-ledgerSkill
- contract-parity-auditSkill
- counterfactual-auditSkill
- design-doc-reviewSkill
- diagram-gen-emergentSkill
- diagram-gen-specSkill
- doc-triageSkill
- explain-workSkill
- feature-implSkill
- finding-triageSkill
- first-party-auditSkill
- gh-token-rotateSkill
- handoffSkill
- implementSkill
- jj-stackSkill
- linear-escalation-triageSkill
- mache-usageSkill
- park-workSkill
- pr-boardSkill
- pr-bucketsSkill
- prior-art-cartographerSkill
- problem-decomposerSkill
- pr-review-kitSkill
- pr-reviewSkill
- pr-suggestionSkill
- readme-restructureSkill
- repo-description-polishSkill
- repo-homepage-setSkill
- repo-social-previewSkill
- repo-topic-taggerSkill
- review-prepSkill
- review-queueSkill
- reviewSkill
- self-auditSkill
- structural-pr-reviewSkill
- surveySkill
- taskfile-ci-paritySkill
- test-fidelitySkill
- workflow-auditSkill
- work-scopeSkill
- writing-pr-descriptionsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If user provided a project hint (like "staging", "dev", "prod"), search for matching projects:
- Distinctive: line 38
Ask user to confirm:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Break Glass - Emergency IAM Elevation
Help the user temporarily elevate their IAM permissions for oncall/emergency access to GCP projects.
Arguments
$ARGUMENTS
Workflow
1. Get current user
gcloud config get-value account2. Discover and match project
If user provided a project hint (like "staging", "dev", "prod"), search for matching projects:
gcloud projects list --format="value(projectId)" --filter="projectId~HINT OR name~HINT"Or list all accessible projects to help them choose:
gcloud projects list --format="table(projectId,name)" --limit=20Always confirm the exact project ID with the user before proceeding.
3. Confirm prerequisites
Ask user to confirm:
- Have you notified the appropriate slack channel?
- Have you raised a ticket per your org's process?
4. Determine role
Parse from arguments or ask. Map shortcuts:
storage->roles/storage.adminrun->roles/run.adminlogs->roles/logging.viewerpubsub->roles/pubsub.adminbigquery->roles/bigquery.adminowneror nothing specified ->roles/owner
5. Grant access
gcloud projects add-iam-policy-binding PROJECT_ID \
--member='user:USER_EMAIL' \
--role='ROLE'If prompted about conditions when ADDING:
- Choose [2] None (the options are: [1] EXPRESSION=..., [2] None, [3] Specify new)
6. Provide revoke command
Immediately after granting, give the exact revoke command:
gcloud projects remove-iam-policy-binding PROJECT_ID \
--member='user:USER_EMAIL' \
--role='ROLE'If prompted about conditions when REMOVING:
- Choose [1] None (the options are: [1] None, [2] all conditions)
- You added without a condition, so remove without a condition
7. Remind about cleanup
Tell user to:
- Revoke permissions when done
- Close their ticket
Example Usage
/break-glass staging- find projects matching "staging", grant owner/break-glass dev storage- find projects matching "dev", grant storage.admin/break-glass my-exact-project-id- use exact project ID/break-glass- list projects and ask what they need
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

