theta-wave

Scan multi-agent systems and plan evidence-based improvements via orchestrator negotiation.

88|108|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/grandamenium/cortextos --skill theta-wave-grandamenium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: theta-wave
Source: https://github.com/grandamenium/cortextos/tree/main/templates/analyst/.claude/skills/theta-wave
Command: npx skills add https://github.com/grandamenium/cortextos --skill theta-wave-grandamenium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves system stagnation by turning overnight evaluations and targeted experiments into measurable, system-level improvements.

Core Features & Use Cases

  • System-wide deep scan: Inspects agent heartbeats, tasks, experiment results, per-agent contexts, goals, memories, and logs to find bottlenecks and failure patterns.
  • Compound effectiveness scoring: Assigns a 1–10 system_effectiveness score each cycle with a required justification tied to observed data and historical trajectory.
  • Evidence-driven orchestrator conversation: Runs a real, non-scripted negotiation with the orchestrator to challenge assumptions, require evidence, and converge on actionable changes.
  • Adaptive cycle management: Creates, modifies, pauses, or removes agent research cycles and crons based on keep/discard outcomes and detected staleness, convergence, or underperformance.

Quick Start

Ask your system to run the theta-wave deep improvement cycle to scan experiments, research evidence, and propose the next system actions.

Frequently Asked Questions about theta-wave

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

FAQPage Schema
How do I evaluate and improve a multi-agent system to prevent research stagnation?

Evaluating a multi-agent system to prevent stagnation requires running scheduled deep-scan cycles that inspect agent heartbeats, tasks, and experiment results. The system identifies bottlenecks and proposes evidence-based architectural or workflow changes to drive measurable improvements.

What is a system effectiveness score in multi-agent orchestration?

A system effectiveness score in multi-agent orchestration is a qualitative 1–10 rating assigned per evaluation cycle. It is justified by observed data and historical trajectories, providing a compound metric to track system-level research performance over time.

How do I detect stale or converged research cycles in an automated agent system?

Detecting stale or converged research cycles involves running system-wide scans that review prior experiments and agent contexts. The evaluation identifies underperformance or convergence patterns, enabling adaptive cycle management to pause, modify, or remove redundant agent crons.

Can I automate orchestrator decisions using evidence from agent experiment logs?

Automating orchestrator decisions using agent experiment logs involves running a real, non-scripted negotiation with the orchestrator. The process challenges assumptions, requires evidence from logged cycle actions, and converges on actionable system modifications.

What is the best way to manage adaptive research cycles for autonomous agents?

Managing adaptive research cycles for autonomous agents requires an evaluation layer that creates, modifies, or removes cycles based on keep/discard outcomes. It detects staleness and underperformance to inform orchestrator decisions across architecture and metrics.

Does multi-agent system monitoring work without a project bus for logging actions?

Multi-agent system monitoring requires a project bus to log cycle actions and command execution. Without logging infrastructure, the deep-scan evaluation cannot review prior experiments, track historical trajectories, or inform orchestrator decisions effectively.