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

87%

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 well-structured, highly actionable skill body with executable templates and concrete commands. The main weaknesses are minor verbosity in the best-practices section and the absence of an explicit validate-the-example-runs checkpoint in the workflow.

Suggestions

Tighten or remove the generic Best Practices items that restate obvious guidance (e.g. "Keep examples focused", "Use descriptive prompts") to improve token efficiency.

Add an explicit workflow checkpoint after writing an example, such as running it with `pnpm tsx` and confirming it executes without errors before considering it done.

Consider moving the four code templates into a referenced file under references/ so the SKILL.md body stays a lean overview, improving progressive disclosure for this longer skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with compact tables and ready-to-use code templates, but the generic "Best Practices" list ("Keep examples focused", "Use descriptive prompts") and the brief explanation of the run() wrapper add mild over-explanation that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, executable TypeScript templates for the common cases (basic, streaming, tool calling, structured output) plus concrete run commands ("pnpm tsx src/generate-text/openai/basic.ts") and precise file-naming patterns.	5 / 5
Workflow Clarity	The naming convention, templates, run commands, and "When to Write Examples" scenarios imply a clear creation flow, but there is no explicit sequenced procedure with validation checkpoints for verifying an example runs correctly before finishing.	4 / 5
Progressive Disclosure	Well organized into clearly headed sections (categories, naming, structure, running, helpers, tools, best practices) with no nested references, though all content is inline with no bundle files to delegate the bulkier template catalog to.	4 / 5
	Total	17 / 20 Passed

Description

92%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, specific description that clearly states both capability and trigger conditions with concrete actions and a narrow, low-conflict niche. The only minor gap is slightly thinner synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating, running, or modifying examples") plus concrete purposes ("validate provider support, demonstrate features, or create test fixtures"), giving comprehensive coverage of the skill's capabilities.	5 / 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	Good natural keyword coverage ("examples", "AI SDK functions", "provider support", "test fixtures") with an explicit "Use when..." trigger, but a few common synonyms or phrasings a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	The highly specific path "examples/ai-functions/src" and narrow "AI SDK functions" niche give it a clear, distinct trigger surface with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: c3c189c

Reviewed: ~4 hours 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.