evolution-steward.default

Classify agent failure root causes and delegate revision creation to the agent factory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill decides whether to evolve a flagged agent and delegates to the agent factory for revision creation, reducing manual triage and expediting remediation.

Core Features & Use Cases

  • Classifies root causes of agent failures (instruction-level, code-level, systemic) and routes improvements to agent-factory.default.
  • Orchestrates evaluation using evidence from the memory curator and maintains safety gates.
  • Use Case: When an agent exhibits recurring failures, Evolution Steward decides if it should be evolved and triggers a factory-driven revision.

Quick Start

Invoke evolution-steward.default with a flagged agent and evidence to determine whether to evolve and delegate revision creation to the agent factory.

Frequently Asked Questions about evolution-steward.default

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

FAQPage Schema
How do I automate agent evolution decisions when an autonomous agent shows persistent failures?

Agent evolution decisions classify root causes of persistent failures into instruction-level, code-level, or systemic categories. It evaluates agent state and evidence to determine if a revision is necessary, then outputs an evolved flag, new revision ID, and detailed rationale.

How do I classify root causes of recurring agent runtime failures before triggering a revision?

Root causes of recurring agent failures are classified by reading agent state and evidence, categorizing them as instruction-level, code-level, or systemic. This classification determines whether to trigger an agent revision and delegate the task to the agent factory.

Can I orchestrate agent evaluation and revision creation without manual triage in the Autonoetic runtime?

Yes, orchestrating agent evaluation and revision creation without manual triage is possible in the Autonoetic runtime. It uses evidence from the memory curator, maintains safety gates, and delegates revision creation directly to the agent factory.

What's the best way to route agent improvements after evaluating persistent runtime failures?

The best way to route agent improvements after evaluating persistent failures is to delegate the revision task to the agent factory. The evaluation outputs a decision with an evolved flag and new revision ID to trigger the factory-driven revision.

When should I not use automated agent evolution for runtime failure remediation?

Automated agent evolution should not be used when evidence from the memory curator is insufficient or safety gates are violated. The process requires valid agent state and evidence to accurately classify root causes and decide whether to trigger a factory revision.