installation-token-generation

Generate GitHub App installation tokens for cross-repo automation workflows.

3|3|Updated Jan 4, 2026

Search Tags:#automation #scoping #github-actions #workflows #token #github-app #installation-token

Ready to run

npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill installation-token-generation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: installation-token-generation
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/installation-token-generation
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill installation-token-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the generation of GitHub App installation tokens to enable automated cross-repo workflows without user interaction.

Core Features & Use Cases

Organization-wide and repository-scoped tokens: generate tokens that grant access to all org repos or specific repos for CI/CD and automation tasks.
Cross-repo automation patterns: enables workflows spanning multiple repositories and teams.
Security-conscious scope: tokens are short-lived with explicit scope boundaries and auditable access.
Use Case: See examples in the repo for Single Repo, Organization-Wide, and Multi-Repository workflows.

Quick Start

Create a workflow that generates an installation token and uses it to access repositories in subsequent steps.

Frequently Asked Questions about installation-token-generation

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

FAQPage Schema

How do I generate a GitHub App installation token for cross-repo automation?▼

You can generate a GitHub App installation token by using the actions/create-github-app-token@v2 action in your workflows. This automates token creation to enable cross-repo automation without user interaction.

Can I scope a GitHub App installation token to specific repositories instead of an entire organization?▼

Yes, GitHub App installation tokens can be scoped to specific repositories. You can generate organization-wide, repository-scoped, or single-repo tokens to enforce security-conscious boundaries for your automation tasks.

When do I need a short-lived GitHub App token for GitHub Actions workflows?▼

You need a short-lived GitHub App token when running CI/CD workflows that span multiple repositories or teams. These tokens provide explicit scope boundaries and auditable access for cross-repo automation without user interaction.

How do I use actions/create-github-app-token to access multiple repos in a single workflow?▼

You create a GitHub Actions workflow that calls actions/create-github-app-token@v2 to generate an installation token, then pass that token to subsequent steps to authenticate and access repositories across your organization or specific scopes.

Do I need a GitHub App with specific permissions to generate installation tokens?▼

Yes, you need a GitHub App configured with appropriate permissions to generate installation tokens. The app's permission settings determine the scope and access level of the tokens created for your organization-wide or per-repository workflows.

What are the limitations of using GitHub App installation tokens for cross-repo workflows?▼

GitHub App installation tokens are short-lived and bound to explicit scope boundaries defined by the app's permissions. They require a pre-configured GitHub App and are limited to the organization-scoped or repository-scoped access granted to the app.