vercel / chat

chat-sdk is the one most people want: it scaffolds a bot with create-chat-sdk, and covers writing the bot logic once and deploying it across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, Linear, and WhatsApp — mentions, direct messages, subscribed threads, reactions, slash commands, JSX-based cards and modals, file uploads, and streaming an LLM's response into the chat as it generates. Each platform still needs its own adapter package installed separately (@chat-adapter/slack, @chat-adapter/teams, and so on), plus a state adapter such as @chat-adapter/state-redis to persist thread state.

add-adapter is not for that job. It is a contributor-facing skill for adding a new adapter to the Chat SDK's own catalog: the adapters.json registry, the docs page, meta.json, the integration-test lists, and a changeset. It is useful only if you are building and submitting a platform adapter upstream to this repository itself, not if you are just building a bot with adapters that already exist.

READ THE FULL ANALYSIS＋

Both skills assume a local project already in some shape. Our dependency label puts both at local_tool rather than ready, meaning neither is a pure reference document; each expects a real Chat SDK project — or, for add-adapter, the repository's own monorepo — to act on rather than working from a blank slate. The package is official, MIT-licensed, and points agents at its own llms.txt/llms-full.txt pages for documentation beyond the skill.