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".

93

2.81x
Quality

Does it follow best practices?

Impact

93%

2.81x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body that defers detail to four genuine reference files and includes validation plus error-recovery loops. Its main weakness is redundancy: the local-search-then-web-search procedure is repeated across three sections.

Suggestions

Consolidate the 'search node_modules/ai/docs and src, then ai-sdk.dev' procedure into a single Finding Documentation section and have the Critical and When Typecheck Fails sections reference it, removing the triple repetition.

Trim the restated rationale in 'Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs...' to a single directive sentence, since the second sentence restates the first.

The 'Consuming Agents (Framework-Specific)' steps ('Search documentation for the framework's quickstart guide', 'Follow the framework-specific patterns') are directional rather than executable — point to a concrete starting command or the specific docs path to search.

DimensionReasoningScore

Conciseness

The body is mostly lean and directive, but the 'search node_modules/ai/docs and src, then ai-sdk.dev' pattern is restated across three sections (Critical: Do Not Trust Internal Knowledge, Finding Documentation, and When Typecheck Fails), so it could be tightened — matching the 'mostly efficient but could be tightened' anchor rather than the every-token-earns-its-place anchor at 3.

2 / 3

Actionability

Provides copy-paste-ready, executable commands throughout — `pnpm add ai`, `grep "query" node_modules/ai/docs/`, a full `curl ... | jq` model-ID command, and `InferAgentUIMessage<typeof agent>` — satisfying the fully-executable anchor rather than the pseudocode/abstract anchor at 2.

3 / 3

Workflow Clarity

The 9-step list includes an explicit validation checkpoint (step 8: 'Run typecheck after changes') and a dedicated 'When Typecheck Fails' error-recovery feedback loop (grep common-errors → search source → search ai-sdk.dev), meeting the clear-sequence-with-validation-and-feedback anchor rather than the missing-checkpoint anchor at 2.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to four real, substantial one-level-deep reference files (common-errors.md 445 lines, type-safe-agents.md 204, ai-gateway.md 66, devtools.md 52) via clearly signaled links and a References section, with no deep reference chains — matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, third-person description that states concrete capabilities, provides explicit numbered 'Use when' triggers, and adds a natural-language 'Triggers on' keyword list. It is dense but not padded with fluff, and clearly distinguishes the AI SDK niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and targets — 'Answer questions about the AI SDK and help build AI-powered features', building 'AI agents, chatbots, RAG systems, or text generation features' — matching the 'lists multiple specific concrete actions' anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly answers both what ('Answer questions... help build AI-powered features') and when via a numbered 'Use when developers: (1)...(4)' clause plus a 'Triggers on:' list, satisfying the explicit-trigger anchor at 3 rather than the implied-when anchor at 2.

3 / 3

Trigger Term Quality

A dedicated 'Triggers on:' list includes natural user phrases like 'add AI to my app', 'build an agent', 'tool calling', and 'useChat', giving good coverage of terms users would actually say rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche ('AI SDK', 'Vercel AI SDK') with SDK-specific function names (generateText, streamText, ToolLoopAgent, useChat) as triggers, making it unlikely to fire for unrelated skills; not the generic 'works with files' anchor at 2.

3 / 3

Total

12

/

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.

Validation16 / 16 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.