vercel-labs / slack-agent-skill

The README's actual flow supports two frameworks: Chat SDK (chat plus @chat-adapter/slack on Next.js, its recommended path for a new project) or Bolt for JavaScript (@slack/bolt on Nitro, for an existing Bolt project), auto-detected from package.json on later runs. The /slack-agent slash command, with new, configure, deploy, or test arguments, drives an interactive wizard through picking a framework, creating the Slack app manifest, configuring environment variables, testing locally over ngrok, and deploying to Vercel, and it holds the result to a stated quality bar: unit tests on exported functions, end-to-end tests on user-facing changes, Biome linting, and a clean TypeScript compile before calling a step done.

This suits a developer already deploying on Vercel who wants a Slack bot's manifest, OAuth wiring, and deployment scaffolded rather than typed by hand. A Slack app and its tokens have to exist before any of it runs, which is the "account key" dependency our database records for it, and the local workflow still expects pnpm and ngrok on the machine running it.

READ THE FULL ANALYSIS＋

The skill's own description and its README do not agree. The live SKILL.md frontmatter on file says to use it "when building Slack agents/bots with eve (Vercel's filesystem-first agent framework), @vercel/connect, or eve/channels/slack," and describes covering defineAgent/defineTool patterns and Vercel Connect credential brokering. The README we have never mentions eve, defineAgent, defineTool, or Vercel Connect anywhere; it documents only Chat SDK and Bolt for JavaScript, with Slack tokens configured by hand. We're reporting both descriptions rather than picking one, because we cannot tell from this material which one the installed skill actually behaves like.

It is a single skill, not a suite. Apache-2.0 licensed, and like several of Vercel Labs' skill repositories, one file doing one job — there's no sibling skill here for, say, Discord or Teams to compare it against.