Skills

Skills give Embedder reusable instructions for a particular kind of work. A skill can cover a board, an instrument, a coding standard, or a workflow your team repeats.

Use a skill

Name the skill and the task in chat:

Use debug-gdb to inspect the hard fault. Preserve the current firmware and RAM.

Embedder can also choose a relevant skill from your request. Available skill commands appear when you type /. Built-in commands take precedence when a skill has the same name.

A skill supplies instructions. You still need the required tools and hardware, and the session’s mode and approval settings still apply.

Find a starting point

Bundled skills cover board and vendor workflows, GDB and instruments, plots and dashboards, optimization, and static analysis. Examples include:

debug-gdb, debug-saleae, debug-digilent, and debug-picoscope for debugging and captures.
debug-joulescope and debug-ppk2 for power measurements.
dashboard-authoring for a project dashboard.
optimize for a measured optimization.
validate-MISRA and validate-CERT for analysis workflows.
usb-cdc plus usb-cdc-stm32, usb-cdc-esp32, usb-cdc-tinyusb, usb-cdc-zephyr, usb-cdc-nxp, and usb-cdc-renesas for USB CDC ACM bring-up, enumeration debugging, and Windows, macOS, and Linux host diagnostics against the vendor drivers and examples.
ethernet-driver plus ethernet-stm32, ethernet-nxp, ethernet-esp-idf, ethernet-zephyr, and ethernet-linux for MAC/PHY bring-up, DMA ownership, and validation on the matching SDK or OS.

The available skills depend on the selected platform and project setup. Use the displayed name when invoking one. Peripheral packs (usb-cdc and ethernet-driver) include a shared router skill that dispatches to the platform-specific skill when the target is known. Name the router when you want it to pick. Name the platform skill directly when you already know which stack applies.

Install a skill

Run the installer from the project directory:

embedder skill install "./path/to/skill-directory"

The directory must contain SKILL.md. You can also install a single file or an HTTPS source:

embedder skill install "./path/to/SKILL.md"
embedder skill install "https://github.com/owner/repository/tree/main/skills/board"

Installation defaults to .embedder/skills/ in the current project. Add --user to make it available across your projects, --project-root <path> for a different project, or --overwrite to replace an existing skill. Read a skill’s instructions before installing it, particularly any commands it asks Embedder to run.

Write a project skill

Create .embedder/skills/board-bringup/SKILL.md:

---
name: board-bringup
description: Build, flash, and verify the team's sensor board.
---

# Board bring-up

1. Read EMBEDDER.md for the target and build command.
2. Build the debug image and stop if it fails.
3. Confirm the connected board before flashing.
4. Capture UART output and check for "self-test: pass".
5. Report the artifact and observed result.

Use a lowercase name with hyphens. Put supporting references beside the skill and link to them from its instructions. Describe a specific workflow with a completion check. Embedder also recognizes skills in .agents/skills/ and .claude/skills/, plus the corresponding directories under your home folder. Keep one authoritative version of a skill to avoid conflicting instructions.

Get started

Core concepts

Complex workflows

Monitor and debug

Project tools

Customize

Integrations

Automation

CLI

Reference

Use a skill

Find a starting point

Install a skill

Write a project skill

​Use a skill

​Find a starting point

​Install a skill

​Write a project skill

Use a skill

Find a starting point

Install a skill

Write a project skill