registry-search
Skill477 starsChanged 11 days agoMITView on GitHub
Find reusable registry modules and component packages for a board or specification.
In this repository4 other files it gives its agents.
- importing-kicad-projectsSkill
- librarianSkill
- spice-simSkill
- zener-languageSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Search the registry before authoring a new reusable package.
- Very specific: line 12
Prefer a reusable module that matches the need, then a component with its support circuitry, then a primitive.
- Very specific: line 20
If no suitable package exists or one needs a fix, use librarian in a registry checkout.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.