Embedded Iot Mentor
alirezarezvani/claude-skills
Mentor for embedded and IoT hardware projects. An agent skill from alirezarezvani/claude-skills.
Checks a KiCad board's production BOM against the schematic, PCB footprints and JLCPCB's parts catalog, then explains which failures are real.
Install JLCPCB BOM Verifier
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bom --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .claude/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .claude/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bomType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bom --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .agents/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .agents/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bom --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .cursor/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .cursor/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jamro/tiny-engineer.git --path .cursor/skills/verify-jlcpcb-bom--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bom --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .gemini/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .gemini/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bomInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .github/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .github/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jamro/tiny-engineer verify-jlcpcb-bom --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jamro/tiny-engineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/verify-jlcpcb-bom .opencode/skills/verify-jlcpcb-bom && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify-jlcpcb-bom" agent skill from https://github.com/jamro/tiny-engineer/tree/main/.cursor/skills/verify-jlcpcb-bom into .opencode/skills/verify-jlcpcb-bom/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-jlcpcb-bom", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify-jlcpcb-bom- GitHub stars
- 580
- Token cost
- ~2k tokens
- SKILL.md length
- 1,016 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks a KiCad board's production BOM against the schematic, PCB footprints and JLCPCB's parts catalog, then explains which failures are real.
- Checking whether a board's BOM matches its schematic and footprints
- SKILL.md covers Run, How to read the report, Interpret and Recommend a fix, plus 1 more section
- Runs Python scripts from its folder; calls python3
- Verifying LCSC part numbers against the JLCPCB catalog before ordering
What it does
Runs a bundled script against one board's `production/bom.csv`, which is report-only and never edits the schematic, PCB, BOM or footprints itself. If the user hasn't named a board and only one exists, it runs against that one automatically; with several boards it asks which one, and a missing BOM file is never invented, instead pointing the user to generate it with KiCad's Fabrication Toolkit.
The script's output is read in a fixed order: FAIL lines first, then WARN lines, then a single PASS count of BOM rows with no problem, with a nonzero exit code meaning at least one failure. A failure covers things like a wrong or missing LCSC part id, a BOM row that disagrees with the schematic or footprint, or a passive value that disagrees with the catalog's rated resistance, capacitance or inductance; a warning covers a do-not-populate part still listed, zero stock, or a footprint pad count that disagrees with the catalog's pin count.
After quoting the raw output verbatim, every line is interpreted as real, a false positive, or informational, with lines sharing one root cause grouped together; a lookup failure that could not reach the catalog is treated as neither real nor false, since package and value simply were not checked for that part, and nothing is filled in from memory to cover the gap.
When your agent uses it
- Checking whether a board's BOM matches its schematic and footprints
- Verifying LCSC part numbers against the JLCPCB catalog before ordering
- Interpreting FAIL and WARN lines from a BOM verification run
- Telling a real part mismatch apart from a string-match false positive
Example prompts
- “Verify the BOM for the main-control-board and interpret every FAIL line.”
- “Check whether this resistor's value in the BOM matches its JLCPCB catalog rating.”
- “Group the WARN lines from the last BOM check by shared root cause.”
Requirements
- Python 3, to run the bundled BOM verification script
- A KiCad project with production/bom.csv generated
What it can do on your machine
Read from SKILL.md and the folder at commit c718397. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
JLCPCB BOM Verifier loads about 2k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 1,016 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,016 words (~2,027 tokens).
“Report only. Do not edit the schematic, PCB, BOM, or footprints.”
- name
- verify-jlcpcb-bom
Files
SKILL.md and 1 other file (scripts) in .cursor/skills/verify-jlcpcb-bom of jamro/tiny-engineer.
- SKILL.md
- scripts/verify_bom.py
Open the folder on GitHubat commit c718397
Compare with similar skills
JLCPCB BOM Verifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| JLCPCB BOM Verifier this skilljamro/tiny-engineer | 580 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Embedded Iot Mentoralirezarezvani/claude-skills | 28k | — | ~2.6k | Automated safety check: Pass | MIT | |
| RuView Hardware Setupruvnet/RuView | 97k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Esp32 Firmware Engineeralxv2016/folloup-sticky | 116 | 1 repos | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| RuView mmWave Radar Setupruvnet/RuView | 97k | — | ~907 | Automated safety check: Notes | MIT | |
| Embedded DebugFastLED/FastLED | 7.5k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
RuView Hardware Setup
ruvnet/RuView
Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.
Esp32 Firmware Engineer
alxv2016/folloup-sticky
ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.
RuView mmWave Radar Setup
ruvnet/RuView
Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.
Embedded Debug
FastLED/FastLED
Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms.
Auto Embedded
DunCanYounG-1/MICU-auto-embedded
全平台嵌入式 AI 开发框架（对标 Trellis）：把 RIPER-5 五阶段协议 + 四文件记忆 + 分层架构门禁 + Scout/Builder/Verifier 多 Agent + 24 个工具调用技能（build/flash/debug/serial/can/modbus/visa/static/memory/rtos/scons），做成『装进工程、项目级 hook…
More from jamro/tiny-engineer
EasyEDA to KiCad Importer
jamro/tiny-engineer
Imports an LCSC part into a Tiny Engineer KiCad board as library files (symbol, footprint, 3D model) using easyeda2kicad and a bundled script.
Tiny Engineer Speech
jamro/tiny-engineer
Makes the Tiny Engineer desk robot speak a short WAV clip through its speaker while it gestures, by posting to its /play endpoint with a bundled script.
Related
Categories
Questions about JLCPCB BOM Verifier
What does JLCPCB BOM Verifier do?
Checks a KiCad board's production BOM against the schematic, PCB footprints and JLCPCB's parts catalog, then explains which failures are real. csv`, which is report-only and never edits the schematic, PCB, BOM or footprints itself. If the user hasn't named a board and only one exists, it runs against that one automatically; with several boards it asks which one, and a missing BOM file is never invented, instead pointing the user to generate it with KiCad's Fabrication Toolkit.
When should I use JLCPCB BOM Verifier?
JLCPCB BOM Verifier fits situations like: checking whether a board's BOM matches its schematic and footprints; verifying LCSC part numbers against the JLCPCB catalog before ordering; interpreting FAIL and WARN lines from a BOM verification run; telling a real part mismatch apart from a string-match false positive.
How do I install JLCPCB BOM Verifier in Claude Code?
Run `npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a claude-code`. Or copy the skill folder (.cursor/skills/verify-jlcpcb-bom in jamro/tiny-engineer) into .claude/skills/verify-jlcpcb-bom in your project. Claude Code loads it when a task matches its description.
How do I install JLCPCB BOM Verifier in Codex?
Run `npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a codex`. Or copy the skill folder (.cursor/skills/verify-jlcpcb-bom in jamro/tiny-engineer) into .agents/skills/verify-jlcpcb-bom in your project. Codex loads it when a task matches its description.
Can I use JLCPCB BOM Verifier in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jamro/tiny-engineer --skill verify-jlcpcb-bom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-jlcpcb-bom, .gemini/skills/verify-jlcpcb-bom, .github/skills/verify-jlcpcb-bom and .opencode/skills/verify-jlcpcb-bom in your project.
What does JLCPCB BOM Verifier need to run?
Going by SKILL.md and its folder, JLCPCB BOM Verifier needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3, to run the bundled BOM verification script; A KiCad project with production/bom.csv generated.
Does JLCPCB BOM Verifier access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is JLCPCB BOM Verifier safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does JLCPCB BOM Verifier use?
JLCPCB BOM Verifier has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does JLCPCB BOM Verifier use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to JLCPCB BOM Verifier?
Skills that share tags, products or a category with JLCPCB BOM Verifier: Embedded Iot Mentor (alirezarezvani/claude-skills, 28k stars), RuView Hardware Setup (ruvnet/RuView, 97k stars), Esp32 Firmware Engineer (alxv2016/folloup-sticky, 116 stars) and RuView mmWave Radar Setup (ruvnet/RuView, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains JLCPCB BOM Verifier?
jamro (a GitHub user) maintains it in jamro/tiny-engineer, which has 580 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.
Source: jamro/tiny-engineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.