eide

Original：🇨🇳 Chinese

Translated

4 scriptsChecked / no sensitive code detected

EIDE (Embedded IDE) project build tool, used to scan .eide/eide.yml projects, enumerate build configurations (ConfigName), execute build/rebuild/clean and parse build logs, returning artifact paths that can be reused by jlink/openocd. It is automatically triggered when users mention EIDE, Embedded IDE, eide.yml, unify_builder, VS Code EIDE Extension, or Cl.eide, and also supports explicit invocation via /eide. Even if users only say "Compile with EIDE" or "Burn to board via EIDE", this skill should be triggered as long as the context involves EIDE embedded projects.

5installs

Sourcezhinkgit/embeddedskills

Added on2026-08-14

NPX Install

npx skill4agent add zhinkgit/embeddedskills eide

SKILL.md Content (Chinese)

View Translation Comparison →

EIDE Embedded Project Building

This skill provides capabilities for EIDE (Embedded IDE) project discovery, build configuration enumeration, incremental compilation, full rebuild, cleaning, and ELF size analysis, and returns firmware artifact paths that can be used by

jlink/openocd

.

EIDE is an embedded development extension for VS Code, using ARM CC (AC5/AC6) or GCC toolchains, driven by the unified build backend

unify_builder

.

Configuration

Environment-level Configuration (skill/config.json)

The

config.json

in the skill directory contains environment-level configurations. Confirm the

builder_dir

path is correct before first use:

json

{
  "builder_dir": "C:\\Users\\<user>\\.vscode\\extensions\\cl.eide-<version>\\res\\tools\\win32\\unify_builder",
  "builder_exe": "unify_builder.exe",
  "code_exe": "code",
  "toolchain_prefix": "arm-none-eabi-",
  "operation_mode": 1
}

```
builder_dir
```
: Directory where EIDE unify_builder is located (required, under the VS Code extension directory)
```
builder_exe
```
: Builder executable filename, default is
```
unify_builder.exe
```
for Windows
```
code_exe
```
: Path to VS Code CLI, defaults to finding
```
code
```
from PATH
```
toolchain_prefix
```
: Toolchain prefix used for size analysis, default is
```
arm-none-eabi-
```
```
operation_mode
```
:
```
1
```
Execute directly /
```
2
```
Output risk summary without blocking /
```
3
```
Confirm before execution

Project-level Configuration (workspace/.embeddedskills/config.json)

Shared project-level configurations are stored uniformly in

.embeddedskills/config.json

of the workspace:

json

{
  "eide": {
    "project": "",
    "config": "",
    "log_dir": ".embeddedskills/build"
  }
}

```
project
```
: Default root directory of EIDE project (directory containing
```
.eide/eide.yml
```
), will be automatically updated after successful build
```
config
```
: Default build configuration name (corresponding to ConfigName in eide.yml), will be automatically updated after successful build
```
log_dir
```
: Build log output directory, default is
```
.embeddedskills/build
```

Parameter Parsing Priority

Parameter parsing order (from highest to lowest):

Explicit CLI parameters
Environment-level configuration (skill/config.json)
Project-level configuration (.embeddedskills/config.json)
```
.embeddedskills/state.json
```
(last build record)
Search/query

Subcommands

Subcommand	Purpose	Risk
`scan`	Search for EIDE projects in the current directory (directories containing `.eide/eide.yml` )	Low
`configs`	Enumerate build configurations in the project	Low
`build`	Incremental compilation	Medium
`rebuild`	Full rebuild	Medium
`clean`	Clean build artifacts	High
`size`	Analyze ELF file size (text/data/bss and memory usage)	Low

Execution Flow

Read
```
config.json
```
and confirm the
```
builder_dir
```
path is valid
Default to executing
```
scan
```
when no subcommand is specified
Execute
```
scan
```
to search for projects if no project path is provided
List options for user selection when multiple projects or configurations are found simultaneously, never guess automatically
```
build/rebuild/clean
```
decides whether confirmation is needed based on
```
operation_mode
```
After successful
```
build/rebuild
```
, parse artifact paths like
```
elf_file
```
/
```
hex_file
```
from the build directory
All build commands call
```
unify_builder
```
based on
```
builder.params
```
, output to log files then parse
```
size
```
defaults to analyzing the .elf file from the most recent build

Script Invocation

Python scripts are available in the skill directory, implemented with standard libraries + PyYAML.

eide_project.py — Project Scanning and Configuration Enumeration

bash

# Scan projects
python <skill-dir>/scripts/eide_project.py scan --root <search directory> --json

# Enumerate build configurations
python <skill-dir>/scripts/eide_project.py configs --project <project directory> --json

eide_build.py — Build / Rebuild / Clean

bash

python <skill-dir>/scripts/eide_build.py <build|rebuild|clean> \
  --builder-dir <unify_builder directory> \
  --project <project root directory> \
  --config <configuration name> \
  --log-dir <log directory> \
  --json

rebuild

additionally supports

--clean-first

to clean before rebuilding.

eide_size.py — ELF Size Analysis

bash

# Basic analysis
python <skill-dir>/scripts/eide_size.py analyze \
  --elf <elf file path> \
  --toolchain-prefix arm-none-eabi- \
  --json

# Comparative analysis
python <skill-dir>/scripts/eide_size.py compare \
  --elf <elf file 1> \
  --compare <elf file 2> \
  --toolchain-prefix arm-none-eabi- \
  --json

Output Format

All scripts return in JSON format, with basic fields

status

(ok/error),

action

,

summary

,

details

, and may include

context

,

artifacts

,

metrics

,

state

,

next_actions

,

timing

.

Success example:

json

{
  "status": "ok",
  "action": "build",
  "summary": "build succeeded, errors=0 warnings=2",
  "details": {
    "project": "Vendor/EIDE",
    "config": "W20_Mainboard",
    "build_dir": "build/W20_Mainboard",
    "elf_file": "build/W20_Mainboard/MDK-ARM_F403A.elf",
    "hex_file": "build/W20_Mainboard/MDK-ARM_F403A.hex",
    "log_file": ".embeddedskills/build/MDK-ARM_F403A-W20_Mainboard-build.log"
  },
  "artifacts": {
    "elf_file": "build/W20_Mainboard/MDK-ARM_F403A.elf",
    "hex_file": "build/W20_Mainboard/MDK-ARM_F403A.hex",
    "flash_file": "build/W20_Mainboard/MDK-ARM_F403A.hex",
    "debug_file": "build/W20_Mainboard/MDK-ARM_F403A.elf"
  },
  "metrics": { "errors": 0, "warnings": 2, "flash_bytes": 32768, "ram_bytes": 8192 }
}

Error example:

json

{
  "status": "error",
  "action": "build",
  "error": { "code": "builder_not_found", "message": "unify_builder.exe does not exist, please confirm EIDE extension is installed" }
}

Core Rules

Do not modify
```
.eide/eide.yml
```
or any EIDE project configuration files
Never automatically guess project paths or build configurations; must ask the user when there is ambiguity
Refer to the "Parameter Parsing Priority" section above for parameter parsing order
After successful build, prefer to use the returned
```
flash_file
```
/
```
debug_file
```
to integrate with
```
jlink/openocd
```
```
clean
```
is not implicitly executed in automatic processes
When build fails, prioritize displaying the first error and log file path
Project name, configuration name, and build directory path are always included in result echoes; artifact paths are prioritized in echoes when build succeeds
EIDE projects take the directory containing
```
.eide/eide.yml
```
as the root directory

Relationship with Keil Projects

EIDE projects in this project share the same source code and ARM CC toolchain (

D:\Keil_V543\ARM\ARMCLANG

) as Keil MDK projects. EIDE projects describe project structure via

eide.yml

, and

builder.params

is automatically generated by EIDE for use by

unify_builder

. The build artifacts (.axf/.hex/.elf) of the two are compatible and interchangeable.

References

EIDE Extension: Search for
```
cl.eide
```
in VS Code to install
```
eide.yml
```
Format: See EIDE Extension Documentation

builder.params

: Automatically generated by EIDE, located at

build/<ConfigName>/builder.params

eide

NPX Install

Tags

SKILL.md Content (Chinese)

EIDE Embedded Project Building

Configuration

Environment-level Configuration (skill/config.json)

Project-level Configuration (workspace/.embeddedskills/config.json)

Parameter Parsing Priority

Subcommands

Execution Flow

Script Invocation

eide_project.py — Project Scanning and Configuration Enumeration

eide_build.py — Build / Rebuild / Clean

eide_size.py — ELF Size Analysis

Output Format

Core Rules

Relationship with Keil Projects

References