autoresearch-worker

Generate, execute, and commit hill-climbing experiments with structured trailers.

1|2|Updated Apr 29, 2026

Search Tags:#automation #git #orchestrator #experiments #path-management #autoresearch #hill-climbing

Ready to run

npx skills add https://github.com/fuzzy-dynamics/strings --skill autoresearch-worker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autoresearch-worker
Source: https://github.com/fuzzy-dynamics/strings/tree/main/skills/autoresearch-worker
Command: npx skills add https://github.com/fuzzy-dynamics/strings --skill autoresearch-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end hill-climbing autoresearch on a single research path, autonomously generating experiments, running them, committing each result, and escalating when needed, without user micromanagement.

Core Features & Use Cases

End-to-end autonomous experimentation: generates, executes, commits, and trailers for each experiment on a candidate branch.
Dual-mode operation: default executor and "writer" synthesis mode for integrator-path reporting.
Orchestrator integration: coordinates with a central orchestrator, interprets escalation signals, and uses structured trailers for traceability.

Quick Start

Spawn an autoresearch-worker on a running autoresearch path and let it manage experiments until budget exhaustion or a stop signal is received.

Frequently Asked Questions about autoresearch-worker

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

FAQPage Schema

How do I automate hill-climbing experimentation and commit results autonomously?▼

Automating hill-climbing experimentation requires a worker that autonomously generates, executes, and commits experiments with structured trailers to a candidate branch. This worker handles the end-to-end process until budget exhaustion or a stop signal is received.

What is autonomous hill-climbing autoresearch and when do I need structured commit metadata?▼

Autonomous hill-climbing autoresearch is a process where a worker explores parameter spaces and commits results with structured trailers. You need it for controlled experimentation where traceability and orchestrator integration managing paths and budgets are required.

How do I escalate on plateaus or anomalies during parameter space exploration?▼

To escalate on plateaus or anomalies during parameter space exploration, the worker interprets escalation signals from a central orchestrator. It coordinates path management and stops when budget exhaustion or a specific stop signal occurs.

Can I use this worker for integrator-path reporting instead of default execution?▼

Yes, you can use the worker for integrator-path reporting through its dual-mode operation. It features a default executor mode for running experiments and a writer synthesis mode specifically for generating integrator-path reports.

Does this autonomous experimentation approach require a central orchestrator for path management?▼

Yes, autonomous experimentation with this worker requires integration with a central orchestrator. The orchestrator manages paths, budgets, and escalation signals, while the worker coordinates with it to execute experiments and log results.

What are the limitations of using a single autoresearch path for parameter optimization?▼

Using a single autoresearch path limits exploration to one branch of parameter space at a time. The worker escalates on plateaus or anomalies and operates until budget exhaustion, requiring orchestrator coordination to manage multiple paths for broader optimization.