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".
98
Does it follow best practices?
Validation for skill structure
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 hits all the marks. It provides specific capabilities, comprehensive trigger terms covering both technical and natural language variations, explicit 'Use when' guidance with numbered scenarios, and clear distinctiveness through SDK-specific terminology. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and functions: 'generateText, streamText, ToolLoopAgent, embed, tools' and specific use cases like 'AI agents, chatbots, RAG systems, text generation features'. Also mentions specific React hooks 'useChat, useCompletion'. | 3 / 3 |
Completeness | Clearly answers both what ('Answer questions about the AI SDK and help build AI-powered features') and when with explicit numbered trigger scenarios and a dedicated 'Triggers on:' clause listing specific keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including both formal names ('AI SDK', 'Vercel AI SDK') and casual phrases ('add AI to my app', 'build an agent'), plus specific function names developers would search for ('generateText', 'streamText', 'useChat'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific SDK function names, provider mentions, and the explicit 'Vercel AI SDK' branding. Unlikely to conflict with generic coding skills due to the specific technical terminology and framework focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that efficiently guides Claude through AI SDK usage without explaining concepts Claude already knows. It provides concrete commands, clear workflows with validation checkpoints, and appropriate progressive disclosure through well-organized references. The explicit instruction to never trust internal knowledge and always verify against current sources is particularly valuable for a rapidly-evolving SDK.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence. No unnecessary explanations of basic concepts; every section provides actionable guidance without padding. | 3 / 3 |
Actionability | Provides concrete, executable commands (grep patterns, curl commands with jq), specific file paths to search, and clear instructions. The curl command for fetching model IDs is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear numbered sequences with explicit validation steps (typecheck after changes, check common-errors.md before searching source). The workflow for finding documentation has clear fallback paths and the troubleshooting flow is well-defined. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to common-errors.md, ai-gateway.md, and type-safe-agents.md. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
- 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.