api-registry

Plugin api-registry in tyroneross/api-registry. Commands read from the repo's manifest — 1 month ago.

Skills (3)

• api-registry

  Use before writing API config, env setup, auth, or LLM client init, or when debugging a failing external-service call. Returns authoritative source URLs, latest version, and deprecation warnings. Not for general docs or how-it-works questions with no setup/debug action; use `docs-search` instead.

• build-loop-bridge

  Use when another plugin's own setup or debug flow (build-loop, debugger, research) needs api-registry's authoritative-source checks without depending on its internals — degrades silently if api-registry isn't installed. Not for a user's own API-setup or docs question; use `api-registry` or `docs-sea

• docs-search

  Use when the user asks how a library/API/tool works, wants docs for a named service, or asks about current models/versions/endpoints — informational questions, not setup. Routes via api-registry to Context7 or WebFetch for authoritative answers. Not for writing config or debugging a failing setup; u

Slash commands (9)

• /api-registry:add

  Add a new service to the registry

• /api-registry:docs

  Answer a question about a service from the local doc cache (Context7 only as fallback)

• /api-registry:feedback

  Report a bug or send feedback about the api-registry plugin

• /api-registry:init

  Initialize the api-registry database and seed 20 well-known services

• /api-registry:list

  List registered services grouped by category

• /api-registry:lookup

  Look up authoritative sources for an API/library/tool

• /api-registry:refresh

  Refresh latest-version info for registered services

• /api-registry:scan

  Auto-discover services from local projects and review candidates

• /api-registry:staleness

  List cached docs that are past the 7-day freshness window (detect only)

Hooks (1)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start-staleness.sh