メニュー
Configure or rotate the Slack bot integration for Blazebot notifications — bot token, channel ID, bot name. Use for "set up slack bot", "rotate slack token", "change slack channel", "configure blazebot slack".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Configure or rotate the agent runtime (Claude or Codex) for the Blazebot workflow. Branches on runtime choice and emits a single paste-template for the chosen kind. Use for "set up claude", "set up codex", "rotate anthropic key", "switch agent to codex", "configure agent runtime".
First-time setup orchestrator for the Blazebot ai-workflow repo. Mirrors SETUP.md as an agent-driven flow — project linking, env vars across Jira / VCS / Agent / Slack / Neon, production deploy, post-deploy registrations (Jira webhook + Slack /ai-workflow slash command), and smoke checks. Use when starting fresh on this repo for the first time — "init project", "first-time setup", "bootstrap this repo", "onboard me", "set up env from scratch".
Set up or modify Jira configuration for the Blazebot workflow — credentials, project key, column statuses, workflow transitions, and webhook registration. State-aware: detects what's already in Vercel env and runs only the missing pieces. Use for "set up jira", "configure jira board", "rotate jira token", "register jira webhook", "fix jira transitions", "jira columns setup".
Configure the Neon Postgres database for Blazebot (run registry + post-PR gate store) via the Vercel Marketplace. Verifies DATABASE_URL is injected per environment, that environments do NOT share a branch, and that migrations apply. Use for "set up neon", "set up postgres", "configure database", "fix run registry", "env_marker error".
Configure or rotate the VCS provider (GitHub or GitLab) for the Blazebot workflow. Branches on provider choice and emits a single paste-template for that provider only. Use for "set up github", "set up gitlab", "rotate github token", "switch vcs provider", "configure vcs".
Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", "queue", "event", "push", "subscribe", or step-based orchestration.
| name | init-slack |
| description | Configure or rotate the Slack bot integration for Blazebot notifications — bot token, channel ID, bot name. Use for "set up slack bot", "rotate slack token", "change slack channel", "configure blazebot slack". |
Configures the Slack bot Blazebot uses to post status updates (run started, PR opened, run failed, etc.) to a single channel.
If you want full project setup (Jira + VCS + Agent + Slack + Neon + deploy), invoke
init-envinstead. This skill only handles Slack.
.vercel/project.json must exist. If missing:
ERROR: no Vercel project linked. Run `vercel link` first, or invoke `init-env`
for the full first-time setup.
Halt.
If a Blazebot Slack app already exists in the workspace, the user just needs the bot token and a channel ID — skip to step 2.
Otherwise, walk the user through references/bot-app-setup.md to create the Slack app with the right scopes.
Ask:
CHAT_SDK_SLACK_TOKEN — bot token, starts with xoxb-CHAT_SDK_CHANNEL_ID — channel ID like C0123456789 (not #channel-name)CHAT_SDK_BOT_NAME — defaults to blazebot; only ask if the user wants to overrideSLACK_SIGNING_SECRET — required. App settings → Basic Information → App Credentials → Signing Secret. Used to verify inbound /ai-workflow slash command requests. See references/slash-commands.md for the full slash-command setup.SLACK_ALLOWED_USER_IDS — optional. Comma-separated Slack user IDs (U…) allowed to run /ai-workflow. Defaults to empty, which lets anyone in the workspace run the slash command. Only ask if the user wants to restrict access.The user-friendly #channel-name doesn't work — Blazebot needs the C… ID. Two ways to find it:
/C0123456789. That's the ID.The bot must be invited to the channel: /invite @blazebot from inside the channel. Otherwise messages 403.
CHAT_SDK_SLACK_TOKEN=<value>
CHAT_SDK_CHANNEL_ID=<value>
SLACK_SIGNING_SECRET=<value>
If non-default bot name:
CHAT_SDK_BOT_NAME=<value>
If restricting slash commands to specific users:
SLACK_ALLOWED_USER_IDS=U0123,U4567
Tell the user to paste into Vercel → Project Settings → Environment Variables (all three environments), save, and reply when done.
After the env vars are saved and the project has been deployed at least once, the operator must register the slash command in Slack:
/ai-workflowhttps://<your-vercel-domain>/webhooks/slackFull walkthrough in references/slash-commands.md.
xoxp- user token. Blazebot needs a bot token (xoxb-). User tokens have different permission semantics and will silently fail in some adapter paths.#whatever) as the channel ID. The Slack API requires the ID. Save the user the silent-failure debug session.