/output-dev-model-selection
Pick the right LLM model for an Output SDK prompt file. Use when writing a new .prompt file, reviewing a model choice, or upgrading a stale model. Walks through priority (reasoning/balance/speed/cost), provider selection, and a live lookup against the Vercel AI Gateway model
$ npx -y skills add growthxai/output --skill output-dev-model-selection --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/output-dev-model-selection
Context preview
The summary Claude sees to decide when to auto-load this skill.
Pick the right LLM model for an Output SDK prompt file. Use when writing a new .prompt file, reviewing a model choice, or upgrading a stale model. Walks through priority (reasoning/balance/speed/cost), provider selection, and a live lookup against the Vercel AI Gateway model
SKILL.md
output-dev-model-selection.SKILL.mdname: output-dev-model-selection
description: Pick the right LLM model for an Output SDK prompt file. Use when writing a new .prompt file, reviewing a model choice, or upgrading a stale model. Walks through priority (reasoning/balance/speed/cost), provider selection, and a live lookup against the Vercel AI Gateway model index.
allowed-tools: [Bash(curl *), Bash(jq *), Read, Glob]
Picking a Model for an Output SDK Prompt
This skill is the single source of truth for model selection across Output SDK skills and agents. Other skills link here instead of pinning specific model IDs, because model rosters drift faster than docs.
Live model snapshot
We run this at skill-load time to fetch the 10 most recently released models per provider from the Vercel AI Gateway:
output=$(curl -fsS https://ai-gateway.vercel.sh/v1/models 2>/dev/null | jq '
.data as $models
| {
anthropic: ([ $models[] | select(.id | startswith("anthropic/")) ] | sort_by(.released) | reverse | .[0:10]),
openai: ([ $models[] | select(.id | startswith("openai/")) ] | sort_by(.released) | reverse | .[0:10]),
google: ([ $models[] | select(.id | startswith("google/")) ] | sort_by(.released) | reverse | .[0:10])
}
' 2>/dev/null)
if [ -n "$output" ]; then printf '%s\n' "$output"; else echo "(snapshot unavailable)"; fiSnapshot Data
output=$(curl -fsS https://ai-gateway.vercel.sh/v1/models 2>/dev/null | jq '
.data as $models
| {
anthropic: ([ $models[] | select(.id | startswith("anthropic/")) ] | sort_by(.released) | reverse | .[0:10]),
openai: ([ $models[] | select(.id | startswith("openai/")) ] | sort_by(.released) | reverse | .[0:10]),
google: ([ $models[] | select(.id | startswith("google/")) ] | sort_by(.released) | reverse | .[0:10])
}
' 2>/dev/null)
if [ -n "$output" ]; then printf '%s\n' "$output"; else echo "(snapshot unavailable)"; fiSnapshot Fallback
If the block above is empty, the script didn't execute automatically — likely because part of it (`jq`, `curl`, or network access) is missing. Query and filter the snapshot yourself before continuing.
Snapshot shape
{
"anthropic": [ <model>, ..., <up to 10> ],
"openai": [ <model>, ..., <up to 10> ],
"google": [ <model>, ..., <up to 10> ]
}Each `<model>` is the unmodified gateway payload. Useful fields per model:
| Field | What to use it for | |---|---| | `id` | The provider-prefixed ID (eg `anthropic/claude-sonnet-4.6`) — translate to prompt-file form (Step 5) | | `released` | Unix timestamp of release. Snapshot is already sorted newest-first per provider. | | `name` | Human-readable name | | `description` | One-paragraph capability summary — read this when comparing similarly-named tiers | | `context_window` | Max input tokens. Matters when prompts include large context (codebases, long docs) | | `max_tokens` | Max single-response output tokens | | `tags` | Capability flags. `reasoning`, `tool-use`, `vision`, `file-input`, `web-search`, `image-generation`, `explicit-caching`, `implicit-caching` | | `pricing.input` / `pricing.output` | Per-token cost (USD). Multiply by 1,000,000 for "per 1M tokens" | | `pricing.input_cache_read` | Cached-input price — usually 10× cheaper than `input` | | `type` | `language` for chat models; image models surface as `image-generation` and aren't valid for `.prompt` files |
Decision flow
Step 1 — Determine task priority
Pick the first row that fits. If unclear, default to **reasoning**.
| Priority | Use when | |---|---| | **reasoning** *(default)* | Complex multi-step logic, structured output extraction, judges with edge cases, anything where wrong > slow | | **balance** | Most generative work — summarization, classification, content drafting, conversation | | **speed** | Short interactive responses, low-latency UI loops, simple transforms | | **cost** | Bulk batch processing where token spend dominates and quality floor is forgiving |
Step 2 — Determine provider
Scan existing `*.prompt` files in the workflow (and its siblings under `src/workflows/`) and tally what `provider:` they declare.
- **If the workflow (or sibling workflows) already use one provider, match it.** Mixing providers means the runtime needs API keys for each — operational footgun.
- **If no existing prompts, default to `anthropic`.**
- Only switch provider when the user explicitly asks, or when a feature you need (eg Gemini's `useSearchGrounding`, OpenAI's `maxToolCalls`) is provider-specific.
Step 3 — Map provider name to snapshot key
Output SDK `provider:` values don't always line up with the snapshot keys, since Vercel groups Gemini under `google/`:
| Output SDK provider | Snapshot key | |---|---| | `anthropic` | `anthropic` | | `openai` | `openai` | | `vertex` (Gemini models) | `google` | | `vertex` (Claude models) | `anthropic` (then re-add the `@vertex` suffix manually) | | `bedrock` | `anthropic` (then translate to bedrock namespace manually) |
Step 4 — Pick a model from the provider's list
The list is already sorted newest-first. Walk it top-down and pick the first model whose `id` matches the tier for your priority.
**Skip these by default:**
- `type != "language"` (eg `gpt-image-2`, `gemini-embedding-2`) — not valid for `.prompt` files.
- IDs containing `preview`, `alpha`, or `beta`. **Use stable / GA models only**, even if a newer preview/alpha/beta exists. Only pick a non-stable model when the user explicitly asks for it ("use the preview", "I want the new beta", etc.).
| Priority | Anthropic — match `id` containing | OpenAI — match `id` | Google — match `id` | |---|---|---|---| | reasoning | `claude-opus-` (and `tags` includes `reasoning`) | ends with `-pro` | contains `-pro` | | balance | `claude-sonnet-` | base `gpt-N.M` (no `-mini`/`-nano`/`-pro` suffix) | contains `-pro` | | speed | `claude-haiku-` | ends with `-mini` | ends with `-flash` (not `-flash-lite`) | | cost | `claud
Read more
name: output-dev-model-selection description: Pick the right LLM model for an Output SDK prompt file. Use when writing a new .prompt file, reviewing a model choice, or upgrading a stale model. Walks through priority (reasoning/balance/speed/cost), provider selection, and a live lookup against the Vercel AI Gateway model index. allowed-tools: [Bash(curl *), Bash(jq *), Read, Glob]
Picking a Model for an Output SDK Prompt
This skill is the single source of truth for model selection across Output SDK skills and agents. Other skills link here instead of pinning specific model IDs, because model rosters drift faster than docs.
Live model snapshot
We run this at skill-load time to fetch the 10 most recently released models per provider from the Vercel AI Gateway:
output=$(curl -fsS https://ai-gateway.vercel.sh/v1/models 2>/dev/null | jq '
.data as $models
| {
anthropic: ([ $models[] | select(.id | startswith("anthropic/")) ] | sort_by(.released) | reverse | .[0:10]),
openai: ([ $models[] | select(.id | startswith("openai/")) ] | sort_by(.released) | reverse | .[0:10]),
google: ([ $models[] | select(.id | startswith("google/")) ] | sort_by(.released) | reverse | .[0:10])
}
' 2>/dev/null)
if [ -n "$output" ]; then printf '%s\n' "$output"; else echo "(snapshot unavailable)"; fiSnapshot Data
output=$(curl -fsS https://ai-gateway.vercel.sh/v1/models 2>/dev/null | jq '
.data as $models
| {
anthropic: ([ $models[] | select(.id | startswith("anthropic/")) ] | sort_by(.released) | reverse | .[0:10]),
openai: ([ $models[] | select(.id | startswith("openai/")) ] | sort_by(.released) | reverse | .[0:10]),
google: ([ $models[] | select(.id | startswith("google/")) ] | sort_by(.released) | reverse | .[0:10])
}
' 2>/dev/null)
if [ -n "$output" ]; then printf '%s\n' "$output"; else echo "(snapshot unavailable)"; fiSnapshot Fallback
If the block above is empty, the script didn't execute automatically — likely because part of it (`jq`, `curl`, or network access) is missing. Query and filter the snapshot yourself before continuing.
Snapshot shape
{
"anthropic": [ <model>, ..., <up to 10> ],
"openai": [ <model>, ..., <up to 10> ],
"google": [ <model>, ..., <up to 10> ]
}Each `<model>` is the unmodified gateway payload. Useful fields per model:
| Field | What to use it for | |---|---| | `id` | The provider-prefixed ID (eg `anthropic/claude-sonnet-4.6`) — translate to prompt-file form (Step 5) | | `released` | Unix timestamp of release. Snapshot is already sorted newest-first per provider. | | `name` | Human-readable name | | `description` | One-paragraph capability summary — read this when comparing similarly-named tiers | | `context_window` | Max input tokens. Matters when prompts include large context (codebases, long docs) | | `max_tokens` | Max single-response output tokens | | `tags` | Capability flags. `reasoning`, `tool-use`, `vision`, `file-input`, `web-search`, `image-generation`, `explicit-caching`, `implicit-caching` | | `pricing.input` / `pricing.output` | Per-token cost (USD). Multiply by 1,000,000 for "per 1M tokens" | | `pricing.input_cache_read` | Cached-input price — usually 10× cheaper than `input` | | `type` | `language` for chat models; image models surface as `image-generation` and aren't valid for `.prompt` files |
Decision flow
Step 1 — Determine task priority
Pick the first row that fits. If unclear, default to **reasoning**.
| Priority | Use when | |---|---| | **reasoning** *(default)* | Complex multi-step logic, structured output extraction, judges with edge cases, anything where wrong > slow | | **balance** | Most generative work — summarization, classification, content drafting, conversation | | **speed** | Short interactive responses, low-latency UI loops, simple transforms | | **cost** | Bulk batch processing where token spend dominates and quality floor is forgiving |
Step 2 — Determine provider
Scan existing `*.prompt` files in the workflow (and its siblings under `src/workflows/`) and tally what `provider:` they declare.
- **If the workflow (or sibling workflows) already use one provider, match it.** Mixing providers means the runtime needs API keys for each — operational footgun.
- **If no existing prompts, default to `anthropic`.**
- Only switch provider when the user explicitly asks, or when a feature you need (eg Gemini's `useSearchGrounding`, OpenAI's `maxToolCalls`) is provider-specific.
Step 3 — Map provider name to snapshot key
Output SDK `provider:` values don't always line up with the snapshot keys, since Vercel groups Gemini under `google/`:
| Output SDK provider | Snapshot key | |---|---| | `anthropic` | `anthropic` | | `openai` | `openai` | | `vertex` (Gemini models) | `google` | | `vertex` (Claude models) | `anthropic` (then re-add the `@vertex` suffix manually) | | `bedrock` | `anthropic` (then translate to bedrock namespace manually) |
Step 4 — Pick a model from the provider's list
The list is already sorted newest-first. Walk it top-down and pick the first model whose `id` matches the tier for your priority.
**Skip these by default:**
- `type != "language"` (eg `gpt-image-2`, `gemini-embedding-2`) — not valid for `.prompt` files.
- IDs containing `preview`, `alpha`, or `beta`. **Use stable / GA models only**, even if a newer preview/alpha/beta exists. Only pick a non-stable model when the user explicitly asks for it ("use the preview", "I want the new beta", etc.).
| Priority | Anthropic — match `id` containing | OpenAI — match `id` | Google — match `id` | |---|---|---|---| | reasoning | `claude-opus-` (and `tags` includes `reasoning`) | ends with `-pro` | contains `-pro` | | balance | `claude-sonnet-` | base `gpt-N.M` (no `-mini`/`-nano`/`-pro` suffix) | contains `-pro` | | speed | `claude-haiku-` | ends with `-mini` | ends with `-flash` (not `-flash-lite`) | | cost | `claud
The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code — describe what you want, Claude builds it, with all the best practices already in place. One framework.
Repo: growthxai/output
Other skills on output.
- /llm-output-schema-constraints
Zod schema constraints that Anthropic rejects or silently ignores when sent as structured-output tool definitions via Output.object(). Use when writing or reviewing Zod schemas passed to Output.object(), or debugging structured-output validation errors.
Open skill - /prompt-file-provider-options
Guide to the providerOptions structure in .prompt files — decision tree for where an option goes, common mistakes, per-provider quick reference, and Anthropic prompt caching. Use when writing or reviewing .prompt file frontmatter (provider, model, providerOptions,
Open skill - /validate
Run lint, build, and tests to validate changes are correct
Open skill - /output-build-workflow
Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build.
Open skill - /output-credentials-edit
View and edit encrypted credentials in an Output.ai project. Use when adding secrets, updating API keys, verifying credential values, or retrieving a specific credential.
Open skill - /output-credentials-env-vars
Wire encrypted credentials to environment variables using the credential: convention. Use when setting up LLM provider keys (ANTHROPIC_API_KEY, OPENAI_API_KEY) or any env var that should come from encrypted credentials.
Open skill

