CtrlK
BlogDocsLog inGet started
Tessl Logo

add-provider-package

Guide for adding first-party AI provider packages to the AI SDK. Use when creating a provider package under packages/ to integrate an external AI service.

62

Quality

75%

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 ./skills/add-provider-package/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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-sequenced skill that leans on external sources of truth and validates via explicit commands and a checklist; its only weakness is that progressive disclosure relies entirely on external repo docs rather than bundled files.

DimensionReasoningScore

Conciseness

Dense and reference-heavy, assuming Claude's competence (no explaining what a provider or ADR is); a few explanatory sentences could be trimmed, so it is efficient but not maximally lean.

4 / 5

Actionability

Provides concrete executable commands (`pnpm update-references`, `pnpm --filter @ai-sdk/<provider> build`), exact values (version `2.0.0`), specific interfaces, and a copy-ready package scaffold, covering the common cases.

5 / 5

Workflow Clarity

A clear sequenced pipeline from reading sources through release, with an explicit 'Verify the Complete Change' validation block and a completion checklist that gates completion, matching the anchor for explicit validation steps plus a checklist.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to external repo docs (contributing/*.md, ADRs, sibling skills) with descriptive link text, but there are no bundle files and the body is a single long document rather than split-out detailed materials.

4 / 5

Total

18

/

20

Passed

Description

62%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 cleanly answers both what and when for a well-scoped niche, but its trigger terms are technical and narrow rather than natural user phrasing with synonyms.

Suggestions

Add natural-language trigger terms and synonyms users might say (e.g., 'AI provider', 'model integration', 'AI service adapter') alongside the repo-specific 'packages/' phrasing.

Broaden the 'Use when' clause with a couple of concrete situational triggers to lift completeness toward 5.

DimensionReasoningScore

Specificity

Names the domain ('first-party AI provider packages to the AI SDK') and one concrete action ('adding... packages'), matching the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Clearly states what ('Guide for adding first-party AI provider packages') and when ('Use when creating a provider package under packages/'), but the 'when' is narrow and repo-internal rather than rich with concrete trigger phrases, so it sits at 4 rather than 5.

4 / 5

Trigger Term Quality

Includes relevant phrases ('creating a provider package under packages/', 'integrate an external AI service') but lacks common synonyms or variations a user would naturally say, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche ('first-party AI provider packages to the AI SDK') is distinct with low overlap risk; it is not a 5 only because the trigger is repo-specific and could marginally overlap with generic package-creation skills.

4 / 5

Total

14

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 10 suspicious

Warning

Total

13

/

16

Passed

Repository
vercel/ai
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.