vellum-github-app-setup

Set up a GitHub App under an organization with manifest flow and vault storage.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CerisonAutomation/clud --skill vellum-github-app-setup-cerisonautomation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vellum-github-app-setup
Source: https://github.com/CerisonAutomation/clud/tree/main/skills/vellum-github-app-setup
Command: npx skills add https://github.com/CerisonAutomation/clud --skill vellum-github-app-setup-cerisonautomation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, bun, and includes scripts (resource) components.

What problem does it solve?

Creating a dedicated GitHub App identity for an assistant is error-prone and involves multiple manual steps, including manifest form setup, OAuth-style credential exchange, installation selection, and token refresh for pushing commits and opening PRs.

Core Features & Use Cases

  • Guided GitHub App creation (manifest flow): Opens a browser flow, submits a pre-filled manifest, and captures the credentials JSON automatically.
  • Repository installation with controlled permissions: Helps you install the App on selected repositories with sensible default scopes for git operations and PR interactions.
  • Vault storage and token helper automation: Stores the App credentials securely and provides a bun-based token refresher (gh-app-token.mjs) for short-lived installation tokens (1 hour).
  • Git configuration for bot-attributed commits: Sets user.name and user.email so pushes and PR activity attribute to <app-slug>[bot] consistently.
  • Optional logo upload instructions: Explains the limitation that the manifest flow can’t upload logos, so you complete it via the GitHub UI.

Quick Start

Tell the assistant: "Run the GitHub App setup skill for ORG_NAME with app name APP_NAME, then install it on my target repositories and prepare the workspace so pushes and PR comments use the app bot identity."

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 set up a GitHub App to authenticate an assistant for git push and pull requests?▼

To set up a GitHub App for git push and pull requests, you use a guided manifest flow to create the app under an organization, install it on target repositories, and configure git remotes. This grants the assistant a dedicated bot identity for attributed commits and PR comments.

Why do my automated GitHub commits need a dedicated bot identity instead of a personal token?▼

A dedicated bot identity is needed for automated GitHub commits so that pushes and PR comments attribute consistently to a specific `<app-slug>[bot]` user. This separates automated assistant activity from personal user accounts, improving audit trails and repository security.

What's the best way to get short-lived installation tokens for a GitHub App?▼

The best way to get short-lived GitHub App installation tokens is by signing a JWT and exchanging it for an access token via an automated token helper. This Skill provides a `bun`-based refresher script that generates fresh installation tokens that expire every hour.

Does GitHub App setup via the manifest flow support uploading a custom logo?▼

GitHub App setup via the manifest flow does not support uploading a custom logo automatically. Because of this known limitation, you must complete the logo upload manually through the GitHub UI after the initial credential exchange and app creation process finishes.

Do I need Python and Bun to automate GitHub App credential storage and token refresh?▼

Yes, you need Python and Bun installed to automate GitHub App credential storage and token refresh. The setup relies on Python for the initial manifest flow and credential vault storage, while a Bun script handles the generation of short-lived installation tokens.

Can I configure git to automatically use my GitHub App bot identity for all repository pushes?▼

Yes, you can configure git to use your GitHub App bot identity for repository pushes by setting the workspace `user.name` and `user.email` configurations. The setup workflow updates your git remotes so subsequent pushes and PR interactions consistently attribute to the bot.