update-provider-models

Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 lean, highly actionable, and well-sequenced with concrete commands and validation steps for both add and remove workflows. The main gap is minor: an explicit fix-and-re-run feedback loop on test failure and possible extraction of the long file-path/location lists into a reference.

Suggestions

In each workflow's Step 7, add an explicit feedback loop: 'If tests fail, fix the failing case and re-run until green' to lift workflow_clarity from 4 to 5.

Consider moving the multi-provider file-location lists (Step 3 of the add workflow) into a references/ file and linking to it, keeping the core SKILL.md shorter.

Add a short 'Verify exact-match (not substring)' checkpoint callout right after the grep steps in both workflows to reinforce the critical rule inline.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence throughout (no explanation of what a model ID, provider, or type union is) and uses concrete grep/pnpm commands plus tight code blocks, with the second workflow reusing 'same as Workflow A Step 7' instead of repeating. Every section earns its tokens, matching the lean-and-efficient anchor; it is not the 4 anchor because there are no meaningful over-explanation instances to trim.	5 / 5
Actionability	Guidance is fully executable: quoted-grep search commands, exact file paths (e.g. 'packages/<provider>/src/*-options.ts'), copy-paste TypeScript type-union and const-array additions, and specific 'pnpm --filter @ai-sdk/<provider> test' commands covering the common add/remove cases. This matches the fully-executable, copy-paste-ready anchor.	5 / 5
Workflow Clarity	Both workflows are clearly sequenced in 7 numbered steps with explicit validation checkpoints ('Step 7: Run Tests') and a Critical Rules checklist covering exact-match, sort-order, and no-unrelated-changes for the batch operation. It sits below 5 because the error-recovery feedback loop is only implied ('run tests') rather than spelled out as 'if tests fail, fix and re-run'.	4 / 5
Progressive Disclosure	Content is well organized with distinct labeled sections (Critical Rules, <adding-new-model>, <removing-obsolete-model>) and no nested external references, and no bundle files exist to validate. It is above 3 (clear sectioning, nothing buried) but below 5 because at ~185 lines the example-path enumeration and per-provider location lists could plausibly be split into a reference file.	4 / 5
	Total	18 / 20 Passed

Description

82%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: it explicitly covers both the what and when with concrete trigger phrases and occupies a distinct, low-conflict niche. The only soft spot is specificity, which lists two actions without finer per-model-type detail.

Dimension	Reasoning	Score
Specificity	Quotes 'Add new or remove obsolete model IDs for existing AI SDK providers' name the domain plus two concrete actions (add/remove) but offer no per-type detail, matching the anchor for naming domain and 1-2 concrete actions without being comprehensive.	3 / 5
Completeness	It clearly states what it does ('Add new or remove obsolete model IDs') and explicitly when to use it ('Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue') with concrete trigger phrases, matching the anchor for explicitly answering both what and when.	5 / 5
Trigger Term Quality	Explicit 'Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs"' plus a 'Use when...' clause gives strong natural keyword coverage with synonyms, fitting good-but-not-comprehensive coverage. It is below 5 because common phrasings like 'add a model to X' or 'deprecate a model' are not all enumerated.	4 / 5
Distinctiveness Conflict Risk	The narrow niche of AI SDK provider model-ID maintenance with dedicated trigger phrases ('add model', 'new model ID', 'obsolete model') makes it clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche anchor.	5 / 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/update-provider-models/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.