ai-sdk
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".
90
92%
Does it follow best practices?
Impact
76%
2.92xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope around the AI SDK ecosystem with specific functions, use cases, and trigger terms. It follows the recommended pattern with explicit 'Use when' guidance and a 'Triggers on' clause. The description is comprehensive yet focused, making it easy for Claude to distinguish this skill from others.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: answering questions about AI SDK, building AI-powered features, and enumerates specific functions (generateText, streamText, ToolLoopAgent, embed), specific use cases (agents, chatbots, RAG systems, text generation), and specific React hooks (useChat, useCompletion). | 3 / 3 |
Completeness | Clearly answers both 'what' (answer questions about AI SDK, help build AI-powered features) and 'when' with an explicit numbered list of trigger scenarios plus a dedicated 'Triggers on' clause with specific keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms developers would use: 'AI SDK', 'Vercel AI SDK', specific function names like 'generateText' and 'streamText', natural phrases like 'add AI to my app' and 'build an agent', plus technical terms like 'tool calling', 'structured output', and 'useChat'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around the AI SDK / Vercel AI SDK specifically. The specific function names (generateText, streamText, useChat) and framework-specific terminology make it very unlikely to conflict with generic coding or AI skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides clear, actionable guidance for working with the AI SDK. Its greatest strengths are the concrete commands, clear workflow sequences with validation steps (typecheck), and good progressive disclosure through well-referenced supporting files. The main weakness is slight verbosity in the 'Critical' section, though the emphasis is understandable given the risk of using outdated APIs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some verbosity. The 'Critical: Do Not Trust Internal Knowledge' section is somewhat heavy-handed, and the numbered list in that section could be tightened. The curl command for fetching model IDs is appropriately detailed since it's non-obvious, but phrases like 'Everything you know about the AI SDK is outdated or wrong' are unnecessarily dramatic. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout: specific grep patterns for searching docs, a curl command with jq for fetching model IDs, exact file paths to search (node_modules/ai/docs/, node_modules/ai/src/), and a specific URL pattern for the search API. The guidance is specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The Prerequisites → Search docs → Verify against source → Typecheck flow is well-defined. The 'When Typecheck Fails' section provides a clear error recovery workflow: check common-errors.md first, then search source, then search online. The agent building section has a clear detect-framework → search-docs → implement sequence. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to four specific reference files (common-errors.md, ai-gateway.md, type-safe-agents.md, devtools.md). References are signaled inline where relevant and collected in a summary References section at the bottom. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.