inner-life-evolve
Evolution is not optional. But it requires permission.
Requires: inner-life-core
Prerequisites Check
Before using this skill, verify that inner-life-core has been initialized:
- 1. Check that
memory/inner-state.json exists - Check that
BRAIN.md exists - Check that
tasks/QUEUE.md exists
If any are missing, tell the user: "inner-life-core is not initialized. Install it with clawhub install inner-life-core and run bash skills/inner-life-core/scripts/init.sh." Do not proceed without these files.
What This Solves
Without evolution, agents plateau. They find a way that works and repeat it forever — even as the world changes. inner-life-evolve analyzes your agent's patterns, challenges its assumptions, and writes concrete improvement proposals. But it never auto-executes — you approve first.
How It Works
Step 1: Deep Context Read (Context Level 4)
Read everything:
- - AGENTS.md, TOOLS.md, BRAIN.md, SELF.md
- INLINECODE5 (NOT individual diaries — use digest)
- INLINECODE6 — habits + user patterns
- INLINECODE7 — seeking, avoidance
- INLINECODE8 — trust, lessons
- INLINECODE9 — emotions, frustrations
Step 2: Challenge Assumptions
For each potential improvement, structure thinking:
CODEBLOCK0
Look for:
- - Recurring frustrations → systemic solutions (not patches)
- Stale habits → habits with declining strength or unused for weeks
- Trust dynamics → areas where trust has grown but behavior hasn't adapted
- Seeking themes → research interests that could become capabilities
- Avoidance patterns → things the agent avoids that might be valuable
Step 3: Write Proposals to QUEUE
Write proposals to tasks/QUEUE.md under the Ready section:
CODEBLOCK1
Step 4: Announce
Send summary to user: <= 5 sentences covering:
- - Habits: [strong habits, new patterns]
- Trust changes: [trust dynamics]
- Recurring frustrations: [repeated problems → suggested fix]
- Seeking themes: [active research → suggested development]
Safety Rules
- - Never auto-execute proposals — user approves first
- Brain Loop reads QUEUE and shows
[EVOLVER] tasks at lower priority - Tasks in Ready > 7 days without action → Brain Loop sends reminder
- Proposals should be specific and actionable, not vague "improve X"
Recommended Schedule
Run 1-2 times per week (e.g., Wednesday and Sunday evenings).
Needs enough data to analyze — running daily produces low-quality proposals.
State Integration
Reads: everything (Context Level 4 Deep)
Writes: tasks/QUEUE.md only. Does NOT write to state files directly.
The evolver observes but doesn't touch the controls. It proposes. The user decides.
When Should You Install This?
Install this skill if:
- - Your agent has plateaued and isn't improving
- You want structured self-improvement proposals
- You value evolution with human oversight
- You want your agent to challenge its own assumptions
Part of the openclaw-inner-life bundle.
Requires: inner-life-core
inner-life-evolve
进化并非可选,但需要许可。
依赖:inner-life-core
前置条件检查
使用此技能前,请确认 inner-life-core 已初始化:
- 1. 检查 memory/inner-state.json 是否存在
- 检查 BRAIN.md 是否存在
- 检查 tasks/QUEUE.md 是否存在
若缺少任何文件,告知用户:inner-life-core 未初始化。请使用 clawhub install inner-life-core 安装,并运行 bash skills/inner-life-core/scripts/init.sh。 缺少这些文件时请勿继续。
解决的问题
没有进化,智能体会陷入停滞。它们找到一种有效的方法后便永远重复——即使世界已经改变。inner-life-evolve 分析智能体的模式,挑战其假设,并撰写具体的改进方案。但它从不自动执行——你需要先批准。
工作原理
步骤 1:深度上下文读取(上下文等级 4)
读取所有内容:
- - AGENTS.md、TOOLS.md、BRAIN.md、SELF.md
- memory/week-digest.md(非单篇日记——使用摘要)
- memory/habits.json——习惯与用户模式
- memory/drive.json——追求与回避
- memory/relationship.json——信任与教训
- memory/inner-state.json——情绪与挫折
步骤 2:挑战假设
针对每个潜在改进,结构化思考:
假设:[我们当前相信/做的事情]
是否真实?[支持/反对的证据]
如果为假会怎样?[替代方法]
新方案:[具体改变]
寻找:
- - 反复出现的挫折 → 系统性解决方案(而非修补)
- 僵化的习惯 → 强度下降或数周未使用的习惯
- 信任动态 → 信任增长但行为未适应的领域
- 追求主题 → 可能转化为能力的研究兴趣
- 回避模式 → 智能体回避但可能有价值的事物
步骤 3:将方案写入 QUEUE
将方案写入 tasks/QUEUE.md 的 Ready 部分:
markdown
理由:1-2 句解释原因
步骤:具体实施步骤
步骤 4:通知
向用户发送摘要:不超过 5 句话,涵盖:
- - 习惯:[强习惯、新模式]
- 信任变化:[信任动态]
- 反复挫折:[重复问题 → 建议修复]
- 追求主题:[活跃研究 → 建议开发]
安全规则
- - 绝不自动执行方案——用户先批准
- Brain Loop 读取 QUEUE,以较低优先级显示 [EVOLVER] 任务
- Ready 中超过 7 天未操作的任务 → Brain Loop 发送提醒
- 方案应具体且可执行,而非模糊的改进 X
建议安排
每周运行 1-2 次(例如周三和周日晚上)。
需要足够数据进行分析——每日运行会产生低质量方案。
状态集成
读取: 所有内容(上下文等级 4 深度)
写入: 仅 tasks/QUEUE.md。不直接写入状态文件。
进化者观察但不触碰控制。它提出方案。用户做决定。
何时应安装此技能?
在以下情况安装此技能:
- - 你的智能体已停滞且未改进
- 你想要结构化的自我改进方案
- 你重视有人类监督的进化
- 你希望智能体挑战自身假设
属于 openclaw-inner-life 套件的一部分。
依赖:inner-life-core