Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From api-registry
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.
npx claudepluginhub tyroneross/rosslabs-ai-toolkit --plugin api-registryHow this skill is triggered — by the user, by Claude, or both
Slash command
/api-registry:build-loop-bridgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is invoked by **other plugins** (build-loop, debugger, research) that want authoritative-source checks without hard-coupling to api-registry internals.
Guides deployment workflows with CI/CD patterns, rolling/blue-green/canary strategies, multi-stage Dockerfiles for Node.js, health checks, rollbacks, and production checklists for web apps.
Share bugs, ideas, or general feedback.
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.