Reppo Orchestrator

Route daily datanet agent RUN/SKIP decisions and emit a reppo-plan block.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill reppo-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Reppo Orchestrator
Source: https://github.com/anajuliabit/aeon/tree/main/skills/reppo-orchestrator
Command: npx skills add https://github.com/anajuliabit/aeon --skill reppo-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reppo Orchestrator prevents wasting time and on-chain effort by deciding which datanet agents should run versus skip, using the latest cached validity and rubric assignments.

Core Features & Use Cases

  • Daily RUN/SKIP routing: Evaluates each datanet rubric against cached validity to safely decide RUN or SKIP.
  • Unassigned datanet discovery: Detects datanets present in the live catalog that do not yet have a rubric/agent assignment.
  • Strict output handoff contract: Produces a required fenced reppo-plan block that the next chain step parses to avoid accidental zero-activity gating.
  • Run logging for auditability: Appends a daily entry summarizing RUN vs SKIP counts, discoveries, and catalog availability.

Quick Start

Ask an AI operator to run the reppo-orchestrator skill so it generates the required reppo-plan from your datanet rubrics and cached datanet validity state.

Frequently Asked Questions about Reppo Orchestrator

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

FAQPage Schema
How do I automate daily RUN or SKIP decisions for agent swarm workflow scheduling?

Automated workflow scheduling for agent swarms evaluates cached datanet validity against rubric assignments to decide daily RUN or SKIP actions, preventing wasted on-chain effort and ensuring idempotent execution.

What is datanet routing for agent swarms and when do I need it?

Datenet routing directs which agents in a swarm execute tasks based on cached validity. You need it when scheduling daily rubric-defined agent strategies to avoid duplicate runs and safely handle catalog unavailability.

How do I generate a structured execution plan for idempotent agent runs?

To generate an execution plan for idempotent agent runs, read local memory and datanet caches, then emit a correctly shaped fenced reppo-plan block that downstream parsing steps use to gate activities safely.

How do I discover unassigned datanets in a live agent catalog?

Discover unassigned datanets by checking the live catalog for datanets present without a rubric or agent assignment, logging discoveries daily to maintain full visibility over your agent swarm coverage.

What happens to datanet routing when the agent catalog is unavailable?

When the agent catalog is unavailable, datanet routing must handle catalog unavailability safely by reading local memory and datanet caches to still emit a correctly shaped reppo-plan block for downstream parsing.