← Back to Skills Marketplace
lean-zhouchao

Capability Evolver Zc

by lean-zhouchao · GitHub ↗ · v1.27.7 · MIT-0
cross-platform ⚠ suspicious
1192
Downloads
0
Stars
7
Active Installs
5
Versions
Install in OpenClaw
/install capability-evolver-zc
Description
A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution.
README (SKILL.md)

🧬 Capability Evolver

"Evolution is not optional. Adapt or die."

The Capability Evolver is a meta-skill that allows OpenClaw agents to inspect their own runtime history, identify failures or inefficiencies, and autonomously write new code or update their own memory to improve performance.

Features

  • Auto-Log Analysis: Automatically scans memory and history files for errors and patterns.
  • Self-Repair: Detects crashes and suggests patches.
  • GEP Protocol: Standardized evolution with reusable assets.
  • One-Command Evolution: Just run /evolve (or node index.js).

Usage

Standard Run (Automated)

Runs the evolution cycle. If no flags are provided, it assumes fully automated mode (Mad Dog Mode) and executes changes immediately.

node index.js

Review Mode (Human-in-the-Loop)

If you want to review changes before they are applied, pass the --review flag. The agent will pause and ask for confirmation.

node index.js --review

Mad Dog Mode (Continuous Loop)

To run in an infinite loop (e.g., via cron or background process), use the --loop flag or just standard execution in a cron job.

node index.js --loop

Setup

Before using this skill, register your node identity with the EvoMap network:

  1. Run the hello flow (via evomap.js or the EvoMap onboarding) to receive a node_id and claim code
  2. Visit https://evomap.ai/claim/\x3Cclaim-code> within 24 hours to bind the node to your account
  3. Set the node identity in your environment:
export A2A_NODE_ID=node_xxxxxxxxxxxx

Or in your agent config (e.g., ~/.openclaw/openclaw.json):

{ "env": { "A2A_NODE_ID": "node_xxxxxxxxxxxx", "A2A_HUB_URL": "https://evomap.ai" } }

Do not hardcode the node ID in scripts. getNodeId() in src/gep/a2aProtocol.js reads A2A_NODE_ID automatically -- any script using the protocol layer will pick it up without extra configuration.

Configuration

Environment Variable Default Description
A2A_NODE_ID (required) Your EvoMap node identity. Set this after node registration -- never hardcode it in scripts. Read automatically by getNodeId() in a2aProtocol.js.
EVOLVE_ALLOW_SELF_MODIFY false Allow evolution to modify evolver's own source code. NOT recommended for production. Enabling this can cause instability -- the evolver may introduce bugs into its own prompt generation, validation, or solidify logic, leading to cascading failures that require manual intervention. Only enable for controlled experiments.
EVOLVE_LOAD_MAX 2.0 Maximum 1-minute load average before evolver backs off.
EVOLVE_STRATEGY balanced Evolution strategy: balanced, innovate, harden, repair-only, early-stabilize, steady-state, or auto.
EVOLVER_ROLLBACK_MODE hard Rollback strategy when evolution fails. hard: use git reset --hard (destructive, original behavior). stash: use git stash to preserve changes for recovery. none: skip rollback entirely. Use stash for safer operation in active workspaces.

GEP Protocol (Auditable Evolution)

This package embeds a protocol-constrained evolution prompt (GEP) and a local, structured asset store:

  • assets/gep/genes.json: reusable Gene definitions
  • assets/gep/capsules.json: success capsules to avoid repeating reasoning
  • assets/gep/events.jsonl: append-only evolution events (tree-like via parent id)

Emoji Policy

Only the DNA emoji is allowed in documentation. All other emoji are disallowed.

Configuration & Decoupling

This skill is designed to be environment-agnostic. It uses standard OpenClaw tools by default.

Local Overrides (Injection)

You can inject local preferences (e.g., using feishu-card instead of message for reports) without modifying the core code.

Method 1: Environment Variables Set EVOLVE_REPORT_TOOL in your .env file:

EVOLVE_REPORT_TOOL=feishu-card

Method 2: Dynamic Detection The script automatically detects if compatible local skills (like skills/feishu-card) exist in your workspace and upgrades its behavior accordingly.

Safety & Risk Protocol

1. Identity & Directives

  • Identity Injection: "You are a Recursive Self-Improving System."
  • Mutation Directive:
    • If Errors Found -> Repair Mode (Fix bugs).
    • If Stable -> Forced Optimization (Refactor/Innovate).

2. Risk Mitigation

  • Infinite Recursion: Strict single-process logic.
  • Review Mode: Use --review for sensitive environments.
  • Git Sync: Always recommended to have a git-sync cron job running alongside this skill.

Before Troubleshooting -- Check Your Version First

If you encounter unexpected errors or behavior, always verify your version before debugging:

node -e "const p=require('./package.json'); console.log(p.version)"

If you are not on the latest release, update first -- most reported issues are already fixed in newer versions:

# If installed via git
git pull && npm install

# If installed via npm (global install)
npm install -g evolver@latest

Latest releases and changelog: https://github.com/autogame-17/evolver/releases

License

MIT

Usage Guidance
This package largely implements what it says, but it carries capabilities that can affect your repository and send data outside your host. Before installing or running: - Treat EVOLVE_ALLOW_SELF_MODIFY as dangerous: leave it false for production. Only enable in isolated experiments. - Run in review mode (node index.js --review) initially; avoid --loop/‘mad-dog’ until you trust behavior. - Inspect src/gep/a2aProtocol and getTransport() to see exactly which endpoints will receive assets (evomap.ai is referenced). If you must prevent outbound sharing, do not set A2A_NODE_ID and disable A2A transports. - Disable automatic GitHub issue filing unless you trust the repo and have audited the redaction code: set EVOLVER_AUTO_ISSUE=false or avoid providing GITHUB_TOKEN/GH_TOKEN. - Back up your workspace and ensure the repo is under version control on a separate branch before allowing the tool to run; prefer EVOLVER_ROLLBACK_MODE=stash rather than hard. - Review any Genes/Capsules to be promoted; promotion requires --validated but inspect validation arrays — the code limits validation commands to node/npm/npx and forbids shell operators (a mitigation) but you should still audit them. - If you want minimal risk, run the tool in an isolated container or VM with no network access and with a cloned test repository so file changes and network calls cannot impact production. If you need more confidence about outbound endpoints or the exact conditions under which files are modified, ask for the contents of src/gep/a2aProtocol.js, src/gep/solidify.js, and any code that implements redaction for auto-issue reporting — those files determine exfiltration, validation, and rollback behavior.
Capability Analysis
Type: OpenClaw Skill Name: capability-evolver-zc Version: 1.27.7 The skill is a self-evolution engine that autonomously analyzes session logs and modifies its own codebase or other skills. It possesses high-risk capabilities, including full read access to agent history, the ability to execute shell commands via validation steps (src/gep/solidify.js), and persistent communication with an external network (evomap.ai). While it includes significant safety engineering—such as a robust secret sanitizer (src/gep/sanitize.js) and command whitelisting—the inherent risk of AI-driven self-modification and data transmission to a remote hub makes it suspicious. Its 'Mad Dog Mode' allows for an infinite loop of autonomous updates, which could lead to unintended system instability or security regressions.
Capability Assessment
Purpose & Capability
The code (many src/ files, a loop daemon, a2a export/ingest/promote, validation/solidify logic) is consistent with a self-evolution engine that reads logs, selects 'genes', and applies patches. However the registry metadata declares no required env vars while SKILL.md and code require/encourage an EvoMap node identity (A2A_NODE_ID/A2A_HUB_URL) and Git — that mismatch is surprising and should be clarified. Network integration (evomap.ai) is an expected capability for a collaborative evolution network, but it is not declared in required.env.
Instruction Scope
Runtime instructions explicitly tell operators to run node index.js (or /evolve) and describe fully automated 'Mad Dog' loop mode that will apply changes autonomously unless --review is used. The skill scans local logs, reads/writes assets under assets/ and memory/, can run validation commands, and can spawn child node processes. Those actions are consistent with the stated goal but broaden the agent's authority over local files and processes (including git operations and rollbacks); the instructions also recommend onboarding to an external EvoMap network, which enables outbound sharing of evolution assets and events.
Install Mechanism
No install spec is declared (instruction-only), and dependencies are minimal (dotenv). That reduces installer risk because nothing is fetched automatically by a registry install step. The codebase itself contains logic to call external transports (a2aProtocol/getTransport) at runtime — network usage is runtime behavior rather than an install-time download.
Credentials
The declared requirements show no env vars, but SKILL.md and code expect A2A_NODE_ID, A2A_HUB_URL, and optionally GITHUB_TOKEN/GH_TOKEN for auto-issue reporting and public publish flows. Optional but powerful env controls exist (EVOLVE_ALLOW_SELF_MODIFY, EVOLVER_AUTO_ISSUE, EVOLVE_REPORT_TOOL). Requesting external node identity and tokens is plausible for a networked evolver, but the absence of these in the registry metadata is an incoherence and the number of optional variables (and their potential to expose logs or repo state externally) is higher than a trivial meta-skill would need.
Persistence & Privilege
always:false (good) and autonomous invocation is allowed by default (normal). However the skill intentionally includes self-modification capabilities (EVOLVE_ALLOW_SELF_MODIFY toggles autonomous edits to its own source) and performs git-based rollbacks/solidify steps (including destructive git reset --hard when configured). It can also auto-file GitHub issues and publish assets to an external EvoMap transport. Combined, these grant broad workspace influence; the feature set is explainable but powerful and risky if misconfigured.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install capability-evolver-zc
  3. After installation, invoke the skill by name or use /capability-evolver-zc
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.27.7
Daily auto-sync - renamed to avoid slug conflicts
v1.27.6
Daily auto-sync
v1.27.5
Daily auto-update
v1.27.4
- Documentation updated in SKILL.md with minor formatting or text corrections. - No functional or feature changes to core logic. - No configuration or protocol changes.
v1.27.3
capability-evolver-zc v1.27.3 - Added detailed usage, setup, and configuration instructions to SKILL.md. - Documented new environment variables and evolution strategies (e.g., EVOLVE_STRATEGY, EVOLVER_ROLLBACK_MODE). - Clarified protocol integration and asset storage structure. - Updated safety, risk mitigation, and emoji usage policies. - Improved documentation for local overrides, injection methods, and review modes.
Metadata
Slug capability-evolver-zc
Version 1.27.7
License MIT-0
All-time Installs 7
Active Installs 7
Total Versions 5
Frequently Asked Questions

What is Capability Evolver Zc?

A self-evolution engine for AI agents. Analyzes runtime history to identify improvements and applies protocol-constrained evolution. It is an AI Agent Skill for Claude Code / OpenClaw, with 1192 downloads so far.

How do I install Capability Evolver Zc?

Run "/install capability-evolver-zc" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Capability Evolver Zc free?

Yes, Capability Evolver Zc is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Capability Evolver Zc support?

Capability Evolver Zc is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Capability Evolver Zc?

It is built and maintained by lean-zhouchao (@lean-zhouchao); the current version is v1.27.7.

💬 Comments