vellum-github-app-setup

Create an organization-owned GitHub App with vault-stored credentials and token refresh.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-github-app-setup-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vellum-github-app-setup
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/vellum-github-app-setup
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill vellum-github-app-setup-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Setting up GitHub access for an assistant usually requires users to create and manage credentials manually and ensure that commits, PRs, and comments are properly attributed to a stable bot identity.

Core Features & Use Cases

  • Creates an organization-owned GitHub App with a dedicated bot identity so automated git actions do not appear under the user’s personal account.
  • Generates and stores all required credentials in the assistant vault (including private key material) and records the installation ID after installation.
  • Enables authenticated repository operations via a token helper script that refreshes short-lived installation tokens for git pushes.
  • Use case: When an assistant needs to push commits and open PRs on behalf of your team, run this setup once so future automation uses APP_SLUG[bot] consistently.

Quick Start

Ask the assistant to run the GitHub App setup flow for your organization and store the resulting credentials in your assistant vault.

Frequently Asked Questions about vellum-github-app-setup

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

FAQPage Schema
How do I create a GitHub App for automated pull request automation under my organization?

To create a GitHub App for pull request automation, run the setup flow to provision an organization-owned app. This generates a dedicated bot identity so automated git actions and PRs attribute consistently to APP_SLUG[bot] instead of a personal account.

How do I get installation tokens for authenticated git push automation?

You obtain installation tokens for git push automation by using the provided token helper script. This script refreshes short-lived, 1-hour installation access tokens required for performing authenticated git operations against your repositories.

What's the best way to store GitHub App credentials and JWT signing keys for a bot?

The best way to store GitHub App credentials and JWT signing keys is directly in the assistant vault. The setup flow automatically saves the private key material and records the installation ID for secure JWT signing and token generation.

Does GitHub App setup use the manifest flow callback for obtaining app credentials?

Yes, GitHub App setup uses the manifest flow callback to securely obtain app credentials. This flow provisions the bot identity and captures the necessary installation details to enable authenticated repository operations.

Why do I need a separate bot identity instead of using a personal access token for GitHub commits?

You need a separate bot identity so automated commits and PRs are properly attributed to a stable APP_SLUG[bot] account. This prevents automated repository operations from appearing under a user's personal GitHub account.

Can I use a GitHub App to open PRs and push commits on behalf of my team?

Yes, you can use a GitHub App to open PRs and push commits on behalf of your team. Once configured, the assistant uses the bot identity and refreshed installation tokens to perform authenticated GitHub API actions consistently.