evolution-orchestrator.default

Coordinate evolution pipelines by analyzing sessions and surfacing admin proposals.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mandubian/autonoetic --skill evolution-orchestrator-default
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-orchestrator.default
Source: https://github.com/mandubian/autonoetic/tree/main/agents/evolution/evolution-orchestrator.default
Command: npx skills add https://github.com/mandubian/autonoetic --skill evolution-orchestrator-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the end-to-end evolution pipeline by analyzing agent sessions, spawning memory-curation prompts, and surfacing admin proposals for systemic improvements.

Core Features & Use Cases

  • Orchestrates cross-session analysis to identify evolution opportunities and governance needs.
  • Triggers memory-curator and evolution-steward workflows, and surfaces admin proposals for systemic gaps.

Quick Start

Configure and run the 4-hour evolution cycle to analyze sessions and generate admin proposals.

Frequently Asked Questions about evolution-orchestrator.default

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

FAQPage Schema
How do I orchestrate cron-driven evolution for multi-agent systems?

You configure and run a 4-hour evolution cycle that analyzes sessions, triggers memory-curation prompts, and generates governance proposals with safety checks and role-based capabilities.

What is evolution orchestration for agent governance?

It applies deterministic control over scheduling, memory-curation triggers, and governance proposals, ensuring safety checks and role-based capabilities across evolved agent sessions.

How do I automate admin proposals for multi-agent evolution pipelines?

The orchestrator analyzes agent sessions on a scheduled cycle, applies safety checks, and surfaces structured admin proposals based on identified evolution opportunities and governance needs.

Does cron-driven evolution orchestration work with role-based governance?

It implements role-based capabilities within its governance proposals, ensuring that memory-curation triggers and evolution-steward workflows operate within defined safety constraints across sessions.

Can I schedule memory-curation triggers across agent sessions?

The 4-hour evolution cycle analyzes sessions and triggers memory-curator workflows, ensuring memory-curation prompts are generated at scheduled intervals with governance safety checks applied.

When should I use a dedicated evolution orchestrator instead of manual agent governance?

Use it when systemic gaps require structured admin proposals, memory-curation triggers, and evolution-steward workflows operating with safety checks and role-based capabilities across multiple sessions.