Autonomous multi-agent open-ended discovery workflow inspired by the CORAL paper. Use when the task requires sustained search, iterative improvement, multi-agent exploration, shared knowledge accumulation, asynchronous parallel attempts, periodic reflection, or heartbeat-style redirection. Best for research discovery, algorithm design, systems optimization, skill discovery, long-running coding/search tasks, and open-ended problems where a single linear attempt is likely to plateau.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Autonomous multi-agent open-ended discovery workflow inspired by the CORAL paper. Use when the task requires sustained search, iterative improvement, multi-agent exploration, shared knowledge accumulation, asynchronous parallel attempts, periodic reflection, or heartbeat-style redirection. Best for research discovery, algorithm design, systems optimization, skill discovery, long-running coding/search tasks, and open-ended problems where a single linear attempt is likely to plateau.
CORAL-Style Open-Ended Discovery
Overview
Use this skill when the user is not asking for a one-shot answer, but for continued discovery under uncertainty.
The core idea from CORAL is:
run multiple long-horizon exploration threads
accumulate reusable knowledge in shared memory/files
periodically reflect and consolidate
redirect when progress stalls
In OpenClaw, do not try to fully reproduce the CORAL infrastructure unless explicitly asked. Instead, map the paper's principles onto OpenClaw-native primitives:
paper distillation → separate note-writing from quality review
If there is no separate agent, at least run an explicit review pass after generation.
Step 6: Add periodic reflection / consolidation
CORAL's heartbeat mechanism is one of the most reusable ideas.
In OpenClaw, simulate this with:
cron reminders
heartbeat prompts
explicit follow-up messages to spawned sessions
Use three reflection modes:
A. Per-iteration reflection
After each meaningful attempt, record:
what changed
whether it helped
what to try next
B. Periodic consolidation
After several attempts, consolidate into:
stable insights
reusable procedure
skill candidate
shortlist of best strategies
C. Stagnation-triggered redirection
If no progress after several rounds:
stop micro-optimizing
pivot strategy
try a different search region
reduce / expand constraints
Recommended Reflection Prompts
Prompt: attempt reflection
Summarize the last attempt in 5 bullets:
1. What was tried
2. What changed
3. Evidence of improvement or failure
4. What should be reused
5. Best next move
Prompt: consolidation
Review all recent attempts and produce:
- 3 stable insights
- 3 failed patterns to avoid
- 1 reusable workflow
- current best candidate
Prompt: stagnation redirect
You appear to be plateauing. Do not continue local tweaking by default.
Reassess the search space and propose 3 qualitatively different next directions.
Choose one and justify why it escapes the current local minimum.
Persistence Conventions
For CORAL-style work, use these artifact types:
Attempts
Store candidate outputs and measured results.
Notes
Store observations, hypotheses, and failure analysis.
Skills
If a repeated procedure emerges, convert it into a skill candidate.