develop-ai-functions-example

Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures.

0.57x

Quality

83%

Does it follow best practices?

Impact

52%

0.57x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 highly actionable, well-structured body with complete templates and concrete commands. The main gaps are minor generic advice in Best Practices, no explicit run-to-verify step in the example-creation workflow, and no use of progressive disclosure despite substantial inline template content.

Suggestions

Trim the generic Best Practices items ('Use descriptive prompts', 'Add comments for complex logic') that Claude already knows, keeping only project-specific guidance like the run() wrapper's error handling.

Move the four code templates to a references/ file (e.g., references/templates.md) and keep one short basic template inline, making SKILL.md a lean overview.

Add an explicit workflow step to verify a new example by running it ('pnpm tsx src/<function>/<provider>/<example>.ts') and iterating on API errors before considering it done.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and project-specific code templates, but the 'Best Practices' section includes generic advice Claude already knows ('Use descriptive prompts', 'Add comments for complex logic') that could be trimmed.	4 / 5
Actionability	Four complete, copy-paste-ready templates (basic, streaming, tool calling, structured output), exact run commands ('pnpm tsx src/generate-text/openai/basic.ts'), and a concrete naming-pattern table cover the common cases; placeholder provider/model names are justified flexibility for a multi-provider repo.	5 / 5
Workflow Clarity	Category table → naming convention → template → run commands form a coherent implied sequence, and running the example serves as a checkpoint, but there is no explicit validation or error-recovery step after creating an example.	4 / 5
Progressive Disclosure	Well-organized sections with clear headers and tables, but no bundle files exist and all ~230 lines are inline; the four code templates could live in a references/ file to keep SKILL.md a leaner overview.	4 / 5
	Total	17 / 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 explicit and specific what/when coverage anchored to a concrete directory. Trigger terms are good but could add function-name keywords and common synonyms to be fully comprehensive.

Suggestions

Add natural trigger keywords users would say, such as specific function names ('generateText', 'streamText', 'generateObject') or synonyms like 'demo' or 'repro script'.

Sharpen distinctiveness by stating what this skill does not cover (e.g., fixture capture, which is delegated to capture-api-response-test-fixture).

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('creating, running, or modifying examples') and purposes ('validate provider support, demonstrate features, or create test fixtures'), but all actions revolve around a single verb family rather than comprehensively enumerating capabilities.	4 / 5
Completeness	Explicitly answers both what ('Develop examples for AI SDK functions') and when ('Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('examples', 'AI SDK', 'provider support', 'test fixtures') plus a concrete directory path, but misses common variations such as specific function names (generateText, streamText) or synonyms like 'demo'/'repro'.	4 / 5
Distinctiveness Conflict Risk	Anchoring to the specific directory 'examples/ai-functions/src' makes it mostly distinct from generic AI SDK development skills, though 'create test fixtures' and broad 'AI SDK functions' wording carries minor overlap risk with test-fixture or SDK-development skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: vercel/ai
Path: skills/develop-ai-functions-example/SKILL.md
Commit: 137a8fe

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.