
Embed Ai Tool
Route vague embedded commands (flash, compile, debug) to the right skill among 24 MCU toolchain skills and guide install-all vs pick-list setup.
Overview
embed-ai-tool is a journey-wide agent skill that routes embedded build, flash, and debug requests to the correct toolchain skill among 24 options—usable whenever a solo builder issues a vague MCU command before committin
Install
npx skills add https://github.com/leokemp223/embed-ai-tool --skill embed-ai-toolWhat is this skill?
- Meta controller for embed-ai-tool repo: install引导 and instruction disambiguation
- 24 skills across build, flash, debug, comms, and analysis (CMake, Keil, IAR, IDF, OpenOCD, J-Link, GDB, Modbus, CAN, VIS
- Install flow requires user choice: all 24 skills vs on-demand names—no silent full install
- Disambiguation lists category candidates when user says 烧录/编译/调试 without naming a toolchain
- Marked internal metadata skill as repo entry point
- 24 skills in the embed-ai-tool catalog
- 5 workflow categories: 构建, 烧录, 调试, 通信, 分析
Adoption & trust: 1 installs on skills.sh; 557 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You said “flash firmware” or “debug” and the agent picked the wrong IDE or probe because your board could be Keil, J-Link, or ESP-IDF.
Who is it for?
Indie hardware hackers using agent-assisted firmware workflows across multiple vendors and debug probes.
Skip if: Pure mobile or web SaaS builds with no on-target toolchain or physical board connected.
When should I use this skill?
User requests installing embed-ai-tool repo skills, or issues vague embedded 烧录/编译/调试 instructions without a specific toolchain.
What do I get? / Deliverables
You get a categorized candidate list and a guided install path, then hand off to the specific build-, flash-, or debug-* skill that matches your hardware.
- User-selected install set or full 24-skill install commands
- Disambiguation table leading to one concrete child skill invocation
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
User says 编译—agent lists build-cmake vs build-idf vs build-keil before running CMake.
Bring-up board: pick flash-jlink vs flash-openocd after confirming debug probe.
Route to debug-gdb-openocd or rtos-debug for pre-release crash reproduction.
Field issue: serial-monitor plus modbus-debug for bus traces without guessing skill names.
How it compares
Meta router and installer for the embed-ai-tool skill bundle, not a single-flash script like flash-openocd alone.
Common Questions / FAQ
Who is embed-ai-tool for?
Solo embedded developers using Claude Code-style agents who need disambiguation across Keil, PlatformIO, ESP-IDF, OpenOCD, and J-Link workflows.
When should I use embed-ai-tool?
At first install of the repo; whenever a command is ambiguous (compile/flash/debug); during Build integrations daily; in Ship testing when attaching GDB; in Operate when capturing serial or RTT logs from production firmware.
Is embed-ai-tool safe to install?
Review the Security Audits panel on this page; downstream skills may invoke shell, hardware debuggers, and serial devices—install only the skills you need.
Workflow Chain
Then invoke: build cmake, flash openocd
SKILL.md
READMESKILL.md - Embed Ai Tool
# embed-ai-tool 总控 本技能负责两类交互:**安装引导** 和 **指令消歧**。 --- ## 一、安装引导 当用户请求安装本仓库的 skill 时,按以下流程引导。不要跳过询问直接安装。 ### 流程 1. 向用户展示下面的 **可用技能列表** 2. 询问用户选择安装方式: - **全部安装** — 安装所有 24 个 skill - **按需安装** — 用户指定要安装的 skill 名称 3. 根据用户选择执行对应的安装命令 ### 可用技能 | 分类 | 技能 | 说明 | |------|------|------| | 构建 | `build-cmake` | 配置并构建基于 CMake 的 MCU 固件工程 | | 构建 | `build-keil` | 配置并构建基于 Keil MDK 的固件工程 | | 构建 | `build-iar` | 配置并构建基于 IAR EWARM 的固件工程 | | 构建 | `build-platformio` | 配置并构建基于 PlatformIO 的固件工程 | | 构建 | `build-idf` | 配置目标芯片并构建 ESP-IDF 固件工程 | | 构建 | `build-makefile` | 配置并构建基于 Makefile 的固件工程 | | 烧录 | `flash-keil` | 通过 Keil MDK 内置调试器烧录固件 | | 烧录 | `flash-openocd` | 通过 OpenOCD 烧录 ELF/HEX/BIN 产物 | | 烧录 | `flash-platformio` | 通过 PlatformIO 上传机制烧录固件 | | 烧录 | `flash-idf` | 通过 ESP-IDF 工具链烧录固件并支持 JTAG 调试 | | 烧录 | `flash-jlink` | 通过 SEGGER J-Link 烧录固件,支持 RTT 日志捕获 | | 调试 | `debug-gdb-openocd` | 通过 OpenOCD 附着 GDB 调试 | | 调试 | `debug-jlink` | 通过 J-Link GDB Server 在线调试和崩溃分析 | | 调试 | `debug-platformio` | 通过 PlatformIO 内置 GDB 调试 | | 调试 | `rtos-debug` | FreeRTOS/RT-Thread/Zephyr 线程感知调试 | | 通信 | `serial-monitor` | 串口选择与运行日志抓取 | | 通信 | `modbus-debug` | Modbus RTU/TCP 寄存器读写与从站扫描 | | 通信 | `can-debug` | CAN 总线帧监听、发送和节点扫描 | | 通信 | `visa-debug` | VISA 仪器 SCPI 通信、波形捕获和截图 | | 分析 | `memory-analysis` | .map/ELF 内存使用报告与符号排名 | | 分析 | `static-analysis` | cppcheck/clang-tidy 静态分析,MISRA-C 合规 | | 开发 | `peripheral-driver` | 搜索并适配开源 BSP 外设驱动 | | 开发 | `stm32-hal-development` | STM32 HAL 库开发指导与最佳实践 | | 编排 | `workflow` | 串联编译+烧录+监控/调试的流水线 | ### 安装命令 优先使用 `npx skills`,若用户无 Node.js 环境改用 Python 脚本。 ```bash # npx 全部安装 npx skills add LeoKemp223/embed-ai-tool -g -y # npx 按需安装 npx skills add LeoKemp223/embed-ai-tool --skill build-cmake --skill flash-openocd -g -y # Python 全部安装 python3 /tmp/embed-ai-tool/scripts/install.py /path/to/project # Python 按需安装 python3 /tmp/embed-ai-tool/scripts/install.py /path/to/project --skills build-cmake flash-openocd ``` --- ## 二、指令消歧 当用户发出模糊指令(如"烧录"、"编译"、"调试")时,先尝试自动探测工程类型;若无法明确判断,必须列出候选 skill 让用户选择,不要自行假设。 ### 消歧流程 ``` 用户输入模糊指令 │ ▼ 自动探测工程类型 │ ├─ 唯一匹配 → 直接调用对应 skill │ └─ 匹配多个或无法判断 → 列出候选 skill 供用户选择 ``` ### 自动探测规则 按工作区文件特征判断工程类型,规则优先级从高到低: | 文件特征 | 工程类型 | 对应 skill | |----------|----------|-----------| | `*.uvprojx` / `*.uvproj` | Keil MDK | `build-keil` `flash-keil` | | `platformio.ini` | PlatformIO | `build-platformio` `flash-platformio` `debug-platformio` | | `sdkconfig` + `components/` | ESP-IDF | `build-idf` `flash-idf` | | `CMakeLists.txt` + `*.cmake` | CMake | `build-cmake` | | `Makefile` / `makefile`(无 CMakeLists.txt) | Makefile | `build-makefile` | | `.jlink` 文件或 JLinkExe 在 PATH | J-Link | `flash-jlink` `debug-jlink` | | `.vscode/launch.json` 含 `openocd` | OpenOCD | `flash-openocd` `debug-gdb-openocd` | | 以上均无 | 未知 | **必须询问用户** | ### 分类候选表 当自动探测无法唯一确定时,按用户指令所属分类展示候选 skill: **编译 / 构建:** | 技能 | 适用场景 | |------|----------| | `build-keil` | Keil MDK 工程(.uvprojx) | | `build-cmake` | CMake 工程(CMakeLists.txt) | | `build-iar` | IAR EWARM 工程(.ewp) | | `build-platformio` | PlatformIO 工程(platformio.ini) | | `build-idf` | ESP-IDF 工程(sdkconfig) | | `build-makefile` | 裸 Makefile 工程 | **烧录 / 下载:** | 技能 | 适用场景 | |------|----------| | `flash-keil` | Keil 工程 + 内置调试器(ST-Link / J-Link / CMSIS-DAP) | | `flash-openocd` | OpenOCD 兼容探针(ST-Link / CMSIS-DAP / DAPLink) | | `flash-jlink` | SEGGER J-Link 探针 | | `flash-platformio` | PlatformIO 上传(串口 / JTAG / DFU) | | `flash-idf` | ESP-IDF 工具链(ESP32 系列串口烧录) | **调试:** | 技能 | 适用场景 | |------|----------| | `debug-gdb-openocd` | OpenOCD + GDB 调试 | | `debug-jlink` | J-Link GDB Server 调试 | | `debug-platformio` | PlatformIO 内置 GDB | | `rtos-debug` | RTOS 线程感知调试(FreeRTOS / RT-Thread / Zephyr) | **通信 / 监控:** | 技能 | 适用场景 | |------|----------| | `serial-monitor` | 串口日志抓取 | | `modbus-debug` | Modbu