skills.rest
JasonYANG170
JasonYANG170COMMUNITY
Explore all skills by this author →
WebsiteGitHub

esp-claw-skill

Guides building, extending, and debugging ESP-Claw edge-agent firmware on ESP32 chips.

28|3|Updated Jun 24, 2026
Search Tags:#agent framework#firmware#embedded#lua#esp32#esp-idf#event router
One-click install
npx skills add https://github.com/JasonYANG170/esp-dev-skill --skill esp-claw-skill-jasonyang170
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: esp-claw-skill
Source: https://github.com/JasonYANG170/esp-dev-skill/tree/main/repos/esp-claw
Command: npx skills add https://github.com/JasonYANG170/esp-dev-skill --skill esp-claw-skill-jasonyang170

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing firmware for Espressif's ESP-Claw edge-agent framework requires deep knowledge of its capability system, Lua module registration order, event-router rules, NVS configuration precedence, and board adaptation workflow, and mistakes in any of these cause silent runtime failures that are hard to diagnose. ## Core Features & Use Cases - Scenario Recipes: Step-by-step guides for building and flashing edge_agent with ESP-IDF v5.5.4 and Board Manager, adapting new boards, implementing cap_* capabilities, writing Lua modules, authoring router_rules.json automation, scheduling tasks, and integrating IM platforms end to end. - Grounded API and Config Reference: Real C structs and function signatures for claw_cap, claw_core, claw_event_router, claw_memory, and cap_mcp_server, plus Kconfig symbols and NVS runtime fields, all sourced from the actual esp-claw repository. - Pitfall Prevention: 15 critical wrong-versus-correct patterns covering Lua registration locking, path layering with {CUR_SKILL_DIR}, asynchronous out_message routing, and NVS-over-menuconfig precedence. - Use Case: A developer wants Telegram messages to reach the on-device LLM agent and receive replies; the Skill walks them through credential setup, the seven real IM router rules, and the required out_message-to-send_message loop, then validates with console commands like auto last. ## Quick Start Ask the agent to help you build and flash the ESP-Claw edge_agent firmware for your ESP32-S3 board using idf.py bmgr, then configure the LLM credentials so the ask command responds.

Frequently Asked Questions about esp-claw-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and flash ESP-Claw edge_agent firmware?▼

Install ESP-IDF v5.5.4 and esp-bmgr-assist, clone the esp-claw repo, then run idf.py bmgr -c ./boards -b <board> inside application/edge_agent to auto-select the chip target. Follow with idf.py build and idf.py flash monitor; do not use idf.py set-target directly.

How do I add a new capability to ESP-Claw?▼

Create a component under components/claw_capabilities/cap_<name> with a claw_cap_descriptor_t and claw_cap_group_t, expose only a cap_<name>_register_group function, and register it in app_capabilities.c. Add an APP_CLAW_CAP_* Kconfig option and ensure the tool id is globally unique with a valid JSON input schema.

Why does my ESP-Claw Lua module fail to register?▼

Lua module registration locks after cap_lua_register_group is called, so any lua_module_*_register call made afterward returns ESP_ERR_INVALID_STATE. Register all modules in app_lua_modules.c before cap_lua_register_group, and confirm the corresponding APP_CLAW_LUA_* Kconfig is enabled for your chip.

Why is the ESP-Claw agent not responding to IM messages?▼

The claw_core agent only starts when llm_api_key, llm_model, and llm_backend_type are all set, and run_agent replies return asynchronously as out_message events. You need a router rule matching source_cap claw_core with event_type out_message that calls send_message back to the IM channel.

Does changing menuconfig defaults take effect on ESP-Claw?▼

Not always, because runtime values follow NVS-first precedence: once a field like Wi-Fi or LLM credentials is saved via the web UI, NVS overrides the menuconfig default. Clear the relevant NVS keys or rewrite values through the web configuration page to change them.

Which chips and frameworks does ESP-Claw support?▼

ESP-Claw targets ESP32-S3, ESP32-P4, ESP32-C5, and ESP32-S31 boards managed through ESP Board Manager definitions under application/edge_agent/boards. It is built with ESP-IDF v5.5.4 and does not apply to generic ESP-IDF development unrelated to the agent framework.

Related Skills

Explore More Software Engineering Skills→
pjcaupjcau
2

firmware-build

Compile and flash ESP32-S3 firmware using ESP-IDF via Docker or Makefile.

Community
Intermediate
edwifiguyedwifiguy
1

cli-anything-rms

Manage Teltonika RMS devices via a CLI for the REST API.

Community
Intermediate
ynyxxxynyxxx
1

esp32-esp-idf

Guide ESP32 development using ESP-IDF, FreeRTOS, and CMake.

Community
Advanced
mirkoserticmirkosertic
5

firmware-core

Orchestrate Megahub ESP32 firmware development and troubleshooting for PlatformIO builds.

Community
Advanced