Menu
Orchestrates automated code improvement through hypothesis-driven experimentation and self-evolution
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.
| name | auto-workflow |
| description | Orchestrates automated code improvement through hypothesis-driven experimentation and self-evolution |
| version | 1.1 |
| level | compound |
| molecules | ["benchmark-improver","evolution-patterns","skill-eval","sandbox-profiles"] |
metadata: evolution-stats: total-experiments: 870
This skill suite orchestrates automated code improvement through systematic experimentation and self-evolution.
The auto-workflow system consists of coordinated sub-skills:
Auto-workflow is triggered by the cron pipeline or manual invocation:
(auto-workflow bootstrap [target-path])
This skill auto-improves through:
0 23,3,7,11,15,19 * * *var/tmp/cron/pipeline.lockvar/tmp/research-traces/var/tmp/researcher-controller.jsonTransforms research paper analysis from extraction to narrative storytelling. Uses 7-beat narrative spine (protagonist/dilemma/old-path/turning-point/solution/ending/core) to make papers understandable to non-experts. Includes speed-read card, PhD advisor review, and real-world testing. Use when researcher encounters a research paper and needs to extract deep understanding, not just surface facts. Triggers on "paper", "research paper", "analyze paper", "tell me about this paper", "讲论文", "读论文".
Workflow chain: researcher → paper-storytelling. When researcher encounters a research paper, automatically invoke paper-storytelling to transform extraction into narrative understanding. Use when user says "research paper", "analyze this paper", "tell me about this paper", or when researcher detects arxiv/PDF links.
Prompt template for external research specialist subagent. Auto-evolves based on experiment outcomes.
Inspect and operate OV5 (Ouroboros V5) through the live Emacs daemon. Use when checking auto-workflow status, starting guarded runs, reviewing experiment results, or querying researcher and evolution state.
Clojure REPL client (nREPL-based, Babashka). Use for evaluating Clojure code, loading Clojure files, fixing unbalanced brackets, and interactive nREPL work. Not the Elisp daemon-repl.
Daemon REPL for Elisp — evaluate Elisp code in a running Emacs daemon via emacsclient, validate brackets before save, auto-evaluate .el files on change. Use when you need to run Elisp from outside Emacs, check daemon status, or validate Elisp syntax.
Based on SOC occupation classification
