CtrlK
BlogDocsLog inGet started
Tessl Logo

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

2.92x
Quality

92%

Does it follow best practices?

Impact

76%

2.92x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

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.

DimensionReasoningScore

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 actionable, concrete guidance for working with the AI SDK. Its strongest aspects are the clear workflow sequences with validation steps (typecheck, doc verification) and excellent progressive disclosure through well-organized references. The main weakness is some verbosity in the Critical section that could be tightened without losing clarity.

Suggestions

Tighten the 'Critical: Do Not Trust Internal Knowledge' preamble — the dramatic framing ('Everything you know is outdated or wrong') wastes tokens; a simple 'Always verify APIs against docs/source before using' suffices.

Consider moving the lengthy curl command for fetching model IDs to a reference file or shortening it, as it adds visual noise to the main skill body.

DimensionReasoningScore

Conciseness

Generally efficient but has some verbosity, particularly the emphatic 'Everything you know about the AI SDK is outdated or wrong' framing and the lengthy curl command inline. The numbered list in the Critical section could be tighter, and some instructions like 'Do not install other packages at this stage' over-explain.

2 / 3

Actionability

Provides concrete, executable commands throughout: grep patterns for searching docs, curl command for fetching model IDs, specific file paths to check, and clear installation commands. The guidance is specific and copy-paste ready.

3 / 3

Workflow Clarity

Clear sequenced workflows with validation checkpoints: Prerequisites → search docs → verify against source → typecheck after changes. The 'When Typecheck Fails' section provides an explicit error recovery flow (check common-errors.md first → search source → search online). The numbered steps in the Critical section establish a clear decision sequence.

3 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear overview in SKILL.md and well-signaled one-level-deep references to common-errors.md, ai-gateway.md, type-safe-agents.md, and devtools.md. The References section at the bottom provides clean navigation with brief descriptions of each linked file.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
vercel/ai
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.