update-provider-models_skill

This skill updates provider model IDs by adding new IDs or removing obsolete ones across the AI SDK, ensuring consistent provider support.
  • TypeScript
  • Official

22.3k

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

1 month ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill vercel/ai --skill update-provider-models

  • SKILL.md9.4 KB

Overview

This skill updates model ID lists for AI SDK providers by adding new IDs or removing obsolete ones across the repository. It enforces exact matching, correct sort order, and minimal, targeted edits so only model-related references change. Use it to process single model changes or batched changes from an issue. The skill guides you through type, docs, examples, and test updates and running the affected package tests.

How this skill works

For each model change the skill runs a scoped search to find exact quoted occurrences in packages/, content/, and examples/. It then follows one of two workflows: adding a new model ID (update type unions, const arrays, docs, examples, tests) or removing an obsolete model ID (remove from types, update docs/examples/tests). At every step it enforces exact-match verification, respects existing sort order, and avoids unrelated edits.

When to use it

  • Adding a new provider model ID to the primary provider package and AI Gateway
  • Removing an obsolete model ID from type unions, docs, examples, and tests
  • Processing a list of multiple model ID changes from an issue
  • Updating examples or tests that should reference a successor model
  • Ensuring type definitions and capability tables reflect new or removed IDs

Best practices

  • Always search for quoted occurrences to avoid substring false positives
  • Process multiple models sequentially: complete one model's workflow before the next
  • Respect existing sort order when inserting or removing entries in unions/arrays
  • Only change model IDs and directly related references; never modify unrelated code or formatting
  • Run package-specific tests (provider + gateway and any affected packages) after edits

Example use cases

  • Add a new chat model ID for the Anthropic package and update the gateway types and docs
  • Remove an obsolete OpenAI-compatible model from type unions, docs, and example lists
  • Update example files to replace a preview model with its stable successor
  • Process an issue that lists several new and deprecated model IDs across providers
  • Add model IDs to Bedrock or Vertex packages when the provider announces cross-platform availability

FAQ

Search for the model ID with single or double quotes (e.g. 'model-id' or "model-id") and manually verify each result to ensure it is an exact match.

Which files must always be updated when adding a new model ID?

At minimum, update the primary provider package type unions/consts and the AI Gateway types. Also check docs, examples, and any other provider packages (Bedrock, Vertex, OpenAI-compatible) if applicable.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational