evolve-status

Read evolution_state.json and report iteration, phase, and convergence status.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/GQAdonis/turboquant-rs --skill evolve-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve-status
Source: https://github.com/GQAdonis/turboquant-rs/tree/main/.opencode/skills/iterative-evolver/skills/evolve-status
Command: npx skills add https://github.com/GQAdonis/turboquant-rs --skill evolve-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and communicate the current state of an evolution cycle, including iteration counts, goal alignment, phase completion, and convergence status.

Core Features & Use Cases

  • Load evolution_state.json if it exists and display a concise status summary.
  • Provide visibility into iteration progress, completed phases, and current convergence signals for decision-making.
  • Use Case: Before advancing to the next evolution step, quickly verify that the current cycle aligns with goals and milestones.

Quick Start

Load evolution_state.json if it exists and display the current status.

Frequently Asked Questions about evolve-status

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

FAQPage Schema
How do I track evolution progress and convergence status during an experiment?

Track evolution progress by loading an evolution_state.json file, which generates a concise status summary of iteration counts, goal alignment, phase completion, and convergence signals for decision-making.

What is the best way to check iteration status before advancing an evolution cycle?

Checking iteration status involves reading the current evolution_state.json to verify phase completion and goal alignment. This ensures the current cycle meets milestones before proceeding to the next evolution step.

Can I monitor goal alignment and phase completion for simulation runs without manual inspection?

Monitoring goal alignment and phase completion is automated by reading the evolution_state.json file, which prints a concise summary of convergence signals and iteration progress without manual inspection.

Does the evolution status tracker work if evolution_state.json is not present?

The evolution status tracker operates by loading evolution_state.json if it exists. If the file is not present, it cannot display the iteration progress, convergence status, or phase completion summary.

Why do I need to verify convergence signals before moving to the next evolution step?

Verifying convergence signals is needed to ensure the current evolution cycle aligns with predefined goals and milestones. Reading the status summary provides visibility into whether the iteration is ready to advance.

What information is included in an evolution cycle status summary?

An evolution cycle status summary includes iteration counts, goal alignment metrics, completed phases, and current convergence signals, providing full visibility into the experiment's overall progress.