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.

1.40x

Quality

78%

Does it follow best practices?

Impact

100%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/develop-ai-functions-example/SKILL.md

Quality

Content

68%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.

The body is a well-structured, actionable reference with concrete templates and run commands. Its main weakness is the absence of an explicit verify/run checkpoint in the example-development workflow, and minor placeholder gaps in the code templates.

Suggestions

Add an explicit verification step to the workflow, e.g. after writing an example: run it with `pnpm tsx src/...` and confirm the expected output before considering it complete.

Tighten the Best Practices section by removing common-sense items ('Keep examples focused', 'Use descriptive prompts') that assume little of Claude.

Either make at least one code template fully copy-paste-ready with a real provider import, or explicitly justify the placeholder pattern so the templates read as intentional patterns rather than gaps.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material (directory tables, naming patterns, code templates) without re-explaining known concepts, though the Best Practices section restates some common-sense guidance that could be trimmed.	4 / 5
Actionability	Provides executable run commands and concrete code templates covering common cases, but the templates use placeholder identifiers ('providerName', '@ai-sdk/provider-name', 'model-id') rather than fully copy-paste-ready imports, keeping it just below the 5 anchor.	4 / 5
Workflow Clarity	The 'When to Write Examples' scenarios and 'Running Examples' commands give a rough sequence, but there is no explicit verification checkpoint (e.g., run the example and confirm expected output) for the develop-then-validate workflow.	3 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections and is appropriately self-contained with no bundle files, though at ~218 lines some template/reference material could plausibly live in separate files.	4 / 5
	Total	15 / 20 Passed

Description

87%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.

The description is strong: third-person voice, explicit 'Use when' trigger clause, and concrete actions scoped to a specific directory. It clearly communicates both purpose and activation conditions with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('creating, running, or modifying examples', 'validate provider support, demonstrate features, or create test fixtures') but stays within a narrow examples-only domain, leaving minor coverage gaps relative to the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Develop examples for AI SDK functions') and 'when' ('Use when creating, running, or modifying examples...') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('creating, running, or modifying examples', 'validate provider support', 'demonstrate features', 'test fixtures') with good coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche tied to a concrete path ('examples/ai-functions/src') and AI SDK function examples, with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	18 / 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: 86892f3

Reviewed: about 3 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.