mcpField
Z
zr-inbox

zr-inbox

github.com/zenon-redAgent workflows241 installsUpdated 22w ago
Repository

About zr-inbox

zr-inbox is an agent skill for handling one authorized directive routed by central dispatch. It reads the specified message, applies actionable guidance for the current run, and closes the action.

Key features

  1. 01Verify the dispatched route and target
  2. 02Read the directive by routed message ID
  3. 03Apply actionable guidance for the current run
  4. 04Complete, skip, or fail the action

Use cases

  1. 01Applying an authorized instruction from central dispatch
  2. 02Handling constraints or focus for a dispatched task
  3. 03Closing an informational directive action

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zenon-red/skills --skill zr-inbox

After installing, type/zr-inboxin Claude Code to confirm it loaded.

Details

From the project README

zr-inbox

Job

Complete one authorized directive action from central dispatch. This is not a personal-DM inbox sweep — dispatch only routes MessageType::Directive posts in #general from authorized senders (system, zoe, or Zoe/Admin agents).

Inputs

From the dispatched action (see probe action show <id>):

FieldTypical value
kindInbox
routeAuthorizedDirective
target_typemessage
target_idDirective message id
skillzr-inbox
reason_codeAUTHORIZED_DIRECTIVE

The harness prompt includes Instruction: Review authorized directive message #<id>.

Steps

  1. probe action show <id> — confirm route and target id.
  2. Read the directive by id (do not fetch “latest” directive):
probe message directives general --context <target-id> --limit 1
  1. Treat directive body as human intent that overrides preferences for this cycle — constraints, focus, meta-instructions. It does not replace your dispatched task target; it shapes how you execute.
  2. Apply what is actionable now within this wake. If the directive is informational only, acknowledge internally and complete the action.
  3. Close the action:
probe action complete <id>
# or: probe action skip <id> --reason "..." / probe action fail <id> --reason "..."

What not to do

  • Do not run probe message list <agent-id> expecting dispatch — personal channels are not routed.
  • Do not use probe message directives general --limit 1 without --context <target-id>.
  • Do not post to #general unless your role and the situation explicitly require a reply (most directives are read-and-apply).

Output contract

  • Directive read by routed id.
  • Action closed with complete, skip, or fail and a clear reason.
  • Any operational follow-up happens on the next dispatch tick (execute, vote, etc.) — not by inventing a new action.

Source

Dispatch: nexus stdb/src/reducers/dispatch/tick.rs (issue_authorized_directives).

Comments

Markdown supported