Slack App Scaffold
Apps & Automationslack-app-scaffoldSlack App Scaffold is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Scaffold Slack apps from existing functionality using Bolt for JavaScript and the Slack CLI. Use when turning a service, script, or workflow into a Slack app with events, commands, modals, or automations.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/communication/slack-app-scaffold/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/slack-app-scaffold, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Slack App Scaffold
Bolt for JavaScript + Slack CLI is the 2026 default. Optimize for fast local runs, clear handlers, and safe deploys.
Stack (Default)
- Runtime: Node.js (LTS)
- Framework:
@slack/bolt - Tooling: Slack CLI (
slack) - Config: Slack manifest via CLI-generated project
Core CLI Commands
# Create new Slack app project
slack create my-slack-app
# Run locally (socket mode / dev env)
cd my-slack-app
slack run
# Deploy to Slack-hosted runtime / target env
slack deploy
Workflow (CLI-First)
- Identify integration points in existing functionality.
- Scaffold app with
slack create. - Model capabilities in the manifest (scopes, events, commands, interactivity).
- Implement handlers in Bolt (events, commands, actions, views/modals).
- Run locally with
slack runand validate in a dev workspace. - Deploy with
slack deploy.
Project Structure (Typical)
my-slack-app/
├── app/
│ ├── app.js # Bolt app bootstrap
│ ├── listeners/ # Events, commands, actions, views
│ ├── services/ # Integration layer to existing functionality
│ └── middleware/ # Auth, validation, shared guards
├── manifest.json # Slack app manifest (CLI-managed)
├── package.json
└── README.md
Design rule: keep Slack handlers thin; push real work into services/.
Common Use Cases
- Notifications: post messages from existing jobs or webhooks.
- Slash commands: wrap existing scripts or APIs behind
/commands. - Workflows: compose multi-step flows with Slack-native triggers.
- Modals: collect structured input, then call existing systems.
Implementation Notes
- Map each Slack surface to one listener module.
- Normalize inputs at the edge; pass clean DTOs inward.
- Acknowledge fast (
ack()), then do work. - Centralize Slack Web API calls behind a small service.
See references/bolt-patterns.md for concrete patterns.
Verification Steps
# 1) Install deps
npm install
# 2) Run locally
slack run
# 3) Lint/test if present
npm test
# 4) Deploy
slack deploy
Manual checks in Slack workspace:
- Trigger each command or event once.
- Validate permissions/scopes match what handlers need.
- Confirm errors surface as user-visible messages, not silent failures.