Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mixelpixx/konnect
Mandatory operating rules for ANY task involving KiCAD projects. Loaded when the user mentions KiCAD, schematics, PCBs, or any .kicad_* file. Prevents file corruption by routing all changes through Konnect MCP tools.
Passed 12 of 17 test cases with the skill, and 8 of 17 without it.
and 7 more in the full report
6 fixed9 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to work on adding components and wiring schematic symbols simultaneously. Should I call `load_toolset("sch_components")` and then separately call `load_toolset("sch_wiring")`, or is there an array syntax to load multiple toolsets at once?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that load_toolset accepts an array of toolset names. | Missed | Passed |
| States that array loading executes in a single call with one context refresh. | Missed | Passed |
The instructions your model reads when the skill loads.
KiCAD source files are not text files. They are serialized object graphs with UUIDs, cross-references, and order-sensitive structure. Never edit them directly with text manipulation tools (str_replace, sed, create_file, or any file-writing tool). All modifications go through Konnect MCP tools.
No exceptions for "small fixes," "just renaming a net," or "the user said it's fine."
*.kicad_sch — schematic sheets*.kicad_pcb — PCB layout*.kicad_pro — project configuration*.kicad_sym / *.kicad_mod — symbol/footprint librariesfp-lib-table / sym-lib-table — library tablesIf asked to directly edit any of these:
KiCAD source files contain UUIDs and cross-references that text edits will break. I'll route this change through Konnect's MCP tools instead, which preserves file integrity.
All writes go through MCP tools. Check they are available first (list_toolboxes). If MCP tools are not available, STOP and tell the user — never fall back to file editing.
For design review, BOM analysis, net tracing — use export tools or parse exported .net/BOM/CSV files, not the source files directly.
Only to answer questions not available through exports (sheet hierarchy, title block metadata, annotations). Read with file-reading tools, but never modify.
Before a mutation, a dependent check, a retry, or a completion claim, read the reliability contract, starting with "For callers: establish what happened". Apply its outcome, source, coverage and recovery rules to the fields this installed server actually returns. Guidance does not establish that a missing server-side check ran.
test cases passed, vs 8 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.