Run any Skill in Manus with one click

keil-build

Compile Keil MDK projects (.uvprojx) via command line using Keil UV4 compiler, supporting incremental build and full rebuild, and parse build results. Trigger scenarios: (1) Compile Keil/MDK ARM project, (2) User mentions "build", "compile", "construct" project, (3) Need to check if project has build errors or warnings, (4) Need to compile before flashing firmware. Even if user just says "compile it for me" or "build this project", this skill should be used.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/changde-tang/embedded-skills --skill keil-build

Copy and paste this command into Claude Code to install the skill

Source

changde-tang/embedded-skills

Stars6

Forks0

UpdatedApril 22, 2026 at 03:34

File Explorer

2 files

SKILL.md

readonly

name

keil-build

description

Keil Project Compilation

Invoke py_keil_build.py to compile projects via Keil UV4 command-line interface, and return structured build results.

Tool Script

Script Path: py_keil_build.py Dependencies: Python 3.x standard library + Installed Keil MDK (with UV4.exe)

Usage

# Incremental build (default)
python py_keil_build.py -p <project.uvprojx>

# Full rebuild (clean rebuild)
python py_keil_build.py -p <project.uvprojx> -r

# Specify UV4.exe path
python py_keil_build.py -p <project.uvprojx> -k "D:\keil\UV4\UV4.exe"

Parameter Description

Parameter	Short	Description	Default
`--project`	`-p`	`.uvprojx` file path	Required
`--keil`	`-k`	UV4.exe path	`D:\application\keil_v5\UV4\UV4.exe`
`--rebuild`	`-r`	Full rebuild	Incremental build

Output Structure

Returns JSON format result:

{
  "status": "success",       // "success" or "failed" or "error"
  "log_path": "C:\\project\\Objects\\GD32F303RCT6.build_log.htm",  // 编译日志路径
  "errors": 0,                // 编译错误数
  "warnings": 3               // 编译警告数
}

Notes

Keil default installation path: D:\application\keil_v5\UV4\UV4.exe, if different please specify with -k
Build output is printed directly to terminal (no log file generated)
Build success is determined by checking if *build_log*.htm exists after compilation
- First checks: <project_dir>\Objects\*build_log*.htm
- Falls back to searching recursively in project directory

Typical Workflow

First use keil-parser to confirm project configuration is correct
Call this tool to build, check if errors_count is 0
After successful build, use jlink-download to flash firmware

More from this repository

same repository

arm-tools-chain

changde-tang/embedded-skills

ARM MCU development full-process orchestration skill. Must read this file first when performing any ARM/Keil/MDK/STM32/GD32 related development tasks to determine execution order and strategy. Applicable scenarios: using ARM toolchain, developing new features, adding logs, compiling and flashing, debugging and viewing logs, full-process development, etc. Keywords: Keil, MDK, ARM, STM32, GD32, uvprojx, compile, flash, RTT, log, development.

2026-04-226

agent-log-helper

changde-tang/embedded-skills

A guidance skill for integrating the agent_log logging system into Keil/MDK projects. Triggers: (1) User says "add agent_log", "add logging system", (2) User needs structured logging in Keil project, (3) User wants to add log output but doesn't know where to start, (4) User needs log initialization template or tick function implementation. Even if user just says "add log" or "use RTT logging", this skill should be used.

2026-04-186

jlink-download

changde-tang/embedded-skills

Use J-Link debugger to flash firmware (.bin or .hex) to ARM Cortex-M microcontrollers, supporting GD32/STM32 and other chips. Trigger scenarios: (1) Flash firmware to microcontroller, (2) User mentions "flash", "burn", "download firmware", "download", (3) Need to write compiled .bin or .hex file to chip, (4) Program target board via J-Link. Even if user just says "flash it" or "burn the chip", this skill should be used.

2026-04-186

jlink-rtt

changde-tang/embedded-skills

Read SEGGER RTT log output in real-time via J-Link debugger, supporting auto-scan of RTT control block addresses, applicable for debugging GD32/STM32 and other ARM Cortex-M microcontrollers. Trigger scenarios: (1) Read RTT debug logs from microcontroller, (2) User mentions "RTT", "view logs", "read serial" (RTT scenario), "real-time logs", (3) Need to view output information when debugging microcontroller programs, (4) Using features similar to SEGGER RTT Viewer. Even if user just says "see what the microcontroller prints" or "read RTT", this skill should be used.

2026-04-186

keil-uvprojx-modifier

changde-tang/embedded-skills

Use this skill to operate Keil MDK's .uvprojx project files. Applicable scenarios: list all Groups and files in project, add source files to specified Group (.c/.cpp/.s/.asm/.lib/.h etc.), remove files from project, create or delete Groups, manage include paths (add/remove/list). Use this skill when user mentions Keil, uvprojx, MDK project file management, or needs batch modification of Keil project structure.

2026-04-186

keil-parser

changde-tang/embedded-skills

Parse Keil MDK project files (.uvprojx), extract macro definitions, include paths, and source file lists. Trigger scenarios: (1) Need to read or analyze Keil project configuration, (2) Query project's macro definitions (defines), header file paths (include paths), source file list, (3) Need to understand project structure before compiling, flashing, etc., (4) User mentions .uvprojx file and wants to know its contents. Even if user just says "check project configuration" or "analyze this Keil project", this skill should be used.

2026-04-186

Source

changde-tang

changde-tang/embedded-skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

name

keil-build

description

Keil Project Compilation

Invoke py_keil_build.py to compile projects via Keil UV4 command-line interface, and return structured build results.

Tool Script

Script Path: py_keil_build.py Dependencies: Python 3.x standard library + Installed Keil MDK (with UV4.exe)

Usage

# Incremental build (default)
python py_keil_build.py -p <project.uvprojx>

# Full rebuild (clean rebuild)
python py_keil_build.py -p <project.uvprojx> -r

# Specify UV4.exe path
python py_keil_build.py -p <project.uvprojx> -k "D:\keil\UV4\UV4.exe"

Parameter Description

Parameter	Short	Description	Default
`--project`	`-p`	`.uvprojx` file path	Required
`--keil`	`-k`	UV4.exe path	`D:\application\keil_v5\UV4\UV4.exe`
`--rebuild`	`-r`	Full rebuild	Incremental build

Output Structure

Returns JSON format result:

{
  "status": "success",       // "success" or "failed" or "error"
  "log_path": "C:\\project\\Objects\\GD32F303RCT6.build_log.htm",  // 编译日志路径
  "errors": 0,                // 编译错误数
  "warnings": 3               // 编译警告数
}

Notes

Keil default installation path: D:\application\keil_v5\UV4\UV4.exe, if different please specify with -k
Build output is printed directly to terminal (no log file generated)
Build success is determined by checking if *build_log*.htm exists after compilation
- First checks: <project_dir>\Objects\*build_log*.htm
- Falls back to searching recursively in project directory

Typical Workflow

First use keil-parser to confirm project configuration is correct
Call this tool to build, check if errors_count is 0
After successful build, use jlink-download to flash firmware