Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →add-provider-package
Guide for adding new AI provider packages to the AI SDK.
Passed 17 of 20 test cases with the skill, and 6 of 20 without it.
and 12 more in the full report
13 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our schema validation files for `@ai-sdk/togetherai`, we imported Zod directly from `'zod'`. What import path should be used for schemas in new package implementations to support the repository's Zod version requirements?
| Checked | Without skill | With skill |
|---|---|---|
| Imports Zod schemas from zod/v4. | Missed | Passed |
The instructions your model reads when the skill loads.
Add a complete first-party @ai-sdk/<provider> package that follows the current provider interfaces, repository conventions, security requirements, and release process.
Before implementing anything, read:
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.
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:
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.
If no official specification exists, derive the contract from official documentation and real response fixtures, and note that limitation in the pull request.
Determine which AI SDK model interfaces the provider supports, such as LanguageModelV4, EmbeddingModelV4, ImageModelV4, SpeechModelV4, TranscriptionModelV4, RerankingModelV4, or Experimental_VideoModelV4.
Before introducing a dependency, public API pattern, or new abstraction, read contributing/decisions/README.md and relevant accepted ADRs. Prefer existing provider utilities and implementation patterns.
test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.