Skill

or-find-audio-models

Use when the user wants to find OpenRouter models that accept audio input. Triggers on phrases like "OpenRouter audio models", "models that accept audio on OR", "speech input models on OpenRouter", "OpenRouter models for transcription", "audio-capable LLMs on OpenRouter".

npx claudepluginhub danielrosehill/claude-open-router-model-research-plugin

Popularity

Stars

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/open-router-model-research:or-find-audio-models

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Filter the OpenRouter catalog to models that accept audio input, then rank or summarize based on user criteria.

SKILL.md

35 lines · ~505 tokens

Similar Skills

cache-components

139.5k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

docx

135.8k

Creates, reads, edits, and analyzes .docx files using docx-js for new documents, pandoc for text extraction, Python scripts for XML unpacking/validation/changes, and LibreOffice for conversions.

20 files

document-skills

Stats

Stars2

MaintenanceFair

Last CommitApr 16, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

or-find-audio-models

Find OpenRouter Audio-Input Models

Filter the OpenRouter catalog to models that accept audio input, then rank or summarize based on user criteria.

When to use

The user wants to discover models on OpenRouter that can process spoken/audio input — for transcription, voice understanding, audio QA, multimodal voice agents.

Workflow

Fetch the catalog:

curl -s https://openrouter.ai/api/v1/models -H "Accept: application/json"

Filter data[] where architecture.input_modalities includes "audio".

The audio-input model set on OpenRouter is small (often a handful of Gemini and GPT-4o variants). If the result set is empty, tell the user clearly and suggest alternatives:

Use a dedicated STT API (Whisper, Deepgram, Gemini transcription) and pass text to an LLM
Use a multimodal model that accepts text + image (a screenshot of a waveform or transcript) — usually wrong fit, mention only if relevant

For each match, surface: supported audio formats (if listed in description), pricing (often charged per second or per token after transcription), and context length.

If the user has a preference (cheapest, longest audio supported), rank accordingly.

Notes

Audio pricing on OR varies — some models bill per audio token, others per audio second. Read the model description carefully and quote the relevant figure.

Audio capability is a fast-moving area; the catalog is the source of truth — do not rely on memory for which models currently support audio.

Output

Markdown table or short list (since the set is small): ID, Context, Audio handling notes, Pricing notes, Caveats. If the set is empty, recommend a fallback workflow.

Find OpenRouter Audio-Input Models

Filter the OpenRouter catalog to models that accept audio input, then rank or summarize based on user criteria.

When to use

The user wants to discover models on OpenRouter that can process spoken/audio input — for transcription, voice understanding, audio QA, multimodal voice agents.

Workflow

Fetch the catalog:

curl -s https://openrouter.ai/api/v1/models -H "Accept: application/json"

Filter data[] where architecture.input_modalities includes "audio".
The audio-input model set on OpenRouter is small (often a handful of Gemini and GPT-4o variants). If the result set is empty, tell the user clearly and suggest alternatives:
- Use a dedicated STT API (Whisper, Deepgram, Gemini transcription) and pass text to an LLM
- Use a multimodal model that accepts text + image (a screenshot of a waveform or transcript) — usually wrong fit, mention only if relevant
For each match, surface: supported audio formats (if listed in description), pricing (often charged per second or per token after transcription), and context length.
If the user has a preference (cheapest, longest audio supported), rank accordingly.

Notes

Audio pricing on OR varies — some models bill per audio token, others per audio second. Read the model description carefully and quote the relevant figure.
Audio capability is a fast-moving area; the catalog is the source of truth — do not rely on memory for which models currently support audio.

Output

Markdown table or short list (since the set is small): ID, Context, Audio handling notes, Pricing notes, Caveats. If the set is empty, recommend a fallback workflow.