القائمة
Contract for external plugins (build-loop, debugger, research) to consult api-registry during API setup or debug. Reads ~/.api-registry/registry.db; exits silently if absent.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use BEFORE writing API config, env setup, auth, LLM client init, or debugging an external service. Returns authoritative source URLs, latest version, and deprecation warnings. Triggers on any named library/API/tool.
Use when the user asks how a library/API/tool works, requests docs for a named service, or asks about current models/versions/endpoints. Routes via api-registry to Context7 or WebFetch for authoritative answers.
| name | build-loop-bridge |
| description | Contract for external plugins (build-loop, debugger, research) to consult api-registry during API setup or debug. Reads ~/.api-registry/registry.db; exits silently if absent. |
This skill is invoked by other plugins (build-loop, debugger, research) that want authoritative-source checks without hard-coupling to api-registry internals.
Consumers should:
~/.api-registry/registry.db exists?api-registry not installed — skipping source verification and continue their flow. Do NOT fail./api-registry:lookup <name> — read entry/api-registry:docs <name> <query> — get routed answer/api-registry:refresh <name> — re-check version before config.env, client init, auth setup).These three commands are the stable external API:
lookup — input: name; output: JSON service recorddocs — input: name + query; output: answered text with citationrefresh — input: name/--all/--stale; output: drift summary JSONInternals (scripts, DB schema, YAML layout) may change without notice.