Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
No significant code or documentation changes; SKILL.md reorganized for clarity. - Streamlined SKILL.md to focus on core setup and command usage. - Clarified setup steps and command explanations. - Revised authentication mode descriptions for brevity. - Removed some detailed usage notes for a more concise overview. - No functional or file content changes in this release.
What This Skill Does
ghapp authenticates git and gh commands as a GitHub App installation, using short-lived tokens instead of personal access tokens. Commits and API actions are attributed to the app's bot account rather than any individual user.
GitHub App tokens have higher rate limits and cleaner audit trails than personal access tokens, and bot-attributed commits keep team history uncluttered.
When to use it
- Pushing commits from CI pipelines as a bot account
- Opening pull requests from automation without using a personal token
- Running scheduled scripts that interact with GitHub repositories
- Separating bot activity from personal GitHub account history
- Authenticating in containers or headless environments without user credentials
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: set up GitHub App authentication for my automation scripts
- 1Run ghapp setup to launch the interactive wizard
- 2Enter the App ID, Installation ID, and path to the .pem private key
- 3Configure git and gh authentication with ghapp auth configure
- 4Verify the setup with ghapp auth status
git clone, push, pull, and gh commands now authenticate as the GitHub App bot account
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.