Use when the user asks what RunAPI models are available, compares models, needs pricing, asks for required fields, searches by modality, or wants a recommendation. Triggers include "what models", "compare models", "cheapest", "pricing", "required params", "有哪些模型", "比较模型", and "价格".
Installs into .claude/skills of the current project.
Are you the author of Model Explorer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/runapi-ai-model-explorer)
---
name: RunAPI Model Explorer
description: >-
Use when the user asks what RunAPI models are available, compares models,
needs pricing, asks for required fields, searches by modality, or wants a
recommendation. Triggers include "what models", "compare models", "cheapest",
"pricing", "required params", "有哪些模型", "比较模型", and "价格".
version: 0.1.0
---
# RunAPI Model Explorer
Use RunAPI catalog and pricing tools for discovery.
## Workflow
1. Call `mcp__runapi__list_models` with modality, service, or action filters when possible.
2. For a specific model, call `mcp__runapi__get_model_info`; when service/action are known, include them to get the exact endpoint constraints.
3. For cost questions, call `mcp__runapi__check_pricing`.
4. Summarize as a compact table.
5. End with one recommended service/action/model triple when the user wants to generate.
## Rules
- Do not quote stale prices.
- Do not mention hidden infrastructure providers.
- Do not overwhelm the user with the whole catalog unless they ask.
- Keep model slugs exactly as returned by tools.