takazudo/easyeda2kicad
skills/easyeda2kicad/SKILL.md
Download KiCad footprints and symbols from LCSC/EasyEDA for JLCPCB PCBA projects. Use when: (1) User asks to download KiCad footprints or symbols from LCSC, (2) User provides LCSC part numbers (e.g., C3975094, C2927029), (3) User is setting up a KiCad project for JLCPCB assembly, (4) User needs exact symbol-footprint combinations for PCBA, or (5) User is working on hardware/PCB projects requiring component libraries from JLCPCB.
$ install --global
skillsauthnpx skillsauth add takazudo/claude-resources easyeda2kicadInstall 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: Apr 22, 2026, 12:07 PM135.2s1 file scanned
SKILL.md
- name:
- easyeda2kicad
- description:
- Download KiCad footprints and symbols from LCSC/EasyEDA for JLCPCB PCBA projects. Use when: (1) User asks to download KiCad footprints or symbols from LCSC, (2) User provides LCSC part numbers (e.g., C3975094, C2927029), (3) User is setting up a KiCad project for JLCPCB assembly, (4) User needs exact symbol-footprint combinations for PCBA, or (5) User is working on hardware/PCB projects requiring component libraries from JLCPCB.
easyeda2kicad - Download KiCad Libraries from LCSC/EasyEDA
Download KiCad footprints and symbols from LCSC/EasyEDA for JLCPCB PCBA projects.
Tool Overview
easyeda2kicad.py downloads KiCad libraries from LCSC/EasyEDA database:
- Footprints (
.kicad_mod) - Physical PCB pads for PCB Editor - Symbols (
.kicad_sym) - Schematic symbols for Schematic Editor - 3D Models (
.step,.wrl) - Optional 3D visualization
Critical: You need BOTH footprints AND symbols for complete KiCad design.
Installation Check
Before downloading, verify installation:
easyeda2kicad --version
If not installed:
pip install easyeda2kicad
Download Commands
Recommended: Download Both Footprint and Symbol
Always use this for JLCPCB PCBA projects to ensure exact symbol-footprint combinations:
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --symbol
Example:
# CH224D USB-PD controller
easyeda2kicad --lcsc_id C3975094 --footprint --symbol
# USB-C connector
easyeda2kicad --lcsc_id C2927029 --footprint --symbol
# Passive components (capacitors, resistors, LEDs)
easyeda2kicad --lcsc_id C7432781 --footprint --symbol # 10µF capacitor
easyeda2kicad --lcsc_id C23138 --footprint --symbol # 330Ω resistor
Overwrite Existing Files
If files already exist:
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --symbol --overwrite
Download Only Footprint or Symbol
# Footprint only
easyeda2kicad --lcsc_id <LCSC_ID> --footprint
# Symbol only
easyeda2kicad --lcsc_id <LCSC_ID> --symbol
Include 3D Models
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --symbol --3d
Download Output Locations
Footprints
$HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/
└── *.kicad_mod
Each footprint is a separate .kicad_mod file.
Symbols
$HOME/Documents/Kicad/easyeda2kicad/
└── easyeda2kicad.kicad_sym
Important: All symbols are added to a SINGLE .kicad_sym file (not separate files).
Copying to Project
After downloading, copy files to project directories:
Standard Project Structure
<project-root>/
├── footprints/
│ └── kicad/
│ └── *.kicad_mod # Copy footprints here
└── symbols/
└── <project-name>.kicad_sym # Copy symbols here
Copy Commands
# Copy footprints (specific files)
cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/<filename>.kicad_mod \
<project-root>/footprints/kicad/
# Copy symbols (entire file)
cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.kicad_sym \
<project-root>/symbols/<project-name>.kicad_sym
Example for multiple footprints:
# Copy all footprints at once
cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/*.kicad_mod \
/path/to/project/footprints/kicad/
Complete Workflow for Multiple Components
When user requests multiple components, use this pattern:
# 1. Change to download directory
cd $HOME/Documents/Kicad/easyeda2kicad
# 2. Download all components
easyeda2kicad --lcsc_id C3975094 --footprint --symbol --overwrite
easyeda2kicad --lcsc_id C2927029 --footprint --symbol --overwrite
easyeda2kicad --lcsc_id C7432781 --footprint --symbol --overwrite
# ... etc
# 3. Copy footprints to project
cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/*.kicad_mod \
<project-root>/footprints/kicad/
# 4. Copy symbols to project
cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.kicad_sym \
<project-root>/symbols/<project-name>.kicad_sym
Verifying Downloads
After copying, verify files exist:
# List footprints
ls -lh <project-root>/footprints/kicad/*.kicad_mod
# Check symbol library size
ls -lh <project-root>/symbols/<project-name>.kicad_sym
# Count symbols in library
grep -c '(symbol "' <project-root>/symbols/<project-name>.kicad_sym
Finding LCSC Part Numbers
LCSC part numbers start with 'C' followed by digits (e.g., C3975094).
Where to find them:
- User's Bill of Materials (BOM)
- LCSC.com - Search by part name
- EasyEDA.com - Component library
- User-provided specifications
Common Part Categories
Active Components (Always download both)
- ICs (USB-PD controllers, buck converters, regulators)
- Connectors (USB-C, pin headers)
- Diodes (Schottky, TVS, ESD protection)
Passive Components (Download both for JLCPCB PCBA)
- Capacitors (ceramic, electrolytic)
- Resistors (all values)
- LEDs (indicator lights)
Note: For JLCPCB PCBA, always download both footprint and symbol even for passive components to ensure exact package matching.
Troubleshooting
Error: "easyeda2kicad: command not found"
# Check installation
which easyeda2kicad
# Try Python module form
python -m easyeda2kicad --version
# Reinstall if needed
pip install easyeda2kicad
Error: "Part not found"
- Verify LCSC ID is correct (starts with 'C')
- Check part exists on LCSC.com
- Try EasyEDA ID instead with
--easyeda_id
Error: "Footprint already exists"
Use --overwrite flag:
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --symbol --overwrite
Download timeout or failure
- Check internet connection
- Retry (server may be temporarily down)
- Use
--fullfor detailed error messages:
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --full
Error: "Failed to fetch data from EasyEDA API"
Common for passive components (capacitors, resistors, LEDs) - Many JLCPCB parts exist but don't have symbols in EasyEDA's database.
Solution: Use Generic KiCad Symbols
-
Download footprint only (if available):
easyeda2kicad --lcsc_id <LCSC_ID> --footprint --overwrite -
Use KiCad's built-in generic symbols:
- Capacitors:
Device:C - Resistors:
Device:R - LEDs:
Device:LED - Inductors:
Device:L
- Pair with downloaded footprint:
- Symbol: Generic KiCad symbol (e.g.,
Device:C) - Footprint: Downloaded or generic (e.g.,
C0805.kicad_mod)
Example workflow for 22nF capacitor (C7393941):
# Try to download (may fail for symbol)
easyeda2kicad --lcsc_id C7393941 --footprint --overwrite
# If symbol download fails:
# 1. Use KiCad generic symbol: Device:C
# 2. Use footprint: C0805.kicad_mod (or downloaded footprint)
# 3. Keep LCSC part number C7393941 in BOM for JLCPCB assembly
This is standard practice - Passive components often use generic symbols with specific footprints. The LCSC part number in the BOM ensures correct component ordering for PCBA.
Expected Output
Successful download shows:
-- easyeda2kicad.py v0.8.0 --
[INFO] Created Kicad symbol for ID : C3975094
Symbol name : CH224D_C3975094
Library path : $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.kicad_sym
[INFO] Created Kicad footprint for ID: C3975094
Footprint name: QFN-20_L3.0-W3.0-P0.40-BL-EP1.7
Footprint path: $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/...
Batch Download Example
For a complete stage (e.g., USB-PD stage with 9 components):
cd $HOME/Documents/Kicad/easyeda2kicad
# Download all components for USB-PD stage
for lcsc_id in C3975094 C2927029 C7432781 C49678 C6119849 C705785 C23186 C23138 C2286; do
echo "Downloading $lcsc_id..."
easyeda2kicad --lcsc_id $lcsc_id --footprint --symbol --overwrite
done
# Copy all to project
cp easyeda2kicad.pretty/*.kicad_mod <project>/footprints/kicad/
cp easyeda2kicad.kicad_sym <project>/symbols/<project>.kicad_sym
Important Notes for Claude
- Always download BOTH footprint and symbol unless user specifically requests only one
- Use
--overwritewhen downloading multiple components to avoid conflicts - Run downloads from
$HOME/Documents/Kicad/easyeda2kicaddirectory for consistency - Copy files separately - footprints are individual files, symbols are a single file
- Verify after copying by listing files in project directories
- Inform user of symbol names so they can find them in KiCad
Quick Reference
| Task | Command |
|------|---------|
| Download both | easyeda2kicad --lcsc_id <ID> --footprint --symbol |
| Overwrite existing | Add --overwrite flag |
| Include 3D model | Add --3d flag |
| Check installation | easyeda2kicad --version |
| Copy footprints | cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.pretty/*.kicad_mod <project>/footprints/kicad/ |
| Copy symbols | cp $HOME/Documents/Kicad/easyeda2kicad/easyeda2kicad.kicad_sym <project>/symbols/<name>.kicad_sym |
References
- easyeda2kicad.py GitHub
- LCSC Component Search
- EasyEDA Component Library
- KiCad Documentation
Related Skills
takazudo/dev-linkify-cc-resources
development
VerifiedTrustedCommunity
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.
10SKILL.mdUpdated Jun 2, 2026
takazudo/opus-2nd
development
VerifiedTrustedCommunity
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.
10SKILL.mdUpdated May 29, 2026
takazudo/dev-ai-based-test
tools
VerifiedTrustedCommunity
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.
10SKILL.mdUpdated May 29, 2026
takazudo/cleanup-resources
development
VerifiedTrustedCommunity
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.
10SKILL.mdUpdated May 29, 2026