/choosing-an-api
Use when the user or agent needs to pick a public API for a task (weather, images, finance, etc.). Queries public-apis-live for reachable, deduped options.
$ npx -y skills add manavarya09/public-apis-live --skill choosing-an-api --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
/choosing-an-api
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user or agent needs to pick a public API for a task (weather, images, finance, etc.). Queries public-apis-live for reachable, deduped options.
SKILL.md
choosing-an-api.SKILL.mdname: choosing-an-api description: Use when the user or agent needs to pick a public API for a task (weather, images, finance, etc.). Queries public-apis-live for reachable, deduped options.
Choosing a Public API
When a task needs an external data source or service, query the `public-apis-live` MCP tools before guessing a provider:
1. `list_categories` to see what's available. 2. `search_apis` with a `category` and/or `search` term; prefer `status: "up"` and `auth: "none"` for zero-setup options. 3. `get_api` for full details (URL, auth, HTTPS) before recommending one.
Always tell the user the auth requirement and that status reflects *reachability*, not functional testing.
3442 working public APIs · verified 2026-10-27 · refreshed daily — 🔎 Search · 📊 Benchmark Aggregated from the top public-API lists, deduped, and reachability-checked every day.