takazudo/jlcpcb-component-finder
skills/jlcpcb-component-finder/SKILL.md
Search the JLCPCB electronic components database (~7M parts) for hardware projects. Use when: (1) Finding components (resistors, capacitors, inductors, ICs, connectors, diodes, transistors, MOSFETs, op-amps, microcontrollers, sensors, LEDs, voltage regulators, audio jacks, etc.), (2) Looking up part numbers, LCSC (C-prefix), or manufacturer part numbers, (3) Finding alternatives/equivalents, (4) Checking stock at JLCPCB/LCSC, (5) Getting specs (package, footprint), (6) Searching SMD or through-hole parts. Keywords: JLCPCB, LCSC, PCB parts, SMT, PCBA, BOM, component sourcing.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources jlcpcb-component-finderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 10, 2026, 5:48 AM147.9s4 files scanned
SKILL.md
- name:
- jlcpcb-component-finder
- description:
- Search the JLCPCB electronic components database (~7M parts) for hardware projects. Use when: (1) Finding components (resistors, capacitors, inductors, ICs, connectors, diodes, transistors, MOSFETs, op-amps, microcontrollers, sensors, LEDs, voltage regulators, audio jacks, etc.), (2) Looking up part numbers, LCSC (C-prefix), or manufacturer part numbers, (3) Finding alternatives/equivalents, (4) Checking stock at JLCPCB/LCSC, (5) Getting specs (package, footprint), (6) Searching SMD or through-hole parts. Keywords: JLCPCB, LCSC, PCB parts, SMT, PCBA, BOM, component sourcing.
JLCPCB Parts Finder
Search ~7 million electronic components in the local JLCPCB database.
Database
- Path:
$HOME/.jlcpcb-db/cache.sqlite3(~5 GB, yaqwsx/jlcpartssource-db-v2schema: tablejlc_components) - Override the path with the
JLCPCB_DB_PATHenv var if needed - If missing, tell the user to run
/jlcpcb-component-finder-update-db
Query Script
All queries use: node $HOME/.claude/skills/jlcpcb-component-finder/query.js <command>
Commands
| Command | Usage | Description |
|---------|-------|-------------|
| db-info | node query.js db-info | Show DB stats (total parts, categories, stock count, DB date) |
| list-categories | node query.js list-categories [keyword] | List categories, optionally filtered by keyword |
| search-parts | node query.js search-parts <category> [keyword] [limit] | Search within a category (category is a NAME substring, matched against category/subcategory) |
| search-all | node query.js search-all <keyword> [limit] | Search across ALL categories by keyword |
| lookup | node query.js lookup <lcsc_number> | Look up a specific part by LCSC number (e.g. C12084) |
Examples
# Check database status
node $HOME/.claude/skills/jlcpcb-component-finder/query.js db-info
# Find audio-related categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js list-categories "audio"
# Search for 3.5mm audio jacks within the "Audio" category
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-parts "Audio" "3.5" 10
# Search for CH340 across all categories
node $HOME/.claude/skills/jlcpcb-component-finder/query.js search-all "CH340" 10
# Look up a specific part
node $HOME/.claude/skills/jlcpcb-component-finder/query.js lookup C12084
Workflow
- Understand request - What component does the user need?
- Find category - Use
list-categories [keyword]orsearch-allfor quick discovery - Search parts - Use
search-partswith a category name, orsearch-allfor cross-category - Present results with LCSC number, manufacturer, description, package, stock, price, and URL
Output Fields
Each result includes:
- LCSC number (C-prefix, e.g. C12084)
- Manufacturer and description
- Package type (e.g. SOP-8, 0805)
- Stock availability (sorted highest first)
- Basic/Preferred tags - Basic parts have lower assembly fees at JLCPCB
- Price tiers (quantity breaks)
- Datasheet URL (when available)
- Detail page URL:
https://jlcpcb.com/partdetail/C{number}
Tips
- Basic parts have the lowest JLCPCB assembly fee - prefer these when possible
- Preferred parts are commonly used and well-stocked
- Start with broader keywords if specific searches return no results
- Use
search-allwhen you don't know the category - Use
list-categorieswith a keyword to discover category names - Limit initial searches to 10-20 results to avoid overwhelming output
- Results are sorted by stock (descending) - highest stock = most available
- Always include the detail page URL in recommendations
Related Skills
takazudo/finalize-codex-work
tools
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Jul 10, 2026
takazudo/fig-url-refer
tools
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Jul 10, 2026
takazudo/dev-codex-sync-settings-from-claude
tools
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Jul 10, 2026
takazudo/video-reader
development
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Jul 7, 2026