CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-sdk

Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.

76

6.33x
Quality

74%

Does it follow best practices?

Impact

76%

6.33x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ai-sdk/SKILL.md

The canonical home for this skill is ai-sdk in vercel/ai

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

A well-structured, lean overview that excels at progressive disclosure by pointing to real bundled references one level deep. Its main weakness is actionability: it tells Claude where to look and how to verify, but shows little executable SDK code itself.

Suggestions

Add 1-2 minimal copy-paste code examples for the most common tasks (e.g. a streamText chat route and a ToolLoopAgent definition) so Claude has a runnable starting point before searching the source.

Promote the typecheck step into an explicit gated checkpoint ("After changes: run typecheck; only proceed when it passes") in a short numbered workflow rather than burying it as item 8 in a list.

Consolidate the repeated "search node_modules/ai/src and docs" guidance that appears in Critical, Finding Documentation, and When Typecheck Fails into one place to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly lean overview that defers detail to bundled docs and source rather than re-explaining concepts Claude already knows, with only minor over-explanation (the long curl model-listing command and some repetition of the "search the source" directive across sections).

4 / 5

Actionability

Provides concrete, executable search/verify commands ("pnpm add ai", grep paths, the models curl) but defers the actual SDK usage patterns to the source/docs rather than showing executable code for the named tasks, leaving key details incomplete.

3 / 5

Workflow Clarity

A logical progression (install → search versioned docs → handle typecheck failures → build/consume agents) with one embedded feedback loop in "When Typecheck Fails", but the typecheck validation is a bullet among nine rather than an explicit gated checkpoint, so checkpoints remain mostly implicit.

3 / 5

Progressive Disclosure

Clean overview body with four well-signaled one-level-deep references (common-errors.md, ai-gateway.md, type-safe-agents.md, devtools.md) all confirmed to exist, plus a dedicated organized References section — easy to navigate.

5 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 description with an explicit Use-when clause and a broad, concrete list of AI SDK capability triggers. It is well-scoped to the Vercel AI SDK, with only minor overlap risk and a few missing synonyms.

DimensionReasoningScore

Specificity

Lists many specific capability domains ("chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation") but these are feature areas rather than concrete verbs, and "expert guidance" + "working with any LLM provider" are slightly generic, leaving minor gaps versus the comprehensive-actions anchor.

4 / 5

Completeness

Explicitly answers both what ("Vercel AI SDK expert guidance" over the listed features) and when ("Use when building AI-powered features — ...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural-keyword coverage ("chat interfaces", "tool calling", "streaming", "embeddings", "agents", "image generation") a developer would actually say, but a few common synonyms (e.g. RAG, chatbot, prompts) are missing and there are no file-extension triggers.

4 / 5

Distinctiveness Conflict Risk

Scoped to the named "Vercel AI SDK" with distinct triggers, but the closing "or working with any LLM provider" breadth creates minor overlap risk with the closely related ai-gateway skill.

4 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

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