access-management

Automate granting repository and shared resource access via CLI/API workflows.

8|1|Updated Aug 5, 2025

Search Tags:#devops #permissions #CLI #GitHub #access-management #collaborators #grant-access

Ready to run

npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill access-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: access-management
Source: https://github.com/ArtyMcLabin/ClaudeCode-global-config/tree/main/skills/access-management
Command: npx skills add https://github.com/ArtyMcLabin/ClaudeCode-global-config --skill access-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates granting access to repositories and shared resources, reducing manual coordination and preventing misconfigurations.

Core Features & Use Cases

Identity resolution and verification to accurately identify the user to grant access.
Deterministic workflow using CLI/API first (gh, gcloud) with a UI fallback as a last resort.
Safe, auditable permission changes for repositories and resources across teams.

Quick Start

To grant access, provide the exact user handle and desired permission level to your AI, along with the target resource (e.g., repository, project, or resource group). Example: Grant user [email protected] write access to repo/common-service.

Frequently Asked Questions about access-management

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

FAQPage Schema

How do I automate granting repository access to new collaborators?▼

Automating granting repository access is handled by resolving the target user's identity and applying deterministic CLI workflows. The process uses CLI/API tools first to safely add collaborators and update permissions without manual UI coordination.

What is the safest way to update team permissions for shared resources?▼

The safest way to update team permissions for shared resources is through deterministic, auditable CLI workflows. This approach prevents misconfigurations by resolving user identities first and falling back to UI only if API methods fail.

Can I use this access-management approach with GitHub and gcloud environments?▼

Yes, this access-management approach works with GitHub and gcloud environments. It prioritizes deterministic CLI/API commands for identity resolution and permission changes, providing a safe method to grant access across these platforms.

What happens if the CLI or API fails while updating collaborator permissions?▼

If the CLI or API fails while updating collaborator permissions, the workflow automatically falls back to a UI method. This ensures access grants are still completed safely when deterministic command-line tools encounter issues.

Do I need to manually verify user identities before granting repository access?▼

No, manual identity verification is not needed before granting repository access. The workflow includes built-in identity resolution and user confirmation to accurately target the correct user and prevent misconfigured permission grants.

Why should I use a deterministic workflow for sharing resources across teams?▼

You should use a deterministic workflow for sharing resources across teams to prevent misconfigurations and reduce manual coordination. It enforces auditable permission changes by standardizing access grants through CLI/API tools first.