cap_router_mgr

Router Rule Management

Use this skill to inspect and modify event router rules through the direct callable capabilities in cap_router_mgr.

When to use

• The task is to list, inspect, add, update, delete, or reload router rules.
• The task is to change router behavior by capability calls, not by editing rule files directly.
• The task requires deciding between add_router_rule and update_router_rule for one rule id.

Operating rules

• Use direct router manager capabilities, not console wrappers.
• Prefer changing exactly one rule per turn.
• Treat rule_json as a JSON string, not an embedded object.
• After add_router_rule or update_router_rule, always call get_router_rule.
• Use reload_router_rules only when the task explicitly requires disk reload semantics.

Capability contract

• list_router_rules Input: {} Output: JSON array of rule objects.
• get_router_rule Input: {"id":"rule_id"} Output: one rule object, or standard error JSON with ok=false.
• add_router_rule Input: {"rule_json":"{\"id\":\"rule_id\",\"match\":{\"event_type\":\"message\"},\"actions\":[{\"type\":\"drop\"}]}"}. Output: {"action":"add_router_rule","ok":true,"id":"rule_id"}. If the error says rule id already exists; use update_router_rule, switch to update_router_rule.
• update_router_rule Input: same shape as add_router_rule. Output: {"action":"update_router_rule","ok":true,"id":"rule_id"}. If the error says rule id not found; use add_router_rule, switch to add_router_rule.
• delete_router_rule Input: {"id":"rule_id"} Output: {"action":"delete_router_rule","ok":true,"id":"rule_id"}
• reload_router_rules Input: {} Output: {"action":"reload_router_rules","ok":true}

Standard workflow

1. Call list_router_rules.
2. Check whether the target id already exists.
3. Build one complete replacement rule object.
4. Call add_router_rule for a new id or update_router_rule for an existing id.
5. Call get_router_rule and verify the stored shape.