slack-app

Provision and configure VibeTeam Slack apps with token wiring and routing validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provisioning and configuring Slack apps for VibeTeam to support an ingress app and per-role responders, wiring tokens and secrets, and validating routing/identity.

Core Features & Use Cases

  • Provision ingress app and role apps for SoftwareEngineer, SupportEngineer, ReleaseEngineer, ProductManager, MarketingManager.
  • Configure ingress manifest and event subscriptions URL, enable required bot events, and disable event subscriptions on role apps.
  • Install/Reinstall apps, invite to channels, map credentials to environment keys, and prepare deploy secrets for GitHub.

Quick Start

Create the ingress and role apps, wire credentials, and verify routing as described.

Frequently Asked Questions about slack-app

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

FAQPage Schema
How do I provision Slack apps with role-scoped bot tokens for multiple environments?

Provisioning Slack apps for role-based responders requires creating an ingress app to handle event subscriptions and separate role apps with unique bot tokens. It uses agents.yaml role mappings to configure distinct bot identities and maps secrets to environment keys for deployment.

What is the difference between an ingress Slack app and a role-scoped responder app?

An ingress Slack app handles incoming events by enabling event subscriptions and routing URLs, whereas role-scoped responder apps have event subscriptions disabled and use unique bot tokens to map to specific roles like SoftwareEngineer or ProductManager for targeted responses.

Do I need Slack admin access to configure event subscriptions and install role bots?

Yes, configuring event subscriptions, enforcing required bot scopes, installing apps, and inviting role bots to channels requires Slack admin access. This ensures proper app installation, secret mapping, and reliable routing validation via smoke testing.

How do I map Slack bot tokens and secrets to GitHub deploy environments?

You map Slack bot tokens and secrets to GitHub deploy environments by preparing deploy secrets from the provisioned apps. This wires the ingress and role app credentials to specific environment keys, ensuring reliable configuration and routing validation for deployment.

Why are my Slack role bots failing smoke tests after provisioning?

Slack role bots fail smoke tests when event subscriptions are incorrectly enabled on role apps, required bot scopes are missing, or secret mapping is incomplete. Proper provisioning disables event subscriptions on role apps and enforces required scopes for reliable routing validation.