slack-init

Provision a Slack app and persist credentials to project config.

11|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/runbear-io/aweek --skill slack-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-init
Source: https://github.com/runbear-io/aweek/tree/main/skills/slack-init
Command: npx skills add https://github.com/runbear-io/aweek --skill slack-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap a Slack app for the project and persist its credentials so the embedded SlackAdapter inside aweek serve can chat with Claude through Slack.

Core Features & Use Cases

  • Provision a real Slack app in the workspace and mint a Socket-Mode app-level token, then persist the credentials to the project config.
  • Support two flows: provision-and-persist and persist-only, with explicit destructive-action confirmation and gating.
  • Credentials are written to a project-local, gitignored path at .aweek/channels/slack/config.json and can be loaded by the runtime Slack adapter.

Quick Start

Run /aweek slack-init to provision a Slack app and persist its credentials to the project's config.

Frequently Asked Questions about slack-init

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

FAQPage Schema
How do I bootstrap a Slack app and persist its credentials for workspace automation?

To bootstrap a Slack app and persist credentials, run the initialization command to provision a real Slack app, mint a Socket-Mode app-level token, and merge the credentials into your project's local gitignored config file for runtime adapter access.

Where are Slack integration tokens stored to prevent accidental commits?

Slack integration tokens are stored in a project-local, gitignored path at .aweek/channels/slack/config.json. This strategy minimizes risk by keeping credentials out of version control while remaining loadable by the runtime Slack adapter.

Does Slack credential provisioning require confirmation for destructive operations?

Yes, Slack credential provisioning enforces a destructive-operation confirmation gate. The two-phase flow requires explicit confirmations before overwriting or merging credentials, ensuring you maintain control over workspace token management actions.

Can I persist existing Slack app credentials without provisioning a new app?

Yes, you can persist existing Slack app credentials without provisioning a new app using the persist-only flow. This supports scenarios where a real Slack app already exists, allowing you to merge tokens into the project config safely.

What is the best way to connect a Slack workspace with Claude using Socket Mode?

The best way to connect a Slack workspace with Claude using Socket Mode is provisioning an app-level token and persisting it to the project config. This enables the embedded SlackAdapter to handle real-time chat communication directly.

Why does my Slack adapter fail to load credentials in a project-level workflow?

Your Slack adapter may fail to load credentials if the config file is missing or malformed. The credential persistence process uses a tolerant on-disk and environment loading strategy to mitigate this, but the initial two-phase provisioning flow must complete successfully.