Builds EIDE embedded projects via unify_builder and returns firmware artifact paths.
npx skills add https://github.com/zhinkgit/embeddedskills --skill eide
Please help me install this Agent Skill. Skill: eide Source: https://github.com/zhinkgit/embeddedskills/tree/main/eide Command: npx skills add https://github.com/zhinkgit/embeddedskills --skill eide
Embedded developers using the EIDE VS Code extension must manually locate projects, pick build configurations, run builds, and hunt for output files before flashing or debugging. This Skill automates that entire loop so an AI assistant can scan, build, and hand off firmware artifacts without human intervention.
.eide/eide.yml projects and lists available build configurations (ConfigName) without guessing.unify_builder for incremental builds, full rebuilds, and cleanup, parsing logs into structured error/warning counts and flash/RAM metrics.arm-none-eabi-size to report text/data/bss usage and compare two ELF files for size deltas.elf_file/hex_file paths ready to pass to jlink or openocd for flashing.Ask the AI to scan the current workspace for EIDE projects and build the default configuration, then show the resulting firmware artifact paths.
High-intent search queries and answers about installing and using this skill.
Run the eide_build.py script with the build action, pointing it at the unify_builder directory, project root, and configuration name. It invokes unify_builder with the project's builder.params file and returns JSON with artifact paths and error counts.
Use the eide_size.py analyze command with the ELF file path and a toolchain prefix like arm-none-eabi-. It runs the GNU size tool and reports text, data, bss, plus computed flash and RAM usage, and can compare two ELF files for deltas.
You need VS Code with the cl.eide extension installed (which provides unify_builder), an ARM CC or arm-none-eabi-gcc toolchain, and Python 3 with PyYAML. The builder_dir path must be configured in the skill's config.json.
The builder.params file is generated by the EIDE extension when a project is first opened in VS Code. Open the project in VS Code with EIDE at least once so the file is created under build/<ConfigName>/ before running builds.
Yes, successful builds return flash_file (hex/bin) and debug_file (elf/axf) paths in the JSON output. These artifacts are compatible with Keil MDK formats and can be passed directly to jlink or openocd flashing skills.
ortus-docsSet up BoxLang development on Chromebooks with Linux, Java 21, and VS Code.
LeoKemp223Flash ELF, HEX, and BIN firmware to microcontrollers via SEGGER J-Link.
LeoKemp223Automates Keil MDK project builds and generates AXF, HEX, and BIN firmware files.
TimeKastCodify CC-native doctrine for authoring and refactoring tk-* workflow skills.