// 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.
| name | AI SDK Documentation |
| description | 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. |
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.
The Vercel AI SDK documentation lives at ai-sdk.dev and covers:
ai package) - generating text, streaming, tool calling, embeddingsThe documentation is large (600+ pages) and frequently updated. Rather than relying on stale knowledge, always use the scripts to fetch current documentation.
All scripts are located in ${CLAUDE_PLUGIN_ROOT}/skills/ai-sdk-docs/scripts/.
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 integrationsWhen to use: Run this first to discover what pages exist. Do not assume documentation structure.
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 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.
list-docs.sh to see available pagesfetch-doc.sh to get full content of relevant pageslist-docs.sh output, it doesn't exist.The AI Gateway is Vercel's unified API for accessing multiple AI providers. Key points:
query-models.sh to see all available modelsprovider/model-name (e.g., anthropic/claude-sonnet-4)/providers/This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
This skill should be used when performing web research beyond a simple single search -- looking into topics, comparing options, investigating questions, finding recommendations, or any task where effective use of Exa, Firecrawl, and Reddit tools matters. Triggers on "research", "look into", "investigate", "compare", "find out about", "search for", "find information", "what do people think about", "what are the best", "look up", or multi-source search tasks. Also invocable explicitly by deep-research team members via the Skill tool.
This skill should be used when the user asks to "audit claude permissions", "audit permissions", "review local claude settings", "promote permissions to global", "clean up claude settings", "find permission patterns", or wants to identify project-local Claude Code permissions that should be added to global configuration.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
This skill should be used when the user asks to "add a cask to homebrew", "create a homebrew cask", "add an app to homebrew", "new cask for", "homebrew cask for", "package an app for homebrew", "submit to homebrew-cask", "make a cask", "contribute a cask", or wants to package a macOS application for Homebrew.
Workaround for Claude Code filtering BMP PUA Unicode (U+E000-U+F8FF). Supplementary PUA Nerd Font icons like (U+F0000+, e.g. nf-md-github, nf-md-kubernetes, nf-md-battery) can be written directly. BMP PUA icons (Powerline, Font Awesome, Devicons) require placeholder syntax like {{ U+E0A0 }} or {{ nf-fa-star }} (without spaces), which hooks auto-convert. Invoke when reading or writing Starship configs, tmux themes, shell prompts, or statuslines.