agentleFS
BingZi-233BingZi-233/check-cx/.agents/skills/ai-sdk/SKILL.md

ai-sdk

Skill636 starsChanged 3 months agoMITView on GitHub

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".

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never write AI SDK code from memory: Always verify every API, option, and pattern against the documentation and source code for the version …

    line 17
  2. Very specific:

    Ensure ai is installed. If node_modules/ai/ does not exist, install only the ai package using the project's package manager (e.g.

    line 23
  3. Very specific:

    Read and grep the bundled docs at node_modules/ai/docs/ and the source at node_modules/ai/src/.

    line 24
  4. Very specific:

    If something isn't in the bundled docs, search https://ai-sdk.dev/docs.

    line 26
  5. Distinctive:

    If you cannot find support for an answer in the docs or source, say so explicitly — do not guess.

    line 27
  6. Very specific:

    Never use model IDs from memory — models are released and retired frequently.

    line 43
  7. Distinctive:

    When multiple versions of a model exist, prefer the one with the highest version number.

    line 53
  8. Very specific:

    Look up the current agent, tool, and type-safety APIs in the bundled docs (node_modules/ai/docs/, especially the agents section) or at …

    line 59
  9. Distinctive:

    If the installed version is a major version (or more) behind the latest, tell the user they are on an old release, and recommend upgrading …

    line 74
  10. Distinctive:

    Run the project's type checker.

    line 78

“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

What the AI SDK Is

The AI SDK by Vercel (the ai package on npm) is a TypeScript toolkit for building AI applications. It provides a unified API across model providers for text generation, structured output, tool calling, agents, embeddings, and framework UI integrations.

Critical: Do Not Trust Your Own Memory

Whatever you remember about the AI SDK is likely outdated. The SDK changes frequently across versions - APIs are renamed, removed, and added. Your training data almost certainly contains obsolete APIs, deprecated patterns, and model IDs that no longer exist. UI hooks like useChat are among the most frequently changed APIs, so be especially careful with client code.

Never write AI SDK code from memory. Always verify every API, option, and pattern against the documentation and source code for the version that is actually installed in the project.

Use the Bundled, Version-Matched Docs

The ai package ships its full documentation and source code inside node_modules. These always match the installed version, so trust them over anything you remember.

  1. Ensure ai is installed. If node_modules/ai/ does not exist, install only the ai package using the project's package manager (e.g. pnpm add ai). Install provider packages (e.g. @ai-sdk/openai) and framework packages (e.g. @ai-sdk/react) later, when the task requires them.
  2. Read and grep the bundled docs at node_modules/ai/docs/ and the source at node_modules/ai/src/.
  3. Provider and framework packages bundle their own docs at node_modules/@ai-sdk/<name>/docs/.
  4. If something isn't in the bundled docs, search https://ai-sdk.dev/docs. You can append .md to any docs page URL to get its markdown, and search via https://ai-sdk.dev/api/search-docs?q=your_query.
  5. If you cannot find support for an answer in the docs or source, say so explicitly — do not guess.

AI Gateway: The Fastest Way to Start

The Vercel AI Gateway is the fastest way to get started with the AI SDK. It provides access to models from OpenAI, Anthropic, Google, and other providers through a single API, without installing provider packages or managing multiple API keys.

To set it up:

  1. Authenticate with OIDC (for Vercel deployments) or get an AI Gateway API key.
  2. Provide it to your app via the AI_GATEWAY_API_KEY environment variable.
  3. Reference models with provider/model strings.

For exact setup, authentication, and usage, read the bundled guide and the AI Gateway docs.

Choosing a Model

Never use model IDs from memory — models are released and retired frequently. Fetch the current list before writing code that references a model. Do not truncate the list (e.g. with head) so you can find the newest models:

# All available models
curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '.data[].id'

# Filter by provider (e.g. anthropic, openai, google)
curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("anthropic/")) | .id] | reverse | .[]'

When multiple versions of a model exist, prefer the one with the highest version number.

Building and Consuming Agents

Use the SDK's built-in agent abstraction (such as ToolLoopAgent) rather than hand-rolling tool-calling loops. For end-to-end type safety, infer the UI message type from your agent definition when consuming it on the client (e.g. with useChat). Consuming an agent is framework-specific: check package.json to detect the stack, then follow the matching quickstart.

Look up the current agent, tool, and type-safety APIs in the bundled docs (node_modules/ai/docs/, especially the agents section) or at https://ai-sdk.dev/docs.

DevTools

AI SDK DevTools captures your AI SDK calls - requests, responses, tool calls, token usage, and multi-step runs - so you can inspect exactly what your agents do. Use it while developing to debug generations. It is a separate package and is intended for local development only.

For setup instructions, read the bundled DevTools documentation.

Keep the SDK Current

Outdated installs are the most common source of errors. Compare the installed version against the latest:

  • Installed: the version field in node_modules/ai/package.json.
  • Latest: run npm view ai version.

If the installed version is a major version (or more) behind the latest, tell the user they are on an old release, and recommend upgrading before continuing. Migration guides are at https://ai-sdk.dev/docs/migration-guides.

After Making Changes

Run the project's type checker. Be minimal — only set options that differ from the defaults, checking docs or source for the defaults rather than over-specifying. Most type errors come from remembered, now-changed APIs; re-check the current docs and source when they occur.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.