القائمة
Wu Xing-based auto-improvement system for benchmarks. Detects anti-patterns via 相克 and generates improvements via 相生 pathways.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | benchmark-improver |
| description | Wu Xing-based auto-improvement system for benchmarks. Detects anti-patterns via 相克 and generates improvements via 相生 pathways. |
| version | 1 |
| metadata | {"evolution-stats":{"total-experiments":870}} |
| level | molecule |
| atoms | ["eight-keys-grader","elisp-expert","evolution-patterns"] |
Apply Wu Xing (Five Elements) theory to detect benchmark anti-patterns and generate targeted improvements.
Water → Wood → Fire → Earth → Metal → Water
Guides the sequence of improvements. When an element is deficient, strengthen it by enhancing its generator.
Wood → Earth → Water → Fire → Metal → Wood
Detects which element is in excess and applies the controlling element as remedy.
Controlled by: Metal (coordination)
Generated by: Water (identity)
When benchmark shows excessive steps, redundant operations, or inefficiency:
Controlled by: Water (identity/principles)
Generated by: Wood (operations)
When benchmark shows lack of planning, reactive fixes, or scattered approach:
Controlled by: Wood (operations/execution)
Generated by: Fire (intelligence)
When benchmark shows rigidity, excessive constraints, or inability to adapt:
Controlled by: Fire (intelligence/adaptation)
Generated by: Earth (control)
When benchmark shows bureaucratic overhead, inflexible rules, or coordination failures:
Controlled by: Earth (control/processes)
Generated by: Metal (coordination)
When benchmark shows vague goals, lack of direction, or identity crisis:
Observe → Detect → Generate → Apply → Verify → Feed Forward
;; Auto-improve a skill
(gptel-benchmark-auto-improve-skill "my-skill" benchmark-results)
;; Auto-improve a workflow
(gptel-benchmark-auto-improve-workflow "my-workflow" benchmark-results)
;; Batch improve multiple items
(gptel-benchmark-batch-improve
'(("skill-a" skill results-a)
("workflow-b" workflow results-b)))
Anti-patterns are detected by analyzing benchmark results against Eight Keys scores:
Map low scores to their element and apply the corresponding improvement rules above.
Based on analysis of which improvement types led to score increases.
| Element | Effectiveness | Improvement Rate | Total | Improved | Worsened |
|---|---|---|---|---|---|
| Control (Earth) | marginally-effective | 22% | 18 | 4 | 5 |
| Intelligence (Fire) | highly-effective | 67% | 3 | 2 | 0 |
| Coordination (Metal) | ineffective | 12% | 77 | 9 | 15 |
| Identity (Water) | ineffective | 18% | 148 | 27 | 27 |
| Operations (Wood) | ineffective | 8% | 78 | 6 | 9 |
Prioritize these improvement types:
Reconsider these improvement types:
Based on analysis of 0 experiments.
Transforms 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.