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.
79
70%
Does it follow best practices?
Impact
100%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/develop-ai-functions-example/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a reasonably well-constructed description with a clear 'Use when...' clause that explicitly defines both what the skill does and when to use it. Its main weakness is that the specific actions could be more concrete (e.g., what kinds of examples, what specific operations), and the trigger terms lean toward project-specific jargon rather than natural language a user might employ.
Suggestions
Add more concrete action verbs describing what 'develop examples' entails, e.g., 'write function call examples, configure provider settings, set up streaming responses'
Include more natural trigger terms users might say, such as 'AI function example', 'SDK demo', 'function calling sample', or 'provider integration test'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI SDK functions) and some actions (creating, running, modifying examples), but doesn't list multiple concrete specific actions beyond that. 'Validate provider support, demonstrate features, create test fixtures' adds some specificity but remains somewhat general. | 2 / 3 |
Completeness | Clearly 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). Has an explicit 'Use when...' clause with clear triggers. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'examples', 'ai-functions', 'provider support', 'test fixtures', but these are somewhat technical/project-specific. Missing more natural user terms a developer might say, and the path 'examples/ai-functions/src' is very specific to one project structure. | 2 / 3 |
Distinctiveness Conflict Risk | The specific path 'examples/ai-functions/src' and the focused domain of 'AI SDK functions' make this clearly distinguishable from other skills. Unlikely to conflict with general coding or testing skills due to the narrow scope. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill with excellent actionability through complete, executable templates and clear naming conventions. Its main weaknesses are a lack of explicit workflow steps with validation checkpoints for creating new examples, and some verbosity in areas like best practices that state things Claude already knows. The content would benefit from a tighter structure with an explicit creation workflow.
Suggestions
Add an explicit step-by-step workflow for creating a new example: create file with correct naming → use appropriate template → run with pnpm tsx → verify output → commit.
Trim the 'Best Practices' section — items like 'handle errors gracefully' and 'add comments for complex logic' are things Claude already knows and waste tokens.
Consider consolidating the four similar templates into one annotated template with inline comments showing variations for streaming, tools, and structured output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-organized but includes some redundancy. The four templates (basic, streaming, tool calling, structured output) are somewhat verbose given their similarity, and the best practices section states things Claude already knows (e.g., 'handle errors gracefully', 'add comments for complex logic'). The tables are efficient, but overall it could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready TypeScript templates for multiple use cases, concrete run commands, specific file naming conventions, and clear import paths. The templates are complete and realistic with actual library imports and function calls. | 3 / 3 |
Workflow Clarity | The 'When to Write Examples' section provides guidance on when to create examples, and the templates show how to structure them, but there's no explicit workflow for creating a new example (e.g., create file → write code → test run → verify output). There are no validation checkpoints or feedback loops for verifying that a newly created example works correctly. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's somewhat monolithic — all content is inline in a single file. The reference to 'capture-api-response-test-fixture' skill is a good cross-reference, but the utility helpers and reusable tools sections could potentially be separate files. Without bundle files, the skill handles organization reasonably but could benefit from splitting detailed templates into a separate reference. | 2 / 3 |
Total | 9 / 12 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.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.