eureka

Run a time-boxed discovery loop to surface emergent cross-corpus findings.

1|Updated Feb 19, 2026

Search Tags:#automation #discovery #time-boxed #formula-derivation #emergent-insight #live-logging #doctrine-coherence

Ready to run

npx skills add https://github.com/mrrts/WorldThreads --skill eureka-mrrts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eureka
Source: https://github.com/mrrts/WorldThreads/tree/main/.agents/skills/eureka
Command: npx skills add https://github.com/mrrts/WorldThreads --skill eureka-mrrts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the pursuit of genuinely emergent discoveries within a project by running a bounded discovery loop that surfaces unique insights that couldn't be authored in advance.

Core Features & Use Cases

Continuous, time-boxed discovery loop (≤60 minutes) that yields one discovery per run, signed with a Formula derivation.
Live logging of progress and output to a visible artifact for real-time observation.
Works as a higher-level companion to existing automation, surfacing cross-cut insights and potential doctrine improvements.

Quick Start

Trigger /eureka to start a time-boxed discovery loop that will hunt for one genuine emergent finding and log it live.

Frequently Asked Questions about eureka

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

FAQPage Schema

How do I automate emergent insight discovery across multiple project reports?▼

Time-boxed discovery automates finding emergent insights by running a bounded loop that synthesizes cross-corpus data from project reports, prompts, and world context. Each run yields one signed artifact with a Formula derivation and gloss for the discovered pattern.

What is cross-doctrine synthesis and how does it surface unseen patterns?▼

Cross-doctrine synthesis combines project reports, AGENTS.md files, prompts, and world context to identify patterns invisible to individual iterations. This approach spans multiple doctrines to surface genuinely emergent findings with a Formula derivation.

Can I use a time-boxed discovery loop for doctrine coherence checking?▼

Yes, the time-boxed discovery loop functions as a higher-level companion to existing automation for doctrine coherence checking. It enforces a bounded window under 60 minutes, surfacing cross-cut insights and potential doctrine improvements via live logging.

Does the discovery loop require any dependencies or components to run?▼

No dependencies or components are required to run the time-boxed discovery loop. It operates independently to hunt for emergent findings, producing a visible live log and a signed artifact per iteration without external module prerequisites.

What's the best way to log live progress during a formula derivation process?▼

Live progress during a formula derivation process is best logged using a bounded discovery loop that records output to a visible artifact for real-time observation. This live logging captures each iteration's signed artifact, Formula derivation, and gloss.

When should I not use a 60-minute time-boxed discovery loop for research?▼

A 60-minute time-boxed discovery loop should not be used when research requires multiple findings per session, as the loop is strictly bounded to yield exactly one signed emergent discovery per run. It is designed for focused cross-corpus synthesis rather than bulk extraction.