About ai-sdk
A documentation-routing skill for developers working with the Vercel AI SDK. It helps identify installed package versions and locate matching APIs and references before implementation, reducing version mismatches.
Key features
- 01Resolve installed SDK versions
- 02Route work to major-specific guidance
- 03Search local docs and package types
- 04Find version-matched API references
- 05Check provider model configuration
Use cases
- 01Prepare an AI SDK upgrade or migration
- 02Verify API calls against an installed major
- 03Locate documentation in an offline workspace
MCP support
The skill notes that @ai-sdk/mcp has no bundled documentation and directs users to guides in ai/docs and API declarations in package types.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/ai-sdkin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.mdreferences/common-errors.mddevtools.mdexamples.mdtype-safe-agents.mdDetails
From the project READMEAI SDK version and documentation routing
Identify ai and the provider/React package versions in the relevant workspace's
manifest, lockfile or installed package. Keep the installed major unless an
upgrade is requested.
- AI SDK 7 implementation or migration: use
ai-sdk-7. - AI SDK 6 maintenance: use
ai-sdk-6. - Unknown, mixed or older versions: resolve them before applying either API set.
- New apps: start on the current major (7 when written;
npm view ai dist-tagsconfirms).ai@7pairs with@ai-sdk/react@4,ai@6with@ai-sdk/react@3. Provider majors differ per package, so install each provider'slatestfor v7 and itsai-v6dist-tag for v6 (npm view <pkg> dist-tags).
Find the API that matches the app
Search the resolved package's docs/, types and src/ (when shipped) first;
they work without network. ai bundles docs from 6.0.32 and in 7.x;
6.0.0-6.0.31 have no docs. The docs tree
mirrors the website: ai-sdk.dev/docs/<section>/<page>
is ai/docs/<nn>-<section>/<nn>-<page>.mdx, so an ai-sdk.dev/docs link in
these skills can be read from the installed major's copy. Provider packages
ship docs/<nn>-<provider>.mdx. @ai-sdk/react, @ai-sdk/workflow,
@ai-sdk/harness, @ai-sdk/otel and @ai-sdk/mcp ship no docs; their guides
are in ai/docs and their API in dist/*.d.ts. Monorepo hoisting and
Yarn PnP may change the paths; do not install or upgrade a dependency solely
to obtain docs.
When local documentation is unavailable, use the matching repository tag
(vercel/ai, tag ai@<version>, content/docs/) or docs version. The
documentation search
and Markdown page variants help locate the relevant feature. Repository main
and the default website can target a newer major than the app. With neither
local docs nor network, say which API facts remain unverified.
Append &tag=v6 (v5, v6 or v7) to scope search
results to a major.
Choose model IDs from the app's provider configuration or current provider catalog. The Gateway catalog can aid discovery; its IDs and capability availability do not imply that another provider accepts them. Choose capability, latency and cost for the task.
Targeted references
- Common errors: obsolete names and protocol mismatches.
- Typed agents: UI inference and server/client boundaries.
- DevTools: local debugging.
- Examples: provider-specific official code.
Use defaults when they fit. Typecheck changed integrations and exercise their streaming/tool path; a supported symbol can still be used with the wrong callback scope, result semantics or provider.