skills/jlcpcb-component-finder-update-db/SKILL.md
Download or update the JLCPCB electronic components database for the jlcpcb-component-finder skill. Use when: (1) User says 'update jlcpcb db', 'download jlcpcb database', 'refresh parts database', (2) The jlcpcb-component-finder skill reports database not found, (3) User wants to get the latest component data from JLCPCB/LCSC, (4) User says 'update db', 'update parts db'. Downloads ~0.6 GB split-zip (~5 GB installed) from yaqwsx.github.io/jlcparts.
npx skillsauth add takazudo/claude-resources jlcpcb-component-finder-update-dbInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
DO NOT auto-invoke this skill. This downloads ~0.6 GB and writes a ~5 GB database. Always ask for user confirmation before proceeding.
Download or update the JLCPCB parts database (~5 GB installed, ~7 million components).
Upstream now ships the slim source-db-v2 format (table jlc_components); the old
v1 format bundled a ~20 GB raw-payload table — this script drops it if it ever reappears.
curl - for downloading files7z (p7zip) - for extracting split-zip archives. Install: brew install p7zipsqlite3 - for the defensive slim-down step. Install: brew install sqliteRun the automated update script:
bash $HOME/.claude/skills/jlcpcb-component-finder-update-db/scripts/update-db.sh
This script will:
curl, 7z, sqlite3)https://yaqwsx.github.io/jlcparts/data/cache.sqlite3 using 7zcache.sqlite3.bak$HOME/.jlcpcb-db/cache.sqlite3jlcpcb_component_details payload table if present (no-op on v2) + VACUUMcache.sqlite3.bak so backups don't pile upDownload size: ~0.6 GB compressed (12×50 MB split parts + a final ~13 MB zip)
Installed size: ~5 GB (source-db-v2); the old v1 format was ~26 GB due to a raw-payload table
Download time: usually a minute or two on a decent connection
Disk space needed: during the transition you briefly hold the old DB + new DB; the script
removes the .bak automatically after install
If the download fails partway, re-run the script - it cleans up partial downloads
Database from JLC Parts by Jan Mrazek. Updated periodically from JLCPCB/LCSC component data.
node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info
If the script doesn't work, download manually:
cache.z* and cache.zip files7z x cache.zipmv cache.sqlite3 $HOME/.jlcpcb-db/development
Link Claude Code skill names mentioned in a CodeGrid article (data/{series}/{n}.md) to the author's public claude-resources repo, pinned to the latest commit hash so links don't rot. Use when: (1) user says 'linkify cc resources', 'link the skills', 'link skill names', or invokes /dev-linkify-cc-resources; (2) editing a CodeGrid article that mentions `/commits`, `/pr-complete`, `/skill-creator` or other Claude Code skills and they should point to claude-resources. Only links skills that actually exist in the public repo; skips hypothetical examples and code blocks.
development
Second opinion from Claude Opus on a plan or approach. Use when: (1) Planning phase of /big-plan needs a higher-quality review than /codex-2nd / /gco-2nd, (2) User says 'opus 2nd' or 'opus opinion', (3) Wanting Anthropic's larger model to critique a plan. Spawns a general-purpose Agent with model: opus that reads the plan file and returns structured feedback. Anthropic quota — not free.
tools
AI-based testing via subagent + a per-task test-flow skill. Use when the user wants to verify something that mechanical assertions can't fully capture — image recognition, visual size/position comparison, animation smoothness, multi-step manual flows that need AI judgment. Triggers: 'AI-based test', 'AI test', 'visual verify', 'image recognition test', 'manual operation test', 'human-eye check', 'verify visually', 'compare screenshots', 'looks the same', 'looks correct'. The skill's job is to (1) author a focused test-flow skill that captures the exact procedure + verdict criteria, then (2) dispatch a verification subagent via the Agent tool that loads BOTH the test-flow skill AND a browser-driving skill (/verify-ui primary, /headless-browser fallback) so the subagent has clear context and consistent verdicts. NEVER uses `claude -p` — subagent dispatch goes through the Agent tool exclusively.
development
End-of-workflow audit of touched GitHub issues, PRs, and branches via a Sonnet subagent. Use when: (1) /big-plan, /x-as-pr, or /x-wt-teams finishes its main work and needs to verify every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead), (2) User says 'cleanup resources', 'audit cleanup', or 'check what should be closed', (3) A long workflow ends and the manager wants a structured paper trail of what it closed/kept/deleted. Auto-execute by default — the Sonnet agent proposes, the manager (you) executes safe actions and prints a final report.