🦞 zbot

An open-source embedded AI agent powered by Zephyr RTOS
zbot implements a ReAct (Reason + Act) loop that connects to any OpenAI-compatible LLM API, enabling hardware control, persistent memory, and multi-step skills.

🎬 Demo

Supported boards: nRF7002-DK (nRF5340 + nRF7002 WiFi), native_sim (Linux host) RTOS: Zephyr latest License: Apache-2.0

Architecture

hljs language-scss

┌──────────────────────────────────────────────────────┐
│                    zbot Agent                        │
│                                                      │
│  ┌──────────┐  ┌──────────┐  ┌──────────────────┐    │
│  │  Config  │  │  Memory  │  │   LLM Client     │    │
│  │ endpoint │  │ slab pool│  │  HTTPS → OpenAI  │    │
│  │ model    │  │ + NVS    │  │  compatible API  │    │
│  │ api key  │  │ summary  │  │                  │    │
│  └──────────┘  └──────────┘  └──────────────────┘    │
│                                                      │
│  ┌──────────────────────┐  ┌──────────────────────┐  │
│  │  LLM-visible Tools   │  │       Skills         │  │
│  │  (src/tools/)        │  │  (src/skills/)       │  │
│  │                      │  │                      │  │
│  │  tool_exec ──────────┼─►│  gpio  (read/write/  │  │
│  │    └─ skill_run()    │  │         blink/sos)   │  │
│  │                      │  │  system(board/uptime/│  │
│  │  read_skill ─────────┼─►│         heap/status) │  │
│  │    └─ skill_read_    │  │                      │  │
│  │       content()      │  │  (add more in        │  │
│  └──────────────────────┘  │   src/skills/<name>/)│  │
│                            └──────────────────────┘  │
│  ┌────────────────────────────────────────────────┐  │
│  │  Shell Commands  (zbot key / chat / skill ...) │  │
│  └────────────────────────────────────────────────┘  │
│                                                      │
│  ┌──────────┐                                        │
│  │ Telegram │  Long-poll thread → agent → sendMessage│
│  │   Bot    │                                        │
│  └──────────┘                                        │
└──────────────────────────────────────────────────────┘

Modules

Module	File	Purpose
Config	`config.h/c`	LLM endpoint, model, API key + WiFi credentials (NVS persistence)
Memory	`memory.h/c`	k_mem_slab conversation history + NVS rolling summary
LLM Client	`llm_client.h/c`	HTTPS POST to OpenAI-compatible Chat Completions API
Tools	`tools.h/c` + `src/tools/`	LLM-visible tool registry; each tool in its own directory, self-registers via `SYS_INIT`
Skills	`skills/skill.h/c` + `src/skills/`	Skill registry; each skill in its own directory, self-registers via `SYS_INIT`
Agent	`agent.h/c` + `src/AGENT.md`	ReAct loop; system prompt loaded from `AGENT.md` at build time
Telegram	`telegram.h/c`	Telegram Bot long-poll thread; forwards messages to agent and replies
JSON Util	`json_util.h/c`	Shared `json_get_str()` and `json_escape()`
Shell	`shell_cmd.c`	All `zbot` shell subcommands

Tool & Skill Design

The LLM sees exactly two tools:

LLM Tool	What it does
`tool_exec`	Dispatches to any registered skill by name — all hardware/system operations go here
`read_skill`	Returns the full Markdown documentation of a skill on demand

Skills are the execution units. They live in src/skills/<name>/ and self-register at boot via SYS_INIT. Each skill has:

SKILL.c — handler implementation, registered with SKILL_DEFINE
SKILL.md (optional) — Markdown documentation embedded at build time via generate_inc_file_for_target

The LLM receives only name + description for each skill per request. Full docs are fetched on demand via read_skill.

Hardware primitives (GPIO, uptime, heap) are themselves skills — the same mechanism, just without Markdown docs.

ReAct Loop

hljs language-sql

user input
    │
    ▼
build messages JSON  ←────────────────────────────────────────────────┐
    │                                                                 │
    ▼                                                                 │
LLM API call (tool_exec + read_skill exposed)                         │
    │                                                                 │
    ├── finish_reason: tool_call ──► tools_execute(name, args)        │
    │                                    └─ skill_run(name, args) ───►│
    │
    └── finish_reason: stop ──► return answer to user
                                        │
                                        ▼
                                request summary ──► NVS

Max iterations per turn: 10

Conversation Memory

History uses a 10-node static pool (k_mem_slab) backed by a sys_slist_t linked list ordered oldest → newest.

When the pool is full on memory_add_turn():

Compress — the oldest nodes are summarised by the LLM; those nodes are freed back to the slab.
Evict (fallback) — the oldest node is recycled directly.

After compression, the rolling summary is written to NVS and injected as prior context on the next boot.

Settings layout:

Key	Type	Notes
`zbot/summary`	`char[768]`	Conversation summary
`zbot/apikey`	`char[256]`	Set by `zbot key`
`zbot/host`	`char[128]`	LLM endpoint hostname
`zbot/path`	`char[128]`	LLM API path
`zbot/model`	`char[128]`	Model name
`zbot/provider_id`	`char[64]`	`X-Model-Provider-Id` header
`zbot/use_tls`	`uint8_t`	TLS enabled flag
`zbot/port`	`uint16_t`	TCP port
`zbot/tg_token`	`char[128]`	Telegram Bot token
`wifi/...`	—	Managed by Zephyr `wifi_credentials` subsystem

Prerequisites

Set up a Zephyr development environment following the official guide: https://docs.zephyrproject.org/latest/develop/getting_started/index.html

Quick Start

1. Build & Flash

nRF7002-DK (physical hardware with WiFi):

hljs language-bash

west build -b nrf7002dk/nrf5340/cpuapp zbot
west flash

native_sim (Linux host simulation, no WiFi):

hljs language-bash

west build -b native_sim zbot
./build/zephyr/zephyr.exe

2. Connect Serial

For nRF7002-DK:

hljs language-bash

minicom -D /dev/ttyACM0 -b 115200

For native_sim, the shell is on the terminal where you launched zephyr.exe.

3. Connect to WiFi (nRF7002-DK only)

hljs language-arduino

uart:~$ zbot wifi connect <SSID> <password>

Credentials are saved to flash and auto-connect on reboot.

native_sim: No WiFi configuration needed — the host OS provides the network stack.

4. Set API Key

Default Provider (OpenRouter) Get a free API key from: https://openrouter.ai/settings/keys

hljs language-vbnet

uart:~$ zbot key sk-...

The key is saved to NVS flash and restored on every reboot.

5. (Optional) Configure Endpoint

OpenAI:

hljs language-vbnet

uart:~$ zbot host api.openai.com
uart:~$ zbot path /v1/chat/completions
uart:~$ zbot model gpt-4o-mini
uart:~$ zbot key sk-...

DeepSeek:

hljs language-vbnet

uart:~$ zbot host api.deepseek.com
uart:~$ zbot path /chat/completions
uart:~$ zbot model deepseek-chat
uart:~$ zbot key sk-...

Local model (e.g. Ollama):

hljs language-vbnet

uart:~$ zbot host 192.168.1.100
uart:~$ zbot tls off 11434

6. (Optional) Configure Telegram Bot

Create a bot via @BotFather on Telegram to obtain a token.

hljs language-ruby

uart:~$ zbot telegram token 1234567890:AAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
uart:~$ zbot telegram start

The token is saved to NVS flash. Polling starts automatically on the next reboot if a token is stored.

7. Chat

hljs language-vbnet

uart:~$ zbot chat
Entering interactive chat mode. Type /exit to quit.
zbot:~$ Hello! What can you do?
Thinking...

zbot: Hi! I'm zbot ...

zbot:~$ Turn on LED0
Thinking...

zbot: Done — LED0 is now on.

zbot:~$ /exit
Leaving chat mode.
uart:~$

Shell Commands

Configuration

Command	Description
`zbot key <key>`	Set API key (saved to flash)
`zbot key_delete`	Delete API key from flash
`zbot config_reset`	Reset all config to defaults and wipe from flash
`zbot host <hostname>`	Set LLM endpoint host
`zbot path <path>`	Set LLM API path
`zbot model <name>`	Set model name
`zbot provider <id>`	Set `X-Model-Provider-Id` header
`zbot tls <on\|off> [port]`	Enable/disable TLS and set port
`zbot status`	Show current config and agent state

WiFi (nRF7002-DK only)

Command	Description
`zbot wifi connect <ssid> [pass]`	Connect to WiFi and save credentials
`zbot wifi disconnect`	Disconnect from WiFi
`zbot wifi status`	Show saved SSID

Conversation

Command	Description
`zbot chat`	Enter interactive chat mode (`/exit` to quit)
`zbot history`	Print in-RAM conversation history
`zbot summary`	Show the NVS-persisted session summary
`zbot clear`	Clear RAM history (keeps NVS summary)
`zbot wipe`	Wipe all history and NVS summary

Telegram Bot

Command	Description
`zbot telegram token <token>`	Set Telegram Bot token (saved to flash)
`zbot telegram start`	Start long-poll thread
`zbot telegram stop`	Stop long-poll thread
`zbot telegram status`	Show token and polling state

Skills & Tools

Command	Description
`zbot skill list`	List all registered skills with descriptions
`zbot skill run <name> [arg]`	Run a skill directly from the shell
`zbot tools`	List all LLM-visible tools

Built-in Skills

Skills are registered at boot via SKILL_DEFINE / SYS_INIT and dispatched by tool_exec.

`gpio` — GPIO operations

Action	Args	Description
`read`	`pin`: `led0`/`led1`/`button0`	Read GPIO pin level
`write`	`pin`: `led0`/`led1`, `value`: `0`/`1`	Set GPIO output level
`blink`	`count`: 1–20 (default 3)	Blink LED0 N times at 300ms intervals
`sos`	—	Transmit SOS morse code on LED0

hljs language-css

zbot:~$ Turn on LED0
# LLM calls: tool_exec({"tool":"gpio","args":{"action":"write","pin":"led0","value":1}})

zbot:~$ Blink 5 times
# LLM calls: tool_exec({"tool":"gpio","args":{"action":"blink","count":5}})

`system` — System information

Action	Description
`board_info`	Board name, RTOS, firmware version
`uptime`	Device uptime in ms and seconds
`heap_info`	Heap free / allocated / peak bytes
`status`	Combined report: board + uptime + heap

hljs language-vbnet

zbot:~$ What's the system status?
# LLM calls: tool_exec({"tool":"system","args":{"action":"status"}})

Shell shortcut:

hljs language-json

uart:~$ zbot skill run system '{"action":"status"}'
uart:~$ zbot skill run gpio '{"action":"blink","count":3}'

Extending zbot

Adding a New Skill

Create src/skills/<name>/SKILL.md (optional — for skills with documentation)
Create src/skills/<name>/SKILL.c:

hljs language-c

#include "skill.h"

static const char my_skill_md[] = {
#include "skills/<name>/SKILL.md.inc"
    0x00
};

static int handler(const char *arg, char *result, size_t res_len)
{
    snprintf(result, res_len, "{\"status\":\"ok\"}");
    return 0;
}

SKILL_DEFINE(my_skill, "my_skill", "One-line description",
             my_skill_md, sizeof(my_skill_md) - 1, handler);

Create src/skills/<name>/CMakeLists.txt:

hljs language-cmake

target_sources(app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/SKILL.c)

generate_inc_file_for_target(
    app
    ${CMAKE_CURRENT_SOURCE_DIR}/SKILL.md
    ${gen_dir}/skills/<name>/SKILL.md.inc
)

The skill is immediately available to the LLM via tool_exec({"tool":"<name>","args":{...}}).

Customising the System Prompt

Edit src/AGENT.md.in — it is embedded into the firmware at build time via generate_inc_file_for_target. No code changes required.

Project Structure

hljs language-bash

zbot/
├── CMakeLists.txt
├── prj.conf
├── boards/
│   ├── nrf7002dk_nrf5340_cpuapp.conf
│   └── native_sim.conf
├── sysbuild/
│   └── nrf7002dk_nrf5340_cpuapp.conf
└── src/
    ├── AGENT.md.in                 # System prompt (embedded at build time)
    ├── main.c
    ├── agent.h/c                   # ReAct loop
    ├── memory.h/c                  # Conversation history + NVS summary
    ├── llm_client.h/c              # HTTPS LLM client
    ├── config.h/c                  # Runtime config + NVS persistence
    ├── tools.h/c                   # LLM tool registry framework
    ├── json_util.h/c               # JSON helpers
    ├── shell_cmd.c                 # zbot shell commands
    ├── telegram.h/c                # Telegram Bot integration
    ├── certs/openrouter/           # TLS CA certificate
    ├── tools/
    │   ├── tool_exec/              # LLM tool: dispatches to skill_run()
    │   │   └── TOOL.c
    │   └── read_skill/             # LLM tool: returns skill Markdown docs
    │       └── TOOL.c
    └── skills/
        ├── skill.h/c               # Skill registry framework
        ├── gpio/                   # GPIO: read, write, blink, sos
        │   ├── SKILL.c
        │   └── SKILL.md
        └── system/                 # System: board_info, uptime, heap, status
            ├── SKILL.c
            └── SKILL.md

Security Notes

API key is saved to NVS flash. Use zbot key_delete to remove it.
Telegram token is saved to NVS flash. Use zbot config_reset to wipe it.
WiFi passphrase is stored in flash as plain text. Acceptable for dev boards.
NVS summary is stored as plain text. Avoid sensitive information in conversations.

⭐ Star History

⭐ If you like this project, give it a star!

🦞 zbot

🎬 Demo

Supported boards: nRF7002-DK (nRF5340 + nRF7002 WiFi), native_sim (Linux host) RTOS: Zephyr latest License: Apache-2.0

Architecture

hljs language-scss

┌──────────────────────────────────────────────────────┐
│                    zbot Agent                        │
│                                                      │
│  ┌──────────┐  ┌──────────┐  ┌──────────────────┐    │
│  │  Config  │  │  Memory  │  │   LLM Client     │    │
│  │ endpoint │  │ slab pool│  │  HTTPS → OpenAI  │    │
│  │ model    │  │ + NVS    │  │  compatible API  │    │
│  │ api key  │  │ summary  │  │                  │    │
│  └──────────┘  └──────────┘  └──────────────────┘    │
│                                                      │
│  ┌──────────────────────┐  ┌──────────────────────┐  │
│  │  LLM-visible Tools   │  │       Skills         │  │
│  │  (src/tools/)        │  │  (src/skills/)       │  │
│  │                      │  │                      │  │
│  │  tool_exec ──────────┼─►│  gpio  (read/write/  │  │
│  │    └─ skill_run()    │  │         blink/sos)   │  │
│  │                      │  │  system(board/uptime/│  │
│  │  read_skill ─────────┼─►│         heap/status) │  │
│  │    └─ skill_read_    │  │                      │  │
│  │       content()      │  │  (add more in        │  │
│  └──────────────────────┘  │   src/skills/<name>/)│  │
│                            └──────────────────────┘  │
│  ┌────────────────────────────────────────────────┐  │
│  │  Shell Commands  (zbot key / chat / skill ...) │  │
│  └────────────────────────────────────────────────┘  │
│                                                      │
│  ┌──────────┐                                        │
│  │ Telegram │  Long-poll thread → agent → sendMessage│
│  │   Bot    │                                        │
│  └──────────┘                                        │
└──────────────────────────────────────────────────────┘

Modules

Module	File	Purpose
Config	`config.h/c`	LLM endpoint, model, API key + WiFi credentials (NVS persistence)
Memory	`memory.h/c`	k_mem_slab conversation history + NVS rolling summary
LLM Client	`llm_client.h/c`	HTTPS POST to OpenAI-compatible Chat Completions API
Tools	`tools.h/c` + `src/tools/`	LLM-visible tool registry; each tool in its own directory, self-registers via `SYS_INIT`
Skills	`skills/skill.h/c` + `src/skills/`	Skill registry; each skill in its own directory, self-registers via `SYS_INIT`
Agent	`agent.h/c` + `src/AGENT.md`	ReAct loop; system prompt loaded from `AGENT.md` at build time
Telegram	`telegram.h/c`	Telegram Bot long-poll thread; forwards messages to agent and replies
JSON Util	`json_util.h/c`	Shared `json_get_str()` and `json_escape()`
Shell	`shell_cmd.c`	All `zbot` shell subcommands

Tool & Skill Design

The LLM sees exactly two tools:

LLM Tool	What it does
`tool_exec`	Dispatches to any registered skill by name — all hardware/system operations go here
`read_skill`	Returns the full Markdown documentation of a skill on demand

Skills are the execution units. They live in src/skills/<name>/ and self-register at boot via SYS_INIT. Each skill has:

SKILL.c — handler implementation, registered with SKILL_DEFINE
SKILL.md (optional) — Markdown documentation embedded at build time via generate_inc_file_for_target

The LLM receives only name + description for each skill per request. Full docs are fetched on demand via read_skill.

Hardware primitives (GPIO, uptime, heap) are themselves skills — the same mechanism, just without Markdown docs.

ReAct Loop

hljs language-sql

user input
    │
    ▼
build messages JSON  ←────────────────────────────────────────────────┐
    │                                                                 │
    ▼                                                                 │
LLM API call (tool_exec + read_skill exposed)                         │
    │                                                                 │
    ├── finish_reason: tool_call ──► tools_execute(name, args)        │
    │                                    └─ skill_run(name, args) ───►│
    │
    └── finish_reason: stop ──► return answer to user
                                        │
                                        ▼
                                request summary ──► NVS

Max iterations per turn: 10

Conversation Memory

History uses a 10-node static pool (k_mem_slab) backed by a sys_slist_t linked list ordered oldest → newest.

When the pool is full on memory_add_turn():

Compress — the oldest nodes are summarised by the LLM; those nodes are freed back to the slab.
Evict (fallback) — the oldest node is recycled directly.

After compression, the rolling summary is written to NVS and injected as prior context on the next boot.

Settings layout:

Key	Type	Notes
`zbot/summary`	`char[768]`	Conversation summary
`zbot/apikey`	`char[256]`	Set by `zbot key`
`zbot/host`	`char[128]`	LLM endpoint hostname
`zbot/path`	`char[128]`	LLM API path
`zbot/model`	`char[128]`	Model name
`zbot/provider_id`	`char[64]`	`X-Model-Provider-Id` header
`zbot/use_tls`	`uint8_t`	TLS enabled flag
`zbot/port`	`uint16_t`	TCP port
`zbot/tg_token`	`char[128]`	Telegram Bot token
`wifi/...`	—	Managed by Zephyr `wifi_credentials` subsystem

Prerequisites

Set up a Zephyr development environment following the official guide: https://docs.zephyrproject.org/latest/develop/getting_started/index.html

Quick Start

1. Build & Flash

nRF7002-DK (physical hardware with WiFi):

hljs language-bash

west build -b nrf7002dk/nrf5340/cpuapp zbot
west flash

native_sim (Linux host simulation, no WiFi):

hljs language-bash

west build -b native_sim zbot
./build/zephyr/zephyr.exe

2. Connect Serial

For nRF7002-DK:

hljs language-bash

minicom -D /dev/ttyACM0 -b 115200

For native_sim, the shell is on the terminal where you launched zephyr.exe.

3. Connect to WiFi (nRF7002-DK only)

hljs language-arduino

uart:~$ zbot wifi connect <SSID> <password>

Credentials are saved to flash and auto-connect on reboot.

native_sim: No WiFi configuration needed — the host OS provides the network stack.

4. Set API Key

Default Provider (OpenRouter) Get a free API key from: https://openrouter.ai/settings/keys

hljs language-vbnet

uart:~$ zbot key sk-...

The key is saved to NVS flash and restored on every reboot.

5. (Optional) Configure Endpoint

OpenAI:

hljs language-vbnet

uart:~$ zbot host api.openai.com
uart:~$ zbot path /v1/chat/completions
uart:~$ zbot model gpt-4o-mini
uart:~$ zbot key sk-...

DeepSeek:

hljs language-vbnet

uart:~$ zbot host api.deepseek.com
uart:~$ zbot path /chat/completions
uart:~$ zbot model deepseek-chat
uart:~$ zbot key sk-...

Local model (e.g. Ollama):

hljs language-vbnet

uart:~$ zbot host 192.168.1.100
uart:~$ zbot tls off 11434

6. (Optional) Configure Telegram Bot

Create a bot via @BotFather on Telegram to obtain a token.

hljs language-ruby

uart:~$ zbot telegram token 1234567890:AAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
uart:~$ zbot telegram start

The token is saved to NVS flash. Polling starts automatically on the next reboot if a token is stored.

7. Chat

hljs language-vbnet

uart:~$ zbot chat
Entering interactive chat mode. Type /exit to quit.
zbot:~$ Hello! What can you do?
Thinking...

zbot: Hi! I'm zbot ...

zbot:~$ Turn on LED0
Thinking...

zbot: Done — LED0 is now on.

zbot:~$ /exit
Leaving chat mode.
uart:~$

Shell Commands

Configuration

Command	Description
`zbot key <key>`	Set API key (saved to flash)
`zbot key_delete`	Delete API key from flash
`zbot config_reset`	Reset all config to defaults and wipe from flash
`zbot host <hostname>`	Set LLM endpoint host
`zbot path <path>`	Set LLM API path
`zbot model <name>`	Set model name
`zbot provider <id>`	Set `X-Model-Provider-Id` header
`zbot tls <on\|off> [port]`	Enable/disable TLS and set port
`zbot status`	Show current config and agent state

WiFi (nRF7002-DK only)

Command	Description
`zbot wifi connect <ssid> [pass]`	Connect to WiFi and save credentials
`zbot wifi disconnect`	Disconnect from WiFi
`zbot wifi status`	Show saved SSID

Conversation

Command	Description
`zbot chat`	Enter interactive chat mode (`/exit` to quit)
`zbot history`	Print in-RAM conversation history
`zbot summary`	Show the NVS-persisted session summary
`zbot clear`	Clear RAM history (keeps NVS summary)
`zbot wipe`	Wipe all history and NVS summary

Telegram Bot

Command	Description
`zbot telegram token <token>`	Set Telegram Bot token (saved to flash)
`zbot telegram start`	Start long-poll thread
`zbot telegram stop`	Stop long-poll thread
`zbot telegram status`	Show token and polling state

Skills & Tools

Command	Description
`zbot skill list`	List all registered skills with descriptions
`zbot skill run <name> [arg]`	Run a skill directly from the shell
`zbot tools`	List all LLM-visible tools

Built-in Skills

Skills are registered at boot via SKILL_DEFINE / SYS_INIT and dispatched by tool_exec.

`gpio` — GPIO operations

Action	Args	Description
`read`	`pin`: `led0`/`led1`/`button0`	Read GPIO pin level
`write`	`pin`: `led0`/`led1`, `value`: `0`/`1`	Set GPIO output level
`blink`	`count`: 1–20 (default 3)	Blink LED0 N times at 300ms intervals
`sos`	—	Transmit SOS morse code on LED0

hljs language-css

zbot:~$ Turn on LED0
# LLM calls: tool_exec({"tool":"gpio","args":{"action":"write","pin":"led0","value":1}})

zbot:~$ Blink 5 times
# LLM calls: tool_exec({"tool":"gpio","args":{"action":"blink","count":5}})

`system` — System information

Action	Description
`board_info`	Board name, RTOS, firmware version
`uptime`	Device uptime in ms and seconds
`heap_info`	Heap free / allocated / peak bytes
`status`	Combined report: board + uptime + heap

hljs language-vbnet

zbot:~$ What's the system status?
# LLM calls: tool_exec({"tool":"system","args":{"action":"status"}})

Shell shortcut:

hljs language-json

uart:~$ zbot skill run system '{"action":"status"}'
uart:~$ zbot skill run gpio '{"action":"blink","count":3}'

Extending zbot

Adding a New Skill

Create src/skills/<name>/SKILL.md (optional — for skills with documentation)
Create src/skills/<name>/SKILL.c:

hljs language-c

#include "skill.h"

static const char my_skill_md[] = {
#include "skills/<name>/SKILL.md.inc"
    0x00
};

static int handler(const char *arg, char *result, size_t res_len)
{
    snprintf(result, res_len, "{\"status\":\"ok\"}");
    return 0;
}

SKILL_DEFINE(my_skill, "my_skill", "One-line description",
             my_skill_md, sizeof(my_skill_md) - 1, handler);

Create src/skills/<name>/CMakeLists.txt:

hljs language-cmake

target_sources(app PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/SKILL.c)

generate_inc_file_for_target(
    app
    ${CMAKE_CURRENT_SOURCE_DIR}/SKILL.md
    ${gen_dir}/skills/<name>/SKILL.md.inc
)

The skill is immediately available to the LLM via tool_exec({"tool":"<name>","args":{...}}).

Customising the System Prompt

Edit src/AGENT.md.in — it is embedded into the firmware at build time via generate_inc_file_for_target. No code changes required.

Project Structure

hljs language-bash

zbot/
├── CMakeLists.txt
├── prj.conf
├── boards/
│   ├── nrf7002dk_nrf5340_cpuapp.conf
│   └── native_sim.conf
├── sysbuild/
│   └── nrf7002dk_nrf5340_cpuapp.conf
└── src/
    ├── AGENT.md.in                 # System prompt (embedded at build time)
    ├── main.c
    ├── agent.h/c                   # ReAct loop
    ├── memory.h/c                  # Conversation history + NVS summary
    ├── llm_client.h/c              # HTTPS LLM client
    ├── config.h/c                  # Runtime config + NVS persistence
    ├── tools.h/c                   # LLM tool registry framework
    ├── json_util.h/c               # JSON helpers
    ├── shell_cmd.c                 # zbot shell commands
    ├── telegram.h/c                # Telegram Bot integration
    ├── certs/openrouter/           # TLS CA certificate
    ├── tools/
    │   ├── tool_exec/              # LLM tool: dispatches to skill_run()
    │   │   └── TOOL.c
    │   └── read_skill/             # LLM tool: returns skill Markdown docs
    │       └── TOOL.c
    └── skills/
        ├── skill.h/c               # Skill registry framework
        ├── gpio/                   # GPIO: read, write, blink, sos
        │   ├── SKILL.c
        │   └── SKILL.md
        └── system/                 # System: board_info, uptime, heap, status
            ├── SKILL.c
            └── SKILL.md

Security Notes

API key is saved to NVS flash. Use zbot key_delete to remove it.
Telegram token is saved to NVS flash. Use zbot config_reset to wipe it.
WiFi passphrase is stored in flash as plain text. Acceptable for dev boards.
NVS summary is stored as plain text. Avoid sensitive information in conversations.

⭐ Star History

⭐ If you like this project, give it a star!

zbot

🦞 zbot

🎬 Demo

Architecture

Modules

Tool & Skill Design

ReAct Loop

Conversation Memory

Prerequisites

Quick Start

1. Build & Flash

2. Connect Serial

3. Connect to WiFi (nRF7002-DK only)

4. Set API Key

5. (Optional) Configure Endpoint

6. (Optional) Configure Telegram Bot

7. Chat

Shell Commands

Configuration

WiFi (nRF7002-DK only)

Conversation

Telegram Bot

Skills & Tools

Built-in Skills

gpio — GPIO operations

system — System information

Extending zbot

Adding a New Skill

Customising the System Prompt

Project Structure

Security Notes

⭐ Star History

Similar Packages

zbot

🦞 zbot

🎬 Demo

Architecture

Modules

Tool & Skill Design

ReAct Loop

Conversation Memory

Prerequisites

Quick Start

1. Build & Flash

2. Connect Serial

3. Connect to WiFi (nRF7002-DK only)

4. Set API Key

5. (Optional) Configure Endpoint

6. (Optional) Configure Telegram Bot

7. Chat

Shell Commands

Configuration

WiFi (nRF7002-DK only)

Conversation

Telegram Bot

Skills & Tools

Built-in Skills

gpio — GPIO operations

system — System information

Extending zbot

Adding a New Skill

Customising the System Prompt

Project Structure

Security Notes

⭐ Star History

Similar Packages

`gpio` — GPIO operations

`system` — System information

`gpio` — GPIO operations

`system` — System information