Slack Agent
Wire a coding agent to Slack so teammates can trigger workflows, read channels, and ship bot replies from the same repo you deploy on Vercel.
Overview
Slack Agent is an agent skill for the Build phase that guides implementation of Slack-connected agent workflows for solo builders using the Vercel Labs skill package.
Install
npx skills add https://github.com/vercel-labs/slack-agent-skill --skill slack-agentWhat is this skill?
- Apache 2.0 licensed Vercel Labs skill package for Slack-oriented agent workflows
- Typical pattern: channel context, threaded replies, and action handlers driven by your agent
- Fits solo builders shipping internal ops bots or customer-facing Slack assistants beside a web app
- Pairs with Node-based deploy targets (secrets via .env, excluded from VCS per package conventions)
- Catalog entry lacks published SKILL.md body—verify capabilities in-repo before trusting automation scope
Adoption & trust: 434 installs on skills.sh; 15 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your coding agent to act in Slack but lack a packaged, repeatable integration playbook in the repo.
Who is it for?
Indie builders adding a Slack bot or internal notify channel beside a Node app on Vercel who will read the full skill sources locally.
Skip if: Teams needing a finished MCP server with audited Slack scopes, or builders still choosing between Discord vs Slack with no integration started.
When should I use this skill?
When implementing or extending a Slack agent or bot in a project that uses this Vercel Labs skill repository.
What do I get? / Deliverables
You get a licensed skill scaffold and conventions so your agent can implement Slack handlers and env hygiene consistently instead of improvising API calls each session.
- Slack event or slash-command handlers
- Documented env template excluding secrets from git
- Agent-ready integration notes in the project
Recommended Skills
Journey fit
Slack agent skills sit in Build because they connect your product and agent runtime to a third-party workspace API during implementation, not during launch distribution or grow lifecycle tooling. Integrations is the canonical shelf for OAuth apps, Slack Bolt-style handlers, and webhook bridges that extend the builder’s stack beyond the core app repo.
How it compares
Use as a Vercel Labs skill package for Slack agent patterns, not as a hosted Slack marketplace app or generic productivity planner.
Common Questions / FAQ
Who is slack-agent for?
Solo and indie developers shipping agent-driven Slack integrations alongside web or API products, especially in the Vercel ecosystem.
When should I use slack-agent?
During Build when you are implementing OAuth, event subscriptions, or bot replies—after you have a Slack app created and tokens ready to configure locally.
Is slack-agent safe to install?
Review the Security Audits panel on this Prism page and inspect the skill repo yourself; Slack skills often need network and secret access, so never paste production tokens into untrusted sessions.
SKILL.md
READMESKILL.md - Slack Agent
# Dependencies node_modules/ # Environment .env .env.local .env.*.local # OS .DS_Store Thumbs.db # IDE .idea/ .vscode/ *.swp *.swo # Logs *.log npm-debug.log* Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense,