Add new or remove obsolete model IDs for existing AI SDK providers.
SkillScore70Maintained
Automatic
◆AI Engineer pack
Last verified 8/2/2026
What it changes
Passed 13 of 19 test cases with the skill, and 6 of 19 without it.
Without skill30%
With skill70%
Checks it passed that the model alone missed
examples/ai-functions/src/e2e/*.test.ts
content/providers/05-community-providers/
examples/ai-functions/src/generate-image/
and 9 more in the full report
10 fixed6 passed either way6 still failing1 broke
Pass-rate lift
+39 pp
Tokens
+77%
Agent turns
0%
Response time
-68%
Model gemini-3.6-flashMeasured 8/2/2026v216 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
When removing a deprecated model ID from a community provider integration in AI SDK, which documentation directory must be checked and updated?
What was checked, without and with the skill
Checked
Without skill
With skill
content/providers/05-community-providers/
Missed
Passed
case-17 · gemini-3.6-flash · 8/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md186 linessingle file
Update Provider Model IDs
This skill covers adding new model IDs and removing obsolete ones across the AI SDK codebase. Each workflow uses search to discover all locations that need changes.
You may be asked to add or remove a single model ID, or to process a list of multiple model ID changes from an issue. For each model ID, follow the appropriate workflow:
If a new model ID is being added, follow the <adding-new-model> workflow.
If an obsolete model ID is being removed, follow the <removing-obsolete-model> workflow.
Critical Rules
Exact matching: Model IDs are often substrings of others (e.g. grok-3 vs grok-3-mini). Always verify each search result is the exact model, not a substring match.
Respect sort order: When inserting into any list (type unions, table rows, arrays), observe the existing order and place the new entry accordingly.
File naming for examples: Use kebab-case with hyphens replacing dots (e.g. gpt-5.4-codex → gpt-5-4-codex.ts).
Sequential processing: When handling multiple models, complete the full workflow for one model before starting the next.
Affected providers: New model IDs always need to be added to the primary provider package and the AI Gateway. There may be additional affected packages (e.g. Bedrock, Vertex, OpenAI-compatible) if the model is available there or referenced in tests/docs.
Never make unrelated changes: Only update model IDs and related references. Don't modify any other code, text, or formatting in the files you edit.
Never modify CHANGELOG.md files of packages/codemod: Changelog files are historical records, codemods are migration scripts. Do not edit either when updating model IDs.
Workflow for Adding a New Model ID
Step 1: Identify Scope
Determine:
Provider name (e.g. anthropic, openai, google, xai)
Exact model ID string (e.g. claude-haiku-4-5-20260218, gemini-3.1-pro, gpt-5.4-codex)
Model type: chat, embedding, image, etc.
Whether this is a new version of an existing older model, or even the stable version of an existing preview or experimental model
Whether any provider packages other than the primary one and the AI Gateway need to be updated (e.g. Bedrock, Vertex, OpenAI-compatible)
If a similar model ID is listed in one of those other provider packages, the new model ID should likely be added there as well. Check the provider's documentation for clues on availability.
Step 2: Find Where Similar Models Are Referenced
Search for a similar existing model from the same provider (e.g. a lower version, or the preview version being replaced) across packages/, content/, and examples/. This reveals all locations that need updates.
# Search quoted occurrences to find all reference locations