Agent-Skills.md

Agent Skills: AI SDK version and documentation routing

Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".

UncategorizedID: laguagu/claude-code-nextjs-skills/ai-sdk

Repository

laguagu/claude-code-nextjs-skills
laguaguLicense: MIT
217

Install this agent skill to your local

pnpm dlx add-skill https://github.com/laguagu/claude-code-nextjs-skills/tree/HEAD/skills/ai-sdk

Skill Files

Browse the full folder contents for ai-sdk.

Download Skill

Loading file tree…

skills/ai-sdk/SKILL.md

Skill Metadata

Name
ai-sdk
Description
'Answer questions about the AI SDK and help build AI-powered features. Use when developers ask about Vercel AI SDK, generateText, streamText, ToolLoopAgent, useChat, providers, tools, structured output, embeddings, streaming, or adding AI to an app. First identify the installed major version and route version-specific work: use ai-sdk-7 for AI SDK 7 features/migrations such as WorkflowAgent, HarnessAgent, reasoning, runtime/tools context, toolApproval, telemetry, realtime, or v6-to-v7 upgrades; use ai-sdk-6 for v6 code.'

AI 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-tags confirms). ai@7 pairs with @ai-sdk/react@4, ai@6 with @ai-sdk/react@3. Provider majors differ per package (for v7, Amazon Bedrock and xAI are 5.x, OpenAI-compatible 3.x), so install each provider's latest for v7 and its ai-v6 dist-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, and 6.0.32 still has no src/. 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.

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

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.