registry-search — Claude Code skill: what it does, how to install
Finds reusable registry modules and component packages for a board or specification. It prevents duplicate work before authoring hardware designs.
npx skills add diodeinc/pcb --skill registry-search -a claude-codeWhat registry-search does
The skill queries the registry to locate existing hardware packages before you build new ones. It follows a strict priority order: first matching reusable modules, then components with support circuitry, and primitives last. To inspect public APIs, it runs pcb list -m -json <module-url>@<version> to read candidate source files. Inferring IO or config parameters directly from search results is prohibited.
Selected .zen entrypoints are instantiated with Module(), managing dependencies through zener-language. Editing pcb.toml by hand is not allowed. The skill also avoids cloning other boards unless you explicitly request it, and any requested clones stay outside the working repository.
If a package is missing or broken, board workflows must prepare a librarian-dispatch request or run librarian in a registry checkout.
What it helps with
- search the registry for reusable modules and component packages
- inspect module APIs via
pcb listwithout guessing IO names - instantiate
.zenentrypoints withModule()correctly - create
librarian-dispatchrequests when matching packages are missing
Example prompts for the agent
- Search the pcb registry for a power management module matching our spec
- Inspect the candidate module API with pcb list and instantiate its .zen entrypoint
How to install registry-search
1Skills CLI (Vercel)
npx skills add diodeinc/pcb --skill registry-search -a claude-code2Manually: put the files in place
~/.claude/skills/registry-search/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/registry-search/
1Skills CLI (Vercel)
npx skills add diodeinc/pcb --skill registry-search -a codex2Manually: put the files in place
.agents/skills/registry-search/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add diodeinc/pcb --skill registry-search -a cursor2Manually: put the files in place
.cursor/skills/registry-search/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install diodeinc/pcb registry-search2Manually: put the files in place
.github/skills/registry-search/SKILL.md1Skills CLI (Vercel)
npx skills add diodeinc/pcb --skill registry-search -a gemini-cli2Platform CLI
gemini skills install https://github.com/diodeinc/pcb --path skills/registry-searchManually: put the files in place
.devin/skills/registry-search/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add diodeinc/pcb --skill registry-search -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about registry-search
How to install registry-search in Claude Code?
Run npx skills add diodeinc/pcb --skill registry-search -a claude-code.
What does registry-search do?
It finds existing packages in the pcb registry, inspects source files for their public API, and wires modules into designs without guessing configuration names.
Can I manually edit pcb.toml to add dependencies?
No. The skill explicitly forbids hand-editing pcb.toml. It requires dependency resolution via zener-language and instantiation via Module().
Source text
SKILL.md · MIT
--- name: registry-search description: Find reusable registry modules and component packages for a board or specification. --- # Registry Search Search the registry before authoring a new reusable package. Read a candidate's source (`pcb list -m -json <module-url>@<version>` reports its `dir`) for its public API; do not infer IO or config names from a search result. Prefer a reusable module that matches the need, then a component with its support circuitry, then a primitive. Instantiate the chosen `.zen` entrypoint with `Module()` and follow `zener-language` for dependencies; do not hand-edit `pcb.toml`. Discover or clone other boards only when the user explicitly asks, and clone them outside the current checkout. If no suitable package exists or one needs a fix, use `librarian` in a registry checkout; from board work, prepare a `librarian-dispatch` request.
© diodeinc · MIT · diodeinc/pcb
