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/tools
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
tools
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
tools
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
development
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.