Agent skill · software engineering · vercel
add-provider-package
Guide for adding first-party AI provider packages to the AI SDK. Use when creating a provider package under packages/ to integrate an external AI service.
Why this skill is useful
Provides a detailed guide and specific configurations for creating new AI provider packages, which includes niche patterns and structures not commonly found in public documentation.
What it needs
Requires tsup, typescript, vitest installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 26,057 stars on the source repository.
What this skill does
Add a Provider Package Add a complete first-party @ai-sdk/<provider> package that follows the current provider interfaces, repository conventions, security requirements, and release process. Read the Current Sources of Truth Before implementing anything, read: Add new provider for current package and release requirements Provider development notes for naming, schemas, and workflow serialization Provider architecture for the provider abstraction Secure URL handling when the provider fetches polling, image, audio, video, or other URLs Use PR #18595 as a recent end-to-end example, but choose the current provider package whose API shape and model types most closely resemble the new provider as the implementation reference. Third parties can publish provider packages outside this repository. A new first-party @ai-sdk/<provider> package requires prior discussion in an issue. Confirm that agreement exists before implementing the package. Discover the API Contract Before designing model classes, look for an official, versioned OpenAPI or Swagger specification in the provider's documentation or repositories. Prefer first-party specifications and record the source URL plus its version, publication date, or commit in the implementation notes or pull request. Use the specification and official documentation to identify: base URLs and authentication schemes supported endpoints, model types, and capabilities request parameters and response shapes streaming transports and event formats error response envelopes asynchronous polling and download URL flows Treat an OpenAPI specification as implementation evidence, not unquestioned truth. Specifications are often incomplete for server-sent events, streaming deltas, polymorphic content, tool calls, nullable fields, and errors. Do not add a generated client or generated production types by default. Implement minimal hand-written types and Zod schemas, then verify them against official documentation and captured API responses. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/add-provider-package