zhinkgit/embeddedskills
12 skills12 installs4.1k starsGitHub
Install
npx skills add https://github.com/zhinkgit/embeddedskillsSkills in this repo
1Cancan is a Claude Code skill for embedded builders who need repeatable CAN and CAN-FD bus workflows without juggling disparate CLI tools. It wraps python-can and cantools behind agent-friendly operations: discover whether pcann, vector, slcan, or other backends are available; apply workspace-level bitrate and channel defaults from .embeddedskills/config.json; and run monitor, send, record, and decode tasks from natural language. Environment config keeps slcan serial port and baud rate separate from per-project interface choices, with a documented parameter priority so overrides behave predictably on the bench. Solo developers shipping automotive, robotics, or industrial firmware can use it during integration to validate frames against a DBC, capture reproducible logs for regressions, and inspect bus load before shipping hardware. It expects Python 3.x and vendor drivers where USB adapters require them, and it is not a replacement for full vehicle simulation or compliance certification tooling.1installs2Eideeide is a Claude Code agent skill for developers who standardize on Embedded IDE (EIDE) inside VS Code. It discovers firmware workspaces by locating `.eide/eide.yml`, lists named build configurations, and drives the bundled unify_builder to incrementally compile, fully rebuild, or clean targets. After a successful run it surfaces artifact paths such as ELF and HEX so you can continue with J-Link, OpenOCD, or your own flash pipeline without retyping paths from the UI. The skill also runs toolchain size analysis on ELF output and turns noisy compiler logs into structured errors and warnings your agent can act on. You configure once via skill-level `config.json` (builder directory, optional `code_exe`, toolchain prefix, and safety-oriented operation_mode). Prerequisites are VS Code with the EIDE extension, an ARM AC5/AC6 or arm-none-eabi-gcc toolchain, Python 3, and PyYAML. It targets indie and small-team embedded builders who want repeatable agent-driven builds on Windows-first EIDE installs while staying compatible with a generic agent workflow.1installs3Gccgcc is an agent skill for solo builders and indie hardware teams shipping on ARM microcontrollers. It targets CMake-first embedded repositories that use the Arm GNU toolchain (arm-none-eabi-gcc) and optionally Ninja or Make as the backend generator. The skill discovers projects under a workspace, lists presets from CMakePresets.json, and drives configure and build steps so your agent does not hand-type fragile cmake invocations. After a successful link, it analyzes the ELF for flash and RAM budgeting—text, data, and bss—so you catch size regressions before flashing. Configuration splits between skill-level config.json (cmake path, toolchain prefix, bin directory, safety mode) and per-workspace .embeddedskills/config.json for default project, preset, and log directory. Python orchestration uses only the standard library. When you need on-device debug, documented outputs align with downstream jlink and openocd skills in the same embeddedskills family.1installs4Jlinkjlink is an agent skill for solo embedded developers who debug and ship firmware through SEGGER J-Link on Windows-oriented paths (JLink.exe, JLinkGDBServerCL, RTT client, optional arm-none-eabi-gdb). It documents configuration via skill/config.json cloned from config.example.json, including serial number, RTT telnet port, SWO commands, and operation mode. Agents can use it to verify probe attachment, program images, inspect memory and registers, stream RTT logs, and run GDB-backed source debugging—work that spans bring-up during build and diagnosis during ship. Python standard library wraps CLI invocation without extra pip deps. Use when your board support package is ready but flashing and live debug still require repeatable probe commands instead of ad-hoc GUI clicking.1installs5KeilKeil is an agent skill for solo and indie embedded builders who ship on ARM Cortex MCUs with Keil MDK instead of only desktop software. It wraps UV4.exe so your coding agent can discover Keil projects in a tree, list Targets, run incremental or full rebuilds, clean, and optionally trigger Keil’s flash path while surfacing paths to hex/axf-style outputs for J-Link or OpenOCD. Configuration splits environment defaults in skill config.json (uv4_exe path, operation_mode) from per-repo settings under .embeddedskills/config.json for default project, target, and log_dir. Python uses only the standard library. Use it when you want repeatable, scriptable builds from Claude Code or Cursor on Windows-heavy embedded workflows without manually clicking through µVision for every iteration.1installs6NetThe net skill from embeddedskills equips Claude Code to troubleshoot embedded network stacks the way a field engineer would: discover interfaces, capture with Wireshark’s tshark and dumpcap, analyze pcaps offline, and run ping, routing, port scans, and live statistics. Solo builders on Windows-centric embedded bring-up need Wireshark, Npcap, and Python 3 with no extra pip packages; optional admin rights apply for capture. Configuration separates machine-level tshark paths from workspace `.embeddedskills/config.json` fields such as default interface, targets, capture and display filters, duration, scan ports, and log directory. It targets firmware and IoT integration work—not cloud SaaS dashboards—when MQTT, Modbus-TCP, or custom UDP misbehaves on the bench. Use it when the agent should reproduce connectivity failures with artifacts (pcap files and logs) instead of guessing from code alone.1installs7Openocdopenocd is an agent skill for solo hardware and firmware builders who need OpenOCD driven from the terminal without juggling opaque one-off scripts. It wraps probe detection, image programming, flash erase modes, GDB server startup, target reset, interactive Telnet debugging, structured GDB sessions, and Semihosting or ITM trace capture for ARM targets. Configuration splits environment-level skill/config.json (executable path, scripts directory, GDB and Telnet ports, gdb_exe, and operation_mode for direct run, risk summary, or confirm-before-execute) from per-project .e-style settings described in the skill. Prerequisites are a installed OpenOCD binary, Python 3 stdlib only, appropriate debugger drivers, and Arm GNU Toolchain when you use GDB subcommands. Use it while iterating firmware on real boards when you need repeatable flash-and-debug steps your coding agent can invoke instead of manual copy-paste of OpenOCD commands.1installs8Probe RsProbe-rs is an agent skill that wraps the official probe-rs CLI for embedded developers who already use the embeddedskills workflow stack alongside J-Link and OpenOCD. It exposes list, info, flash, erase, reset, read-mem, write-mem, one-shot GDB, and RTT helpers with JSON outputs and timing metadata so agents can script repeatable bring-up without relearning each debugger’s flags. Solo builders on STM32 and similar targets configure chip, protocol, probe, and speed in .embeddedskills/config.json while accepting that probe-rs itself must be installed externally and that Windows J-Link users may need WinUSB tradeoffs against SEGGER tools. Workflow integration limits probe-rs to one-shot debug rather than long-lived DAP sessions, which keeps orchestration predictable for CI and local agent runs. Use it when you are integrating firmware builds with automated flash-and-test loops rather than only editing application code on a host OS.1installs9Serialserial is a Claude Code skill from the embeddedskills family for practical UART and USB-serial work on solo hardware projects. It helps you discover COM ports, watch firmware boot logs in real time, push test commands or Hex frames, and persist traces for later diffing with your agent. Configuration lives at the workspace level in `.embeddedskills/config.json`, covering baud rate, parity, encoding, timeouts, and log paths, while CLI flags win when you need a one-off session. The workflow assumes Python 3 with pyserial installed and socat when you need multiplexing across streams. It is aimed at indie builders flashing MCUs, debugging AT modules, or validating sensor streams—not at production fleet monitoring. Pair it with your board docs and flashing scripts so the agent can reproduce the same serial steps you would run manually in a terminal.1installs10SshThe ssh skill is a Claude Code–oriented procedural package for everyday OpenSSH work: maintaining a single source of truth in ~/.ssh/config, resolving Host aliases, executing remote commands, moving files with scp, and setting up local port forwards or jump hosts. It targets embedded and Linux lab setups—example configs reference dev boards and bastions—but any solo builder with a few VPS or Pi nodes gets the same benefit. Scripts under ssh_config.py cover list, find, show, and add flows, with add performing a config backup first. The skill explicitly forbids storing passwords or private keys in config comments and supports optional first-connect host-key acceptance for trusted devices. No extra Python dependencies are required beyond the standard library, aligning with agents that should run deterministic CLI helpers on Windows, macOS, or Linux with an OpenSSH client installed.1installs11Terminalterminal is an agent skill from embeddedskills that gives Claude Code and similar agents a managed, bidirectional terminal layer for embedded and systems work. Instead of one-off shell snippets, you start a named background session for a serial port, SSH host, or local shell, then drive it with send, read, and foreground attach flows while logs and PID metadata stay in the workspace. Solo and indie builders shipping firmware, IoT prototypes, or CLI-heavy tooling use it when menus, AT command sequences, or long-running device consoles need the same session across many agent turns. It fits the Build integrations shelf because the first hard need is wiring the agent to real hardware during development; the same pattern carries into Ship testing and Operate infra when you SSH into field devices or tail console output. Requires Python 3, optional pyserial for UART, and a normal OpenSSH client for SSH backends.1installs12WorkflowWorkflow is a thin orchestration skill for embedded workspaces in the embeddedskills ecosystem. It does not replace Keil, GCC, EIDE, J-Link, OpenOCD, or probe-rs; it discovers which projects exist, picks backends for build, flash, debug, and observe, threads state through `.embeddedskills/state.json`, and aggregates script output. Preferred backends (auto or explicit) live under the workflow section of `.embeddedskills/config.json` alongside keil, gcc, eide, jlink, openocd, and probe-rs blocks. Operators run Python scripts such as workflow_plan and workflow_run with JSON flags for plan-only runs, full build-flash-debug chains, observe mode, and diagnose. It suits indie hardware and firmware builders who juggle multiple IDEs and probes and want one agent-guided path instead of re-documenting commands every session.1installs