Slack Agent Skill: Build a Slack agent on Vercel with eve

Who it's for

This skill is for people who want to build and deploy a Slack agent on Vercel. It works with eve (Vercel's persistent-agent framework) and Vercel Connect (which hosts Slack credentials). eve docs live at https://eve.dev/docs Connect notes live at https://vercel.com/kb/guide/vercel-connect The repository stresses that you do not need to handle the bot token or signing secret yourself.

A better fit is this workflow: you plan to use /slack-agent to start a new project or configure an existing one, first test tools, instructions, and conversations locally in the eve dev text UI, and leave Slack events until after deploy. It is not for people who still want to keep the Slack signing secret themselves, or who expect to click through every event in the Slack UI without deploying.

Do not apply this install command in an environment without skill support. Also do not treat an ngrok tunnel as a required step: the docs say Slack events are forwarded through Connect to the deployed project; ngrok is not needed.

First try in 3 minutes

The official install command is: npx skills add vercel-labs/slack-agent-skill. The repository URL is https://github.com/vercel-labs/slack-agent-skill Follow only this page. Do not write undocumented installers.

Preconditions: the current assistant supports skills, and you have a disposable empty directory or an existing eve project. The install location is the assistant's skills directory. After install, confirm you can see /slack-agent new, /slack-agent configure, /slack-agent deploy, and /slack-agent test.

Low-risk first task: do not deploy first. If you are starting from scratch, run /slack-agent new first (it scaffolds with eve), but confirm the directory is for practice before any files are written. If you already have a project, use /slack-agent configure (it auto-detects eve). The success signal is that scaffolding or configuration is done, and you have not yet run /slack-agent deploy.

Local verification uses the eve dev TUI: test tools, instructions, and conversations. Events in the Slack UI wait until after deploy, then reach the project through Vercel Connect. Slack-side environment-variable notes mention only SLACK_CONNECTOR; do not invent other secret placeholders. /slack-agent test is for setting up tests; wait until local conversations work before considering it.

Use cases

Case 1: Scaffold from scratch. /slack-agent new uses eve to scaffold a new project. It fits when you have no repository yet and just want to see the agent structure locally first. The docs do not list the generated files, so the farthest you can verify is that the command succeeded and an eve project appeared. Confirm the directory before writing. The reference page is https://github.com/vercel-labs/slack-agent-skill

Case 2: Configure an existing project and split local versus production checks. /slack-agent configure auto-detects eve. Locally, use eve dev to test tools, instructions, and conversations; Slack events arrive through Connect after deploy, and ngrok is not needed. /slack-agent deploy deploys to production and should come after the local TUI has passed. Connect hosts OAuth, token rotation, and webhook verification; the only named Slack environment variable is SLACK_CONNECTOR. The docs do not describe how to fill that variable, and they do not describe production rollback; do not deploy before Connect setup is complete.

Usage limits

Install limit: the official docs only list npx skills add vercel-labs/slack-agent-skill. Command limit: you can verify /slack-agent new, configure, deploy, and test. Credential limit: you do not need to handle the bot token or signing secret yourself; the only named Slack environment variable is SLACK_CONNECTOR. Test limit: the local TUI tests tools, instructions, and conversations; Slack events are verified through Connect after deploy, and ngrok is not needed. Framework limit: eve and Vercel Connect are the documented dependencies, with docs at https://eve.dev/docs and https://vercel.com/kb/guide/vercel-connect The docs do not guarantee that other hosting platforms can be used as-is.