skills.rest
espressif
espressifOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cap_router_mgr

Manage IoT event router automation rules via capability calls.

2.0k|410|Updated Apr 17, 2026
Search Tags:#command matching#event routing#router rules#IoT automation#capability calls#rule_json#startup triggers
One-click install
npx skills add https://github.com/espressif/esp-claw --skill cap-router-mgr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cap_router_mgr
Source: https://github.com/espressif/esp-claw/tree/main/components/claw_capabilities/cap_router_mgr/skills/cap_router_mgr
Command: npx skills add https://github.com/espressif/esp-claw --skill cap-router-mgr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you inspect and change how the device routes incoming events to actions, without manually editing rule files, reducing configuration mistakes and speeding up iteration.

Core Features & Use Cases

  • Rule CRUD via capabilities: List, fetch, add, update, and delete router rules through cap_router_mgr capability calls.
  • Controlled reload semantics: Reload router rules only when you explicitly need disk reload behavior.
  • Strict rule_json correctness: Enforces that rule_json is a JSON string with required fields like id, match, and actions, and that match.event_type is correctly placed.
  • Common automation patterns: Apply rules that trigger on events such as startup triggers and message text commands (including prefix-style command matching), then run agent/scripts, send messages, emit events, or drop messages.

Quick Start

Ask the assistant to list router rules, then create or update a single rule id using a complete rule_json string, and finally verify it by calling get_router_rule.

Frequently Asked Questions about cap_router_mgr

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

FAQPage Schema
How do I add and update IoT event router rules without manually editing files?▼

You can add and update IoT event router rules by using capability calls to submit a strict JSON string containing the required fields: id, match, and actions. After submitting the rule, verify the change by fetching it.

What is the correct structure for a rule_json string when configuring router automation?▼

A valid rule_json string requires the fields id, match, and actions at the top level. The match object must contain the event_type field correctly placed to ensure the router evaluates the trigger conditions properly.

How do I trigger actions on startup events or match message text commands?▼

You trigger actions on startup events or message text commands by configuring the match.event_type field in your rule_json. For commands, use prefix-style command matching to execute agents, send messages, or drop messages.

When should I reload router rules instead of just updating them?▼

You should reload router rules only when you explicitly need disk reload behavior. Standard updates apply changes dynamically, but a full reload ensures the router reads the persisted rule files from disk fresh.

Why are my router rule changes not taking effect after updating the JSON string?▼

Router rule changes fail if the rule_json string is malformed or if match.event_type is incorrectly nested. Always validate the JSON structure and verify the applied configuration by calling get_router_rule to inspect the active rule.

Related Skills

Explore More Software Engineering Skills→
AstorYHAstorYH
15

mongodb-document-upsert

Performs upsert operations on MongoDB collections with query and update objects.

Community
Intermediate
ANcpLuaANcpLua
5

verification-before-completion

Enforce verification steps before claiming completion of code changes.

Community
Intermediate
viktorbezdekviktorbezdek
10

workflow-automation

Automate CI/CD pipelines, git worktrees, and release workflows.

Community
Advanced
luongldptitluongldptit

plankton-code-quality

Enforce linting and formatting on every file edit via Claude Code hooks.

Community
Advanced