Provides direct access and search for Vercel AI SDK documentation and configuration.
Install
mkdir -p .claude/skills/ai-sdk-documentation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3167" && unzip -o skill.zip -d .claude/skills/ai-sdk-documentation && rm skill.zipInstalls to .claude/skills/ai-sdk-documentation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill should be used when working with Vercel AI SDK, AI Gateway, streamText, generateText, generateObject, streamObject, tool calling, or AI SDK providers. Also relevant for "ai-sdk", "@ai-sdk/*" packages, or questions about AI SDK patterns, configuration, and best practices.Key capabilities
- →List documentation pages by category
- →Fetch full markdown content for specific docs
- →Query AI Gateway models and capabilities
- →Check model pricing and context limits
How it works
The skill provides shell scripts to fetch real-time documentation from ai-sdk.dev and query the AI Gateway API for current model metadata.
Inputs & outputs
When to use ai-sdk-documentation
- →Looking up streaming UI component syntax
- →Finding provider configuration for OpenAI
- →Checking tool calling documentation
- →Reviewing React Server Component integration
About this skill
AI SDK Documentation Skill
This skill provides tools for accessing Vercel AI SDK documentation and AI Gateway model information. Use the bundled scripts to discover available documentation pages and fetch their full content.
Overview
The Vercel AI SDK documentation lives at ai-sdk.dev and covers:
- Core SDK (
aipackage) - generating text, streaming, tool calling, embeddings - UI integrations - React hooks, streaming UI components
- RSC - React Server Components integration
- Providers - Configuration for OpenAI, Anthropic, Google, and 30+ other providers
- AI Gateway - Vercel's multi-provider routing service
The documentation is large (600+ pages) and frequently updated. Rather than relying on stale knowledge, always use the scripts to fetch current documentation.
Scripts
All scripts are located in ${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/.
list-docs.sh
Discover available documentation pages.
Usage:
# List all pages grouped by category
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/list-docs.sh
# List pages in a specific category
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/list-docs.sh docs
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/list-docs.sh cookbook
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/list-docs.sh providers
Categories:
docs- Core documentation (concepts, guides, API reference)cookbook- Code examples by framework (Next.js, Node.js, etc.)providers- Provider-specific setup and configurationelements- UI component library documentationtools-registry- Third-party tool integrations
When to use: Run this first to discover what pages exist. Do not assume documentation structure.
fetch-doc.sh
Fetch the full markdown content of a specific documentation page.
Usage:
# Fetch a documentation page
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/fetch-doc.sh /docs/ai-sdk-core/generating-text
# Fetch a cookbook example
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/fetch-doc.sh /cookbook/next/generating-structured-data
# Fetch provider documentation
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/fetch-doc.sh /providers/ai-sdk-providers/openai
Input: A documentation path (e.g., /docs/ai-sdk-core/tools-and-tool-calling)
Output: Full markdown content of the page
When to use: After identifying relevant pages with list-docs.sh, fetch the ones that look most relevant to the task.
query-models.sh
Query the AI Gateway models API for available models and their capabilities.
Usage:
# List all models with their provider
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh list
# List all providers
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh providers
# List all capability tags
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh tags
# List models from a specific provider
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh --provider anthropic
# List models with a specific capability
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh --tag vision
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh --tag tool-use
# Get full details for a specific model
${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/query-models.sh --details openai/gpt-4o
Model details include: context window, max tokens, pricing, capability tags (vision, tool-use, reasoning, etc.)
When to use: When needing to know what models are available, compare model capabilities, or check pricing/context limits.
Workflow Guidelines
Finding Documentation
- Start with discovery: Run
list-docs.shto see available pages - Identify relevant pages: Look for pages whose paths match the topic
- Fetch content: Use
fetch-doc.shto get full content of relevant pages - Read multiple pages if needed: Topics often span multiple pages (e.g., a concept page + API reference page)
Important Notes
- Always fetch current docs: Do not rely on potentially outdated knowledge. Use the scripts to get current documentation.
- If a page doesn't appear in
list-docs.shoutput, it doesn't exist. - Some pages may not have .md versions: The script will indicate when this happens.
- Documentation is comprehensive: The AI SDK docs include guides, API references, examples, and troubleshooting. Check multiple sections for complete information.
AI Gateway
The AI Gateway is Vercel's unified API for accessing multiple AI providers. Key points:
- Single API endpoint, multiple providers
- Use
query-models.shto see all available models - Models are identified as
provider/model-name(e.g.,anthropic/claude-sonnet-4) - Provider-specific documentation is under
/providers/
When not to use it
- →Relying on stale or cached documentation
Limitations
- →Requires network access to fetch docs
- →Some pages may not have markdown versions
How it compares
It forces the use of live-fetched documentation rather than relying on potentially outdated internal knowledge.
Compared to similar skills
ai-sdk-documentation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ai-sdk-documentation (this skill) | 1 | 7mo | Review | Beginner |
| dapp | 0 | 1mo | Review | Intermediate |
| senior-fullstack | 35 | 7mo | Review | Intermediate |
| clerk-install-auth | 1 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by malob
View all by malob →You might also like
dapp
salazarsebas
Stellar dApp / frontend development. Covers the JavaScript stellar-sdk (browser + Node.js), Freighter wallet, Stellar Wallets Kit (multi-wallet), Wallet Standard, smart accounts with passkeys, transaction building / signing / submission, Soroban contract invocation from the client, simulation, and e
senior-fullstack
davila7
Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.
clerk-install-auth
jeremylongshore
Install and configure Clerk SDK/CLI authentication. Use when setting up a new Clerk integration, configuring API keys, or initializing Clerk in your project. Trigger with phrases like "install clerk", "setup clerk", "clerk auth", "configure clerk API key", "add clerk to project".
senior-qa
diegosouzapw
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup, and quality metrics. Use when designing test strategies, writing test cases, implementing
fullstack-developer
daithang59
|
nx
TerminalSkills
>-