github-apps

Automates provisioning, credential rotation, and installation validation of GitHub Apps for VibeTeam roles.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/VibeTechnologies/VibeTeam --skill github-apps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-apps
Source: https://github.com/VibeTechnologies/VibeTeam/tree/main/.agents/skills/github-apps
Command: npx skills add https://github.com/VibeTechnologies/VibeTeam --skill github-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provision and manage GitHub Apps for VibeTeam across roles, enabling centralized credential handling and streamlined installation workflows.

Core Features & Use Cases

  • Create per-role GitHub Apps with mapped credentials and clear naming.
  • Install apps to the VibeTechnologies org and target repos with precise permissions.
  • Validate app permissions, installations, and runtime attribution for automated governance.

Quick Start

Create a GitHub App for each role, install it in the VibeTechnologies organization, and map the generated credentials to environment variables for automated usage.

Frequently Asked Questions about github-apps

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

FAQPage Schema
How do I automate GitHub App provisioning for different organizational roles?

Automating GitHub App provisioning involves creating role-scoped apps with mapped credentials, installing them to target repositories with precise permissions, and validating the installation for governance. This Skill automates that entire workflow for the VibeTeam organization.

What is the best way to manage credential rotation for GitHub Apps?

Managing credential rotation for GitHub Apps requires secure key handling and mapping updated credentials to environment variables for deployment pipelines. This Skill provides ongoing management to rotate keys and validate app permissions automatically.

Can I set per-app permissions for GitHub Apps across multiple repositories?

Yes, setting per-app permissions across multiple repositories is supported. You can install apps into the VibeTechnologies organization and target specific repositories with precise permission checks to ensure automated governance.

How do I map GitHub App credentials to environment variables for deployment pipelines?

Mapping GitHub App credentials to environment variables requires generating the app credentials and configuring them within your deployment pipeline environment. This Skill provisions the app and maps the generated credentials for automated usage.

Does this GitHub App provisioning process support onboarding new roles like software engineers and product managers?

Yes, the provisioning process supports onboarding new roles including software_engineer, support_engineer, release_engineer, product_manager, and marketing_manager. It creates per-role GitHub Apps with clear naming and mapped credentials.

Why do I need per-role GitHub Apps instead of a single organizational app?

Per-role GitHub Apps provide role-scoped permissions and centralized credential handling, ensuring precise access control across multiple repositories. This approach satisfies governance requirements for secure key handling and webhook configuration better than a single app.