Skip to content
TakoAPI
Back to skills

ghapp

by rmorse

Coding Agents & IDEs
323Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Give your AI agents and automations their own GitHub (App) identity.

Description

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

INPUT

User asks: set up GitHub App authentication for my automation scripts

AGENT
  1. 1

    Run ghapp setup to launch the interactive wizard

  2. 2

    Enter the App ID, Installation ID, and path to the .pem private key

  3. 3

    Configure git and gh authentication with ghapp auth configure

  4. 4

    Verify the setup with ghapp auth status

OUTPUT

git clone, push, pull, and gh commands now authenticate as the GitHub App bot account

Requirements

  • GitHub App with App ID and Installation ID
  • GitHub App private key (.pem file)

Installation

clawhub install rmorse/ghapp

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links