Agent skill · software engineering · vercel
add-adapter
Add a vendor-official or community adapter to the Chat SDK catalog and docs — adapters.json registry, chat/adapters catalog entry, the docs MDX page, meta.json, integration-test lists, and a changeset. Use when a developer wants to add, list, register, or submit a third-party (vendor-official or community) adapter to this repo, add an adapter to the catalog, or create or edit an adapter docs page under apps/docs/content/adapters/vendor-official or apps/docs/content/adapters/community.
Why this skill is useful
Adds specific integration patterns and documentation requirements for third-party adapters that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 2,269 stars on the source repository.
What this skill does
Add a catalog adapter (vendor-official or community) Use this to list a third-party adapter in the Chat SDK catalog and docs. It is not for building a first-party packages/adapter- package. Gather the source — never invent details Ask the user for: 1. Their adapter's GitHub repository URL. 2. Their docs or README. Read both. Everything you write into the catalog and docs must come directly from those sources or from the user. Do not assume or guess any information: packageName — read it from the repo's package.json, verbatim. Factory export (e.g. createFooAdapter) — read it from the package's exports/source. Do not guess it from the display name. type (platform or state), env vars, and the feature matrix — base these on what the code and README actually document. Install and usage snippets — take them from the README; do not write example code the adapter may not support. If the repo or README does not make something clear, stop and ask the user rather than filling it in. When in doubt, ask. Choose the slug (kebab-case) and confirm it is not already taken: ls apps/docs/content/adapters//. Pick the tier community — listed in the docs only. No chat/adapters catalog entry, no changeset. vendor-official — a maintained/blessed adapter. Everything community has, plus a chat/adapters catalog entry, a matching create-chat-sdk scaffold-spec entry, and a changeset. Frontmatter adds vendorOfficial: true and author. Files to change <tier> is vendor-official or community. 1. apps/docs/content/adapters/<tier>/<slug>.mdx — the docs page. Start from assets/adapter.mdx. The filename basename must equal the slug frontmatter field, and the page must render <FeatureSupport />. 2. apps/docs/content/adapters/<tier>/meta.json — add "<slug>" to the pages array. 3. apps/docs/adapters.json — add a registry entry: name, slug, type, community: true, description, packageName, author, readme (the GitHub URL). Add vendorOfficial: true for vendor-official. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/add-adapter