CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vercel-ai-sdk-expert

Expert in the Vercel AI SDK. Covers Core API (generateText, streamText), UI hooks (useChat, useCompletion), tool calling, and streaming UI components with React and Next.js.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/vercel-ai-sdk-expert/SKILL.md

The canonical home for this skill is vercel-ai-sdk-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 solid, example-driven reference with executable code for the core SDK workflows, a clear server-to-client narrative, and practical troubleshooting. Its main weaknesses are padding (role-play preamble, known-concept explanations, styling markup) and a declared generative-UI use case with no accompanying example.

Suggestions

Remove the 'You are a production-grade Vercel AI SDK expert...' preamble and the 'Tools allow the LLM to interact with your code...' concept explanation — Claude already knows these; keep only SDK-specific guidance.

Trim the Tailwind class markup from the useChat example (or reduce it to the minimal messages loop and form) so tokens go to SDK mechanics rather than styling.

Either add a minimal streaming UI (streamUI / useChat tool result rendering) example or drop 'building AI-powered generative UIs' from the When-to-Use list so the declared scope matches the demonstrated content; consider moving the full Chat component to a references/ file.

DimensionReasoningScore

Conciseness

The code examples are tight and comments are mostly load-bearing, but there are several instances of unnecessary content: the role-play preamble ('You are a production-grade Vercel AI SDK expert... You understand streaming...'), an explanation of a concept Claude already knows ('Tools allow the LLM to interact with your code, fetching external data...'), and substantial Tailwind styling markup in the useChat example that teaches nothing about the SDK. This exceeds the 'minor instances' of anchor 4, fitting 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Concrete, copy-paste-ready TypeScript covering generateText, a streamText API route, generateObject with a Zod schema, a working useChat component, and a tool() definition with execute. Not 5: the 'When to Use' section declares 'building AI-powered generative UIs (streaming React components)' and useCompletion, but no example of either is provided — a minor gap against the 'covers the common cases' anchor.

4 / 5

Workflow Clarity

A coherent server-to-client progression: the streamText route is explicitly linked to the client ('Points to the streamText route created above'), tool calling builds from server definition to multi-step UI handling, and the Troubleshooting section gives concrete problem-to-solution error recovery (timeout fix, maxSteps fix). Not 5: there are no explicit validation checkpoints or ordered steps, keeping it at 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Well-organized hierarchical sections (Core API, UI hooks, Tool Calling, Best Practices, Troubleshooting) with no dangling or nested references and easy navigation — matching 'good structure; most content appropriately placed'. Not 5: at ~213 lines everything is inline with no reference files, and content like the fully-styled Chat component and tool-calling UI fragment could be split into a references/ file to keep SKILL.md a leaner overview.

4 / 5

Total

15

/

20

Passed

Description

70%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 specific, well-scoped description that names concrete SDK APIs and is highly distinct, but it lacks any 'Use when...' trigger guidance, capping completeness, and misses natural synonyms plus the structured-data capability. Adding an explicit trigger clause would lift it substantially.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when adding AI chat or streaming LLM features to a React/Next.js app, implementing tool calling, or generating structured JSON output with the Vercel AI SDK (ai / @ai-sdk/react packages).'

Include the structured-data capability (generateObject) and natural synonyms such as 'function calling', 'chatbot', and 'AI chat app' to broaden trigger coverage.

Drop the 'Expert in...' role claim in favor of a verb-led, third-person action statement (e.g. 'Builds AI chat, streaming, and generative UI features with the Vercel AI SDK...').

DimensionReasoningScore

Specificity

The description lists several concrete capabilities with specific API names ("generateText, streamText", "useChat, useCompletion", "tool calling, streaming UI components"), matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because structured data generation (generateObject) is omitted and the leading 'Expert in...' is a role claim rather than a concrete action.

4 / 5

Completeness

The 'what' is clearly stated (Core API, UI hooks, tool calling, streaming UI), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4: the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Terms like "Vercel AI SDK", "useChat", "streamText", "tool calling", and "React and Next.js" are natural phrases developers would say. Not 5: common synonyms and variations are missing — 'function calling', 'chatbot', 'AI chat app', 'structured output', and the package names 'ai' / '@ai-sdk/react'.

4 / 5

Distinctiveness Conflict Risk

"Vercel AI SDK" plus SDK-exclusive API names (generateText, useChat) form a clear niche with distinct triggers and minimal conflict risk against generic React/Next.js skills. Fits the anchor 5 example's pattern of a specific domain with unambiguous trigger terms.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/vercel-ai-sdk-expert/SKILL.md

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.