SKILLEMALL.ai
GitHub ↗ RU Sign in

CB kicad-pcb

Workflow skill for KiCAD PCB layout and routing via MCP tools. Triggers on: "layout the board", "route traces", "PCB", "place footprints", "copper pour", "board outline", "differential pair", "board setup", "track width", "via", "zone", "design rules", "stackup", "silkscreen".

mixelpixx/Konnect Claude Code author: mixelpixx AGPL-3.0 4 files body ≈ 5 509 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Workflow skill for KiCAD PCB layout and routing via MCP tools.

As a process B 71/100 · Nearly there — weak spots: result and completion, running it twice

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
B
71/100
Nearly there
Running it twice w 4
30
Result and completion w 14
40
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5509 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 166, 167, 212): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 71/100

  • 30Running it twice. 9 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5509 tokens
  • 85Steps. 83 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 11 example trigger phrases
  • +3Description length 277: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 83 items
  • +4Has examples (9 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.