From a3db9d258542a2960645743442f944968d24ec2b Mon Sep 17 00:00:00 2001
From: TevinClaw <510129976@qq.com>
Date: Tue, 17 Mar 2026 12:50:46 +0800
Subject: [PATCH] 移除：旧热记忆和自改进技能，更新工具箱记录 memory-md-learning 触发规则
---
workspace/TOOLS.md | 47 +++++++++
/dev/null | 221 --------------------------------------------
2 files changed, 47 insertions(+), 221 deletions(-)
diff --git a/workspace/TOOLS.md b/workspace/TOOLS.md
index 3a5947a..08cfa62 100644
--- a/workspace/TOOLS.md
+++ b/workspace/TOOLS.md
@@ -10,6 +10,53 @@
- 搜索新闻时，优先使用技能 `tavily-search` 而不是 `web_fetch`
+## 记忆技能触发规则
+
+### memory-md-hot 热记忆更新
+- **触发时机**: 每日晚上10点后（心跳任务）
+- **执行命令**: `python skills/memory-md-hot/scripts/daily_maintenance.py update`
+- **功能**: 扫描当日记忆，更新事件流水，保留所有历史
+
+### memory-md-archive 归档控制
+- **触发时机**: 每日热记忆更新后（心跳任务）
+- **执行命令**: `python skills/memory-md-archive/scripts/archive.py`
+- **功能**: 归档8天前内容、超过30条的重要/学习事件、体积控制（4KB限制）
+
+### memory-md-learning 学习记录
+
+**自动触发场景**（解决问题后立即调用）：
+- 修复了难以发现的 bug
+- 解决了配置冲突问题
+- 找到了更优的解决方案
+- 翻过陷阱或踩坑后
+
+**用户主动触发**（用户说以下关键词时）：
+- "学习一下"
+- "记录下来"
+- "记住这个"
+- "总结经验"
+- "这个要记"
+
+**执行命令**:
+```bash
+python skills/memory-md-learning/scripts/learning.py \
+ --trap "现象描述" \
+ --cause "根本原因" \
+ --fix "解决方案" \
+ --prevent "预防措施" \
+ --principle "行为准则" \
+ --trigger "触发条件" \
+ --action "具体行动" \
+ --tag "标签" \
+ --summary "一句话概要" \
+ --keywords "关键词1,关键词2"
+```
+
+**学习内容**:
+1. **技术层**（长期记忆）: 陷阱、原因、修复、预防
+2. **原则层**（长期记忆）: 决策原则、触发条件、行动
+3. **学习事件**（MEMORY.md）: 日期+概要+关键词
+
## 这里记什么
技能定义了工具如何工作，这个文件是用来记录那些只属于你的设置的东西
diff --git a/workspace/skills/hot-memory/SKILL.md b/workspace/skills/hot-memory/SKILL.md
deleted file mode 100644
index 6d3e010..0000000
--- a/workspace/skills/hot-memory/SKILL.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-name: hot-memory
-description: 管理 MEMORY.md 热记忆文件，维护最近7天事件流水和重要事件记录。当需要更新 memory.md、添加日常事件或重要事件、检查文件大小时使用。支持每日自动维护，移除8天前的旧记录，监控4KB大小限制。
----
-
-# hot-memory 技能
-
-管理 `MEMORY.md` 热记忆文件，让 agent 每次启动时被动了解最近发生的事情。
-
-## 文件定位
-
-- **目标文件**: `~/.openclaw/workspace/MEMORY.md`
-- **维护脚本**: `scripts/daily_maintenance.py`
-
-## 文件结构
-
-`MEMORY.md` 包含三个部分：
-
-1. **文件说明** - 说明本文件记录已发生的事情，详细信息可通过记忆检索获取
-2. **🔔 重要事件** - 全局长期性影响的重要决策和事件（默认空，记录时需告知用户）
-3. **📅 最近7天事件流水** - 按天分组的每日主要事情概要
-
-## 事件格式
-
-所有事件遵循统一格式：
-
-```
-- YYYY-MM-DD HH:MM | 一句话概要 | 关键词1,关键词2
-```
-
-示例：
-```
-- 2026-03-16 10:30 | 创建hot-memory技能 | 技能,记忆系统
-- 2026-03-16 14:00 | 配置LanceDB嵌入模型 | 配置,向量数据库
-```
-
-## 使用场景
-
-### 场景1: 每日维护（自动）
-
-每天执行一次，从记忆检索中获取当日事件，更新流水：
-
-```bash
-python3 ~/.openclaw/workspace/skills/hot-memory/scripts/daily_maintenance.py update
-```
-
-**功能**:
-- 扫描今日记忆，提取重要事件
-- 添加新的日常事件到对应日期分组
-- 自动移除8天前的旧记录
-- 检查文件大小，超限则警告
-
-### 场景2: 添加日常事件
-
-记录一般的日常活动：
-
-```bash
-python3 scripts/daily_maintenance.py add-daily 2026-03-16 "10:30" "测试脚本" "开发,测试"
-```
-
-或在 agent 会话中：
-
-```python
-from skills.hot_memory.scripts.daily_maintenance import update_memory_file
-
-# 添加单个日常事件
-event = ("2026-03-16", "10:30", "测试脚本", "开发,测试")
-result = update_memory_file(new_daily_events=[event])
-```
-
-### 场景3: 添加重要事件
-
-记录具有全局长期性影响的事件（**必须告知用户**）：
-
-```bash
-python3 scripts/daily_maintenance.py add-important 2026-03-16 "14:00" "重构记忆系统" "架构,重要"
-```
-
-或在 agent 会话中：
-
-```python
-event = ("2026-03-16", "14:00", "重构记忆系统", "架构,重要")
-result = update_memory_file(important_event=event)
-
-if result['added_important']:
- print("已记录重要事件，请告知用户")
-```
-
-### 场景4: 检查文件大小
-
-```bash
-python3 scripts/daily_maintenance.py check-size
-```
-
-或在 agent 会话中：
-
-```python
-from skills.hot_memory.scripts.daily_maintenance import check_size
-
-status = check_size()
-if status['exceeded']:
- print(f"⚠️ 文件大小 {status['size_kb']}KB 超过 4KB 限制")
-```
-
-## 重要事件判断标准
-
-什么应该记录为重要事件：
-
-| 类型 | 示例 |
-|------|------|
-| 架构变更 | 记忆系统重构、技能体系升级 |
-| 配置变更 | API Key 更换、模型切换 |
-| 重要决策 | 采用新工作流、确立规范 |
-| 关键里程碑 | 项目完成、重要功能上线 |
-
-什么只记录为日常事件：
-
-| 类型 | 示例 |
-|------|------|
-| 常规查询 | 天气查询、网页搜索 |
-| 临时任务 | 单次文件处理、数据分析 |
-| 日常对话 | 问答、简单讨论 |
-
-## 文件大小管理
-
-**限制**: 4KB (4096 字节)
-
-**超限处理**:
-1. 首先检查是否有过期的日常事件未清理
-2. 考虑将较早的重要事件归档到 L1 层
-3. 与用户讨论瘦身方案
-
-**瘦身策略**:
-- 保留最近7天流水（已自动维护）
-- 将旧的重要事件移动到 `memory/milestones/` 归档
-- 简化事件描述的详细程度
-
-## 与其他组件的关系
-
-```
-┌─────────────────────────────────────────────────────────┐
-│ LanceDB-Pro 向量记忆 │
-│ - 存储所有详细记忆 │
-│ - 支持语义检索 │
-└────────────────────┬────────────────────────────────────┘
- │ 检索
- ▼
-┌─────────────────────────────────────────────────────────┐
-│ MEMORY.md 热记忆 (本技能管理) │
-│ - 最近7天流水（摘要） │
-│ - 重要事件（全局影响） │
-│ - 4KB 精简索引 │
-└────────────────────┬────────────────────────────────────┘
- │ 启动注入
- ▼
-┌─────────────────────────────────────────────────────────┐
-│ Agent 启动上下文 │
-│ - 快速了解最近发生了什么 │
-│ - 无需查询即可感知活跃记忆 │
-└─────────────────────────────────────────────────────────┘
-```
-
-## 最佳实践
-
-1. **每日更新**: 建议设置定时任务每天执行 `update` 命令
-2. **即时记录**: 重要事件发生后立即记录，不要累积
-3. **简洁描述**: 一句话概要，关键词用逗号分隔
-4. **主动告知**: 添加重要事件时必须告知用户
-5. **定期检查**: 每周检查一次文件大小
-
-## 故障排查
-
-### 文件未更新
-- 检查脚本路径是否正确
-- 确认 `MEMORY.md` 存在且可写
-
-### 大小超限警告
-- 执行 `check-size` 确认实际大小
-- 考虑手动归档旧的重要事件
-- 与用户讨论清理策略
-
-### 日期解析错误
-- 确保日期格式为 `YYYY-MM-DD`
-- 时间格式建议为 `HH:MM` 或 `--:--`
diff --git a/workspace/skills/hot-memory/scripts/daily_maintenance.py b/workspace/skills/hot-memory/scripts/daily_maintenance.py
deleted file mode 100644
index 5640d98..0000000
--- a/workspace/skills/hot-memory/scripts/daily_maintenance.py
+++ /dev/null
@@ -1,327 +0,0 @@
-#!/usr/bin/env python3
-"""
-hot-memory 每日维护脚本
-维护 memory.md 文件的最近7天事件流水和重要事件
-"""
-
-import os
-import re
-import sys
-from datetime import datetime, timedelta
-from pathlib import Path
-
-# 配置
-MEMORY_FILE = Path.home() / ".openclaw" / "workspace" / "MEMORY.md"
-MAX_SIZE_BYTES = 4 * 1024 # 4KB 限制
-DAYS_TO_KEEP = 7
-
-
-def read_memory_file():
- """读取 memory.md 文件内容"""
- if not MEMORY_FILE.exists():
- return ""
- return MEMORY_FILE.read_text(encoding='utf-8')
-
-
-def write_memory_file(content):
- """写入 memory.md 文件"""
- MEMORY_FILE.parent.mkdir(parents=True, exist_ok=True)
- MEMORY_FILE.write_text(content, encoding='utf-8')
-
-
-def get_file_size():
- """获取文件大小（字节）"""
- if not MEMORY_FILE.exists():
- return 0
- return MEMORY_FILE.stat().st_size
-
-
-def parse_date_from_line(line):
- """从行中提取日期（YYYY-MM-DD 格式）"""
- match = re.search(r'(\d{4}-\d{2}-\d{2})', line)
- if match:
- try:
- return datetime.strptime(match.group(1), '%Y-%m-%d').date()
- except ValueError:
- return None
- return None
-
-
-def is_within_last_7_days(line):
- """检查行是否在最近7天内"""
- date = parse_date_from_line(line)
- if not date:
- return True # 无日期的行保留
- cutoff_date = (datetime.now() - timedelta(days=DAYS_TO_KEEP)).date()
- return date >= cutoff_date
-
-
-def extract_event_entries(content):
- """
- 从内容中提取事件条目
- 返回: (important_events, daily_events) 元组
- """
- important_events = []
- daily_events = []
-
- lines = content.split('\n')
- in_important = False
- in_daily = False
-
- for line in lines:
- stripped = line.strip()
-
- # 检测区块
- if '重要事件' in stripped and stripped.startswith('#'):
- in_important = True
- in_daily = False
- continue
- elif ('最近7天事件流水' in stripped or '事件流水' in stripped) and stripped.startswith('#'):
- in_important = False
- in_daily = True
- continue
- elif stripped.startswith('#') and in_important:
- in_important = False
- elif stripped.startswith('#') and in_daily:
- in_daily = False
-
- # 收集事件
- if in_important and stripped and not stripped.startswith('-') and not stripped.startswith('*'):
- if len(stripped) > 10: # 过滤空行和短行
- important_events.append(line)
- elif in_daily and (stripped.startswith('-') or stripped.startswith('*')):
- if is_within_last_7_days(line):
- daily_events.append(line)
-
- return important_events, daily_events
-
-
-def generate_default_content():
- """生成默认的 memory.md 内容"""
- today = datetime.now().strftime('%Y-%m-%d')
- return f"""# MEMORY.md - 热记忆 / 活跃记忆
-
-> 本文件记录近期发生的重要事情，详细信息可通过记忆检索获取。
-
----
-
-## 🔔 重要事件
-
-> 记录具有全局长期性影响的重要决策和事件。
-> 添加重要事件时会告知用户。
-
-<!-- 重要事件在此添加 -->
-
----
-
-## 📅 最近7天事件流水
-
-> 按天分组，每天主要事情的概要。
-> 自动维护，8天前的记录会被移除。
-
-### {{today}}
-
-- {today} 10:00 | memory.md 初始化 | 热记忆系统
-
----
-
-*文件大小: ~0.5KB | 限制: 4KB*
-*维护脚本: `hot-memory/scripts/daily_maintenance.py`*
-""".format(today=today)
-
-
-def update_memory_file(new_daily_events=None, important_event=None):
- """
- 更新 memory.md 文件
-
- Args:
- new_daily_events: 新的每日事件列表 [(date, time, summary, keywords), ...]
- important_event: 重要事件元组 (date, time, summary, keywords) 或 None
-
- Returns:
- dict: 操作结果
- """
- result = {
- 'success': True,
- 'added_daily': 0,
- 'added_important': False,
- 'removed_old': 0,
- 'size_warning': False,
- 'current_size_kb': 0,
- 'messages': []
- }
-
- # 读取现有内容
- content = read_memory_file()
- if not content:
- content = generate_default_content()
-
- # 提取现有事件
- existing_important, existing_daily = extract_event_entries(content)
-
- # 移除8天前的日常事件
- cutoff_date = (datetime.now() - timedelta(days=DAYS_TO_KEEP)).date()
- filtered_daily = []
- for line in existing_daily:
- date = parse_date_from_line(line)
- if date and date < cutoff_date:
- result['removed_old'] += 1
- else:
- filtered_daily.append(line)
-
- # 添加新的日常事件
- if new_daily_events:
- for event in new_daily_events:
- date, time, summary, keywords = event
- entry = f"- {date} {time} | {summary} | {keywords}"
- # 检查是否已存在
- if not any(entry.strip() in existing.strip() for existing in filtered_daily):
- filtered_daily.append(entry)
- result['added_daily'] += 1
-
- # 添加重要事件
- new_important = list(existing_important)
- if important_event:
- date, time, summary, keywords = important_event
- entry = f"- {date} {time} | {summary} | {keywords}"
- new_important.append(entry)
- result['added_important'] = True
- result['messages'].append(f"重要事件已记录: {summary}")
-
- # 重新构建文件内容
- today = datetime.now().strftime('%Y-%m-%d')
-
- # 按日期分组日常事件
- daily_by_date = {}
- for line in filtered_daily:
- date = parse_date_from_line(line)
- if date:
- date_str = date.strftime('%Y-%m-%d')
- if date_str not in daily_by_date:
- daily_by_date[date_str] = []
- daily_by_date[date_str].append(line)
-
- # 构建日常事件区块
- daily_sections = []
- for date_str in sorted(daily_by_date.keys(), reverse=True):
- daily_sections.append(f"\n### {date_str}\n")
- daily_sections.extend([f"{line}\n" for line in daily_by_date[date_str]])
-
- daily_content = ''.join(daily_sections) if daily_sections else f"\n### {today}\n\n- {today} --:-- | 暂无记录 | --\n"
-
- # 构建重要事件区块
- important_content = '\n'.join(new_important) if new_important else "<!-- 重要事件在此添加 -->"
-
- # 组装最终内容
- current_size = get_file_size()
- new_content = f"""# MEMORY.md - 热记忆 / 活跃记忆
-
-> 本文件记录近期发生的重要事情，详细信息可通过记忆检索获取。
-
----
-
-## 🔔 重要事件
-
-> 记录具有全局长期性影响的重要决策和事件。
-> 添加重要事件时会告知用户。
-
-{important_content}
-
----
-
-## 📅 最近7天事件流水
-
-> 按天分组，每天主要事情的概要。
-> 自动维护，8天前的记录会被移除。
-{daily_content}
----
-
-*文件大小: ~{current_size / 1024:.1f}KB | 限制: 4KB*
-*维护脚本: `hot-memory/scripts/daily_maintenance.py`*
-"""
-
- # 写入文件
- write_memory_file(new_content)
-
- # 检查文件大小
- new_size = get_file_size()
- result['current_size_kb'] = round(new_size / 1024, 2)
-
- if new_size > MAX_SIZE_BYTES:
- result['size_warning'] = True
- result['messages'].append(f"警告: 文件大小 ({result['current_size_kb']}KB) 超过 4KB 限制，需要瘦身")
-
- return result
-
-
-def check_size():
- """检查文件大小并返回状态"""
- size = get_file_size()
- return {
- 'size_bytes': size,
- 'size_kb': round(size / 1024, 2),
- 'limit_bytes': MAX_SIZE_BYTES,
- 'limit_kb': 4,
- 'exceeded': size > MAX_SIZE_BYTES,
- 'percentage': round((size / MAX_SIZE_BYTES) * 100, 1)
- }
-
-
-def main():
- """主函数 - 供命令行调用"""
- if len(sys.argv) < 2:
- print("用法: python daily_maintenance.py <command> [args]")
- print("")
- print("命令:")
- print(" update - 执行每日更新")
- print(" check-size - 检查文件大小")
- print(" add-daily <date> <time> <summary> <keywords>")
- print(" - 添加日常事件")
- print(" add-important <date> <time> <summary> <keywords>")
- print(" - 添加重要事件")
- print("")
- print("示例:")
- print(' python daily_maintenance.py add-daily 2026-03-16 "10:30" "测试脚本" "开发,测试"')
- sys.exit(1)
-
- command = sys.argv[1]
-
- if command == "update":
- result = update_memory_file()
- print(f"更新完成:")
- print(f" - 添加日常事件: {result['added_daily']}")
- print(f" - 移除旧事件: {result['removed_old']}")
- print(f" - 添加重要事件: {'是' if result['added_important'] else '否'}")
- print(f" - 当前大小: {result['current_size_kb']}KB")
- for msg in result['messages']:
- print(f" - {msg}")
-
- elif command == "check-size":
- status = check_size()
- print(f"文件大小检查:")
- print(f" - 当前: {status['size_kb']}KB ({status['percentage']}%)")
- print(f" - 限制: {status['limit_kb']}KB")
- print(f" - 状态: {'⚠️ 超限' if status['exceeded'] else '✅ 正常'}")
-
- elif command == "add-daily" and len(sys.argv) >= 6:
- event = (sys.argv[2], sys.argv[3], sys.argv[4], sys.argv[5])
- result = update_memory_file(new_daily_events=[event])
- print(f"已添加日常事件: {event}")
- if result['size_warning']:
- print(f"⚠️ 警告: 文件大小 {result['current_size_kb']}KB 超过限制")
-
- elif command == "add-important" and len(sys.argv) >= 6:
- event = (sys.argv[2], sys.argv[3], sys.argv[4], sys.argv[5])
- result = update_memory_file(important_event=event)
- print(f"已添加重要事件: {event}")
- print(f"ℹ️ 请知悉用户: 已记录重要事件 '{sys.argv[4]}'")
- if result['size_warning']:
- print(f"⚠️ 警告: 文件大小 {result['current_size_kb']}KB 超过限制")
-
- else:
- print(f"未知命令或参数不足: {command}")
- sys.exit(1)
-
-
-if __name__ == "__main__":
- main()
diff --git a/workspace/skills/self-improving-agent/.clawhub/origin.json b/workspace/skills/self-improving-agent/.clawhub/origin.json
deleted file mode 100644
index c0718b2..0000000
--- a/workspace/skills/self-improving-agent/.clawhub/origin.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
- "version": 1,
- "registry": "https://clawhub.ai",
- "slug": "self-improving-agent",
- "installedVersion": "3.0.1",
- "installedAt": 1773304830240
-}
diff --git a/workspace/skills/self-improving-agent/.learnings/ERRORS.md b/workspace/skills/self-improving-agent/.learnings/ERRORS.md
deleted file mode 100644
index 6bce392..0000000
--- a/workspace/skills/self-improving-agent/.learnings/ERRORS.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Errors Log
-
-Command failures, exceptions, and unexpected behaviors.
-
----
diff --git a/workspace/skills/self-improving-agent/.learnings/FEATURE_REQUESTS.md b/workspace/skills/self-improving-agent/.learnings/FEATURE_REQUESTS.md
deleted file mode 100644
index 3527277..0000000
--- a/workspace/skills/self-improving-agent/.learnings/FEATURE_REQUESTS.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Feature Requests
-
-Capabilities requested by user that don't currently exist.
-
----
diff --git a/workspace/skills/self-improving-agent/.learnings/LEARNINGS.md b/workspace/skills/self-improving-agent/.learnings/LEARNINGS.md
deleted file mode 100644
index d31195d..0000000
--- a/workspace/skills/self-improving-agent/.learnings/LEARNINGS.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Learnings Log
-
-Captured learnings, corrections, and discoveries. Review before major tasks.
-
----
diff --git a/workspace/skills/self-improving-agent/SKILL.md b/workspace/skills/self-improving-agent/SKILL.md
deleted file mode 100644
index 97b5717..0000000
--- a/workspace/skills/self-improving-agent/SKILL.md
+++ /dev/null
@@ -1,647 +0,0 @@
----
-name: self-improvement
-description: "Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks."
-metadata:
----
-
-# Self-Improvement Skill
-
-Log learnings and errors to markdown files for continuous improvement. Coding agents can later process these into fixes, and important learnings get promoted to project memory.
-
-## Quick Reference
-
-| Situation | Action |
-|-----------|--------|
-| Command/operation fails | Log to `.learnings/ERRORS.md` |
-| User corrects you | Log to `.learnings/LEARNINGS.md` with category `correction` |
-| User wants missing feature | Log to `.learnings/FEATURE_REQUESTS.md` |
-| API/external tool fails | Log to `.learnings/ERRORS.md` with integration details |
-| Knowledge was outdated | Log to `.learnings/LEARNINGS.md` with category `knowledge_gap` |
-| Found better approach | Log to `.learnings/LEARNINGS.md` with category `best_practice` |
-| Simplify/Harden recurring patterns | Log/update `.learnings/LEARNINGS.md` with `Source: simplify-and-harden` and a stable `Pattern-Key` |
-| Similar to existing entry | Link with `**See Also**`, consider priority bump |
-| Broadly applicable learning | Promote to `CLAUDE.md`, `AGENTS.md`, and/or `.github/copilot-instructions.md` |
-| Workflow improvements | Promote to `AGENTS.md` (OpenClaw workspace) |
-| Tool gotchas | Promote to `TOOLS.md` (OpenClaw workspace) |
-| Behavioral patterns | Promote to `SOUL.md` (OpenClaw workspace) |
-
-## OpenClaw Setup (Recommended)
-
-OpenClaw is the primary platform for this skill. It uses workspace-based prompt injection with automatic skill loading.
-
-### Installation
-
-**Via ClawdHub (recommended):**
-```bash
-clawdhub install self-improving-agent
-```
-
-**Manual:**
-```bash
-git clone https://github.com/peterskoett/self-improving-agent.git ~/.openclaw/skills/self-improving-agent
-```
-
-Remade for openclaw from original repo : https://github.com/pskoett/pskoett-ai-skills - https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/self-improvement
-
-### Workspace Structure
-
-OpenClaw injects these files into every session:
-
-```
-~/.openclaw/workspace/
-├── AGENTS.md # Multi-agent workflows, delegation patterns
-├── SOUL.md # Behavioral guidelines, personality, principles
-├── TOOLS.md # Tool capabilities, integration gotchas
-├── MEMORY.md # Long-term memory (main session only)
-├── memory/ # Daily memory files
-│ └── YYYY-MM-DD.md
-└── .learnings/ # This skill's log files
- ├── LEARNINGS.md
- ├── ERRORS.md
- └── FEATURE_REQUESTS.md
-```
-
-### Create Learning Files
-
-```bash
-mkdir -p ~/.openclaw/workspace/.learnings
-```
-
-Then create the log files (or copy from `assets/`):
-- `LEARNINGS.md` — corrections, knowledge gaps, best practices
-- `ERRORS.md` — command failures, exceptions
-- `FEATURE_REQUESTS.md` — user-requested capabilities
-
-### Promotion Targets
-
-When learnings prove broadly applicable, promote them to workspace files:
-
-| Learning Type | Promote To | Example |
-|---------------|------------|---------|
-| Behavioral patterns | `SOUL.md` | "Be concise, avoid disclaimers" |
-| Workflow improvements | `AGENTS.md` | "Spawn sub-agents for long tasks" |
-| Tool gotchas | `TOOLS.md` | "Git push needs auth configured first" |
-
-### Inter-Session Communication
-
-OpenClaw provides tools to share learnings across sessions:
-
-- **sessions_list** — View active/recent sessions
-- **sessions_history** — Read another session's transcript
-- **sessions_send** — Send a learning to another session
-- **sessions_spawn** — Spawn a sub-agent for background work
-
-### Optional: Enable Hook
-
-For automatic reminders at session start:
-
-```bash
-# Copy hook to OpenClaw hooks directory
-cp -r hooks/openclaw ~/.openclaw/hooks/self-improvement
-
-# Enable it
-openclaw hooks enable self-improvement
-```
-
-See `references/openclaw-integration.md` for complete details.
-
----
-
-## Generic Setup (Other Agents)
-
-For Claude Code, Codex, Copilot, or other agents, create `.learnings/` in your project:
-
-```bash
-mkdir -p .learnings
-```
-
-Copy templates from `assets/` or create files with headers.
-
-### Add reference to agent files AGENTS.md, CLAUDE.md, or .github/copilot-instructions.md to remind yourself to log learnings. (this is an alternative to hook-based reminders)
-
-#### Self-Improvement Workflow
-
-When errors or corrections occur:
-1. Log to `.learnings/ERRORS.md`, `LEARNINGS.md`, or `FEATURE_REQUESTS.md`
-2. Review and promote broadly applicable learnings to:
- - `CLAUDE.md` - project facts and conventions
- - `AGENTS.md` - workflows and automation
- - `.github/copilot-instructions.md` - Copilot context
-
-## Logging Format
-
-### Learning Entry
-
-Append to `.learnings/LEARNINGS.md`:
-
-```markdown
-## [LRN-YYYYMMDD-XXX] category
-
-**Logged**: ISO-8601 timestamp
-**Priority**: low | medium | high | critical
-**Status**: pending
-**Area**: frontend | backend | infra | tests | docs | config
-
-### Summary
-One-line description of what was learned
-
-### Details
-Full context: what happened, what was wrong, what's correct
-
-### Suggested Action
-Specific fix or improvement to make
-
-### Metadata
-- Source: conversation | error | user_feedback
-- Related Files: path/to/file.ext
-- Tags: tag1, tag2
-- See Also: LRN-20250110-001 (if related to existing entry)
-- Pattern-Key: simplify.dead_code | harden.input_validation (optional, for recurring-pattern tracking)
-- Recurrence-Count: 1 (optional)
-- First-Seen: 2025-01-15 (optional)
-- Last-Seen: 2025-01-15 (optional)
-
----
-```
-
-### Error Entry
-
-Append to `.learnings/ERRORS.md`:
-
-```markdown
-## [ERR-YYYYMMDD-XXX] skill_or_command_name
-
-**Logged**: ISO-8601 timestamp
-**Priority**: high
-**Status**: pending
-**Area**: frontend | backend | infra | tests | docs | config
-
-### Summary
-Brief description of what failed
-
-### Error
-```
-Actual error message or output
-```
-
-### Context
-- Command/operation attempted
-- Input or parameters used
-- Environment details if relevant
-
-### Suggested Fix
-If identifiable, what might resolve this
-
-### Metadata
-- Reproducible: yes | no | unknown
-- Related Files: path/to/file.ext
-- See Also: ERR-20250110-001 (if recurring)
-
----
-```
-
-### Feature Request Entry
-
-Append to `.learnings/FEATURE_REQUESTS.md`:
-
-```markdown
-## [FEAT-YYYYMMDD-XXX] capability_name
-
-**Logged**: ISO-8601 timestamp
-**Priority**: medium
-**Status**: pending
-**Area**: frontend | backend | infra | tests | docs | config
-
-### Requested Capability
-What the user wanted to do
-
-### User Context
-Why they needed it, what problem they're solving
-
-### Complexity Estimate
-simple | medium | complex
-
-### Suggested Implementation
-How this could be built, what it might extend
-
-### Metadata
-- Frequency: first_time | recurring
-- Related Features: existing_feature_name
-
----
-```
-
-## ID Generation
-
-Format: `TYPE-YYYYMMDD-XXX`
-- TYPE: `LRN` (learning), `ERR` (error), `FEAT` (feature)
-- YYYYMMDD: Current date
-- XXX: Sequential number or random 3 chars (e.g., `001`, `A7B`)
-
-Examples: `LRN-20250115-001`, `ERR-20250115-A3F`, `FEAT-20250115-002`
-
-## Resolving Entries
-
-When an issue is fixed, update the entry:
-
-1. Change `**Status**: pending` → `**Status**: resolved`
-2. Add resolution block after Metadata:
-
-```markdown
-### Resolution
-- **Resolved**: 2025-01-16T09:00:00Z
-- **Commit/PR**: abc123 or #42
-- **Notes**: Brief description of what was done
-```
-
-Other status values:
-- `in_progress` - Actively being worked on
-- `wont_fix` - Decided not to address (add reason in Resolution notes)
-- `promoted` - Elevated to CLAUDE.md, AGENTS.md, or .github/copilot-instructions.md
-
-## Promoting to Project Memory
-
-When a learning is broadly applicable (not a one-off fix), promote it to permanent project memory.
-
-### When to Promote
-
-- Learning applies across multiple files/features
-- Knowledge any contributor (human or AI) should know
-- Prevents recurring mistakes
-- Documents project-specific conventions
-
-### Promotion Targets
-
-| Target | What Belongs There |
-|--------|-------------------|
-| `CLAUDE.md` | Project facts, conventions, gotchas for all Claude interactions |
-| `AGENTS.md` | Agent-specific workflows, tool usage patterns, automation rules |
-| `.github/copilot-instructions.md` | Project context and conventions for GitHub Copilot |
-| `SOUL.md` | Behavioral guidelines, communication style, principles (OpenClaw workspace) |
-| `TOOLS.md` | Tool capabilities, usage patterns, integration gotchas (OpenClaw workspace) |
-
-### How to Promote
-
-1. **Distill** the learning into a concise rule or fact
-2. **Add** to appropriate section in target file (create file if needed)
-3. **Update** original entry:
- - Change `**Status**: pending` → `**Status**: promoted`
- - Add `**Promoted**: CLAUDE.md`, `AGENTS.md`, or `.github/copilot-instructions.md`
-
-### Promotion Examples
-
-**Learning** (verbose):
-> Project uses pnpm workspaces. Attempted `npm install` but failed.
-> Lock file is `pnpm-lock.yaml`. Must use `pnpm install`.
-
-**In CLAUDE.md** (concise):
-```markdown
-## Build & Dependencies
-- Package manager: pnpm (not npm) - use `pnpm install`
-```
-
-**Learning** (verbose):
-> When modifying API endpoints, must regenerate TypeScript client.
-> Forgetting this causes type mismatches at runtime.
-
-**In AGENTS.md** (actionable):
-```markdown
-## After API Changes
-1. Regenerate client: `pnpm run generate:api`
-2. Check for type errors: `pnpm tsc --noEmit`
-```
-
-## Recurring Pattern Detection
-
-If logging something similar to an existing entry:
-
-1. **Search first**: `grep -r "keyword" .learnings/`
-2. **Link entries**: Add `**See Also**: ERR-20250110-001` in Metadata
-3. **Bump priority** if issue keeps recurring
-4. **Consider systemic fix**: Recurring issues often indicate:
- - Missing documentation (→ promote to CLAUDE.md or .github/copilot-instructions.md)
- - Missing automation (→ add to AGENTS.md)
- - Architectural problem (→ create tech debt ticket)
-
-## Simplify & Harden Feed
-
-Use this workflow to ingest recurring patterns from the `simplify-and-harden`
-skill and turn them into durable prompt guidance.
-
-### Ingestion Workflow
-
-1. Read `simplify_and_harden.learning_loop.candidates` from the task summary.
-2. For each candidate, use `pattern_key` as the stable dedupe key.
-3. Search `.learnings/LEARNINGS.md` for an existing entry with that key:
- - `grep -n "Pattern-Key: <pattern_key>" .learnings/LEARNINGS.md`
-4. If found:
- - Increment `Recurrence-Count`
- - Update `Last-Seen`
- - Add `See Also` links to related entries/tasks
-5. If not found:
- - Create a new `LRN-...` entry
- - Set `Source: simplify-and-harden`
- - Set `Pattern-Key`, `Recurrence-Count: 1`, and `First-Seen`/`Last-Seen`
-
-### Promotion Rule (System Prompt Feedback)
-
-Promote recurring patterns into agent context/system prompt files when all are true:
-
-- `Recurrence-Count >= 3`
-- Seen across at least 2 distinct tasks
-- Occurred within a 30-day window
-
-Promotion targets:
-- `CLAUDE.md`
-- `AGENTS.md`
-- `.github/copilot-instructions.md`
-- `SOUL.md` / `TOOLS.md` for OpenClaw workspace-level guidance when applicable
-
-Write promoted rules as short prevention rules (what to do before/while coding),
-not long incident write-ups.
-
-## Periodic Review
-
-Review `.learnings/` at natural breakpoints:
-
-### When to Review
-- Before starting a new major task
-- After completing a feature
-- When working in an area with past learnings
-- Weekly during active development
-
-### Quick Status Check
-```bash
-# Count pending items
-grep -h "Status\*\*: pending" .learnings/*.md | wc -l
-
-# List pending high-priority items
-grep -B5 "Priority\*\*: high" .learnings/*.md | grep "^## \["
-
-# Find learnings for a specific area
-grep -l "Area\*\*: backend" .learnings/*.md
-```
-
-### Review Actions
-- Resolve fixed items
-- Promote applicable learnings
-- Link related entries
-- Escalate recurring issues
-
-## Detection Triggers
-
-Automatically log when you notice:
-
-**Corrections** (→ learning with `correction` category):
-- "No, that's not right..."
-- "Actually, it should be..."
-- "You're wrong about..."
-- "That's outdated..."
-
-**Feature Requests** (→ feature request):
-- "Can you also..."
-- "I wish you could..."
-- "Is there a way to..."
-- "Why can't you..."
-
-**Knowledge Gaps** (→ learning with `knowledge_gap` category):
-- User provides information you didn't know
-- Documentation you referenced is outdated
-- API behavior differs from your understanding
-
-**Errors** (→ error entry):
-- Command returns non-zero exit code
-- Exception or stack trace
-- Unexpected output or behavior
-- Timeout or connection failure
-
-## Priority Guidelines
-
-| Priority | When to Use |
-|----------|-------------|
-| `critical` | Blocks core functionality, data loss risk, security issue |
-| `high` | Significant impact, affects common workflows, recurring issue |
-| `medium` | Moderate impact, workaround exists |
-| `low` | Minor inconvenience, edge case, nice-to-have |
-
-## Area Tags
-
-Use to filter learnings by codebase region:
-
-| Area | Scope |
-|------|-------|
-| `frontend` | UI, components, client-side code |
-| `backend` | API, services, server-side code |
-| `infra` | CI/CD, deployment, Docker, cloud |
-| `tests` | Test files, testing utilities, coverage |
-| `docs` | Documentation, comments, READMEs |
-| `config` | Configuration files, environment, settings |
-
-## Best Practices
-
-1. **Log immediately** - context is freshest right after the issue
-2. **Be specific** - future agents need to understand quickly
-3. **Include reproduction steps** - especially for errors
-4. **Link related files** - makes fixes easier
-5. **Suggest concrete fixes** - not just "investigate"
-6. **Use consistent categories** - enables filtering
-7. **Promote aggressively** - if in doubt, add to CLAUDE.md or .github/copilot-instructions.md
-8. **Review regularly** - stale learnings lose value
-
-## Gitignore Options
-
-**Keep learnings local** (per-developer):
-```gitignore
-.learnings/
-```
-
-**Track learnings in repo** (team-wide):
-Don't add to .gitignore - learnings become shared knowledge.
-
-**Hybrid** (track templates, ignore entries):
-```gitignore
-.learnings/*.md
-!.learnings/.gitkeep
-```
-
-## Hook Integration
-
-Enable automatic reminders through agent hooks. This is **opt-in** - you must explicitly configure hooks.
-
-### Quick Setup (Claude Code / Codex)
-
-Create `.claude/settings.json` in your project:
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [{
- "matcher": "",
- "hooks": [{
- "type": "command",
- "command": "./skills/self-improvement/scripts/activator.sh"
- }]
- }]
- }
-}
-```
-
-This injects a learning evaluation reminder after each prompt (~50-100 tokens overhead).
-
-### Full Setup (With Error Detection)
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [{
- "matcher": "",
- "hooks": [{
- "type": "command",
- "command": "./skills/self-improvement/scripts/activator.sh"
- }]
- }],
- "PostToolUse": [{
- "matcher": "Bash",
- "hooks": [{
- "type": "command",
- "command": "./skills/self-improvement/scripts/error-detector.sh"
- }]
- }]
- }
-}
-```
-
-### Available Hook Scripts
-
-| Script | Hook Type | Purpose |
-|--------|-----------|---------|
-| `scripts/activator.sh` | UserPromptSubmit | Reminds to evaluate learnings after tasks |
-| `scripts/error-detector.sh` | PostToolUse (Bash) | Triggers on command errors |
-
-See `references/hooks-setup.md` for detailed configuration and troubleshooting.
-
-## Automatic Skill Extraction
-
-When a learning is valuable enough to become a reusable skill, extract it using the provided helper.
-
-### Skill Extraction Criteria
-
-A learning qualifies for skill extraction when ANY of these apply:
-
-| Criterion | Description |
-|-----------|-------------|
-| **Recurring** | Has `See Also` links to 2+ similar issues |
-| **Verified** | Status is `resolved` with working fix |
-| **Non-obvious** | Required actual debugging/investigation to discover |
-| **Broadly applicable** | Not project-specific; useful across codebases |
-| **User-flagged** | User says "save this as a skill" or similar |
-
-### Extraction Workflow
-
-1. **Identify candidate**: Learning meets extraction criteria
-2. **Run helper** (or create manually):
- ```bash
- ./skills/self-improvement/scripts/extract-skill.sh skill-name --dry-run
- ./skills/self-improvement/scripts/extract-skill.sh skill-name
- ```
-3. **Customize SKILL.md**: Fill in template with learning content
-4. **Update learning**: Set status to `promoted_to_skill`, add `Skill-Path`
-5. **Verify**: Read skill in fresh session to ensure it's self-contained
-
-### Manual Extraction
-
-If you prefer manual creation:
-
-1. Create `skills/<skill-name>/SKILL.md`
-2. Use template from `assets/SKILL-TEMPLATE.md`
-3. Follow [Agent Skills spec](https://agentskills.io/specification):
- - YAML frontmatter with `name` and `description`
- - Name must match folder name
- - No README.md inside skill folder
-
-### Extraction Detection Triggers
-
-Watch for these signals that a learning should become a skill:
-
-**In conversation:**
-- "Save this as a skill"
-- "I keep running into this"
-- "This would be useful for other projects"
-- "Remember this pattern"
-
-**In learning entries:**
-- Multiple `See Also` links (recurring issue)
-- High priority + resolved status
-- Category: `best_practice` with broad applicability
-- User feedback praising the solution
-
-### Skill Quality Gates
-
-Before extraction, verify:
-
-- [ ] Solution is tested and working
-- [ ] Description is clear without original context
-- [ ] Code examples are self-contained
-- [ ] No project-specific hardcoded values
-- [ ] Follows skill naming conventions (lowercase, hyphens)
-
-## Multi-Agent Support
-
-This skill works across different AI coding agents with agent-specific activation.
-
-### Claude Code
-
-**Activation**: Hooks (UserPromptSubmit, PostToolUse)
-**Setup**: `.claude/settings.json` with hook configuration
-**Detection**: Automatic via hook scripts
-
-### Codex CLI
-
-**Activation**: Hooks (same pattern as Claude Code)
-**Setup**: `.codex/settings.json` with hook configuration
-**Detection**: Automatic via hook scripts
-
-### GitHub Copilot
-
-**Activation**: Manual (no hook support)
-**Setup**: Add to `.github/copilot-instructions.md`:
-
-```markdown
-## Self-Improvement
-
-After solving non-obvious issues, consider logging to `.learnings/`:
-1. Use format from self-improvement skill
-2. Link related entries with See Also
-3. Promote high-value learnings to skills
-
-Ask in chat: "Should I log this as a learning?"
-```
-
-**Detection**: Manual review at session end
-
-### OpenClaw
-
-**Activation**: Workspace injection + inter-agent messaging
-**Setup**: See "OpenClaw Setup" section above
-**Detection**: Via session tools and workspace files
-
-### Agent-Agnostic Guidance
-
-Regardless of agent, apply self-improvement when you:
-
-1. **Discover something non-obvious** - solution wasn't immediate
-2. **Correct yourself** - initial approach was wrong
-3. **Learn project conventions** - discovered undocumented patterns
-4. **Hit unexpected errors** - especially if diagnosis was difficult
-5. **Find better approaches** - improved on your original solution
-
-### Copilot Chat Integration
-
-For Copilot users, add this to your prompts when relevant:
-
-> After completing this task, evaluate if any learnings should be logged to `.learnings/` using the self-improvement skill format.
-
-Or use quick prompts:
-- "Log this to learnings"
-- "Create a skill from this solution"
-- "Check .learnings/ for related issues"
diff --git a/workspace/skills/self-improving-agent/_meta.json b/workspace/skills/self-improving-agent/_meta.json
deleted file mode 100644
index d53726a..0000000
--- a/workspace/skills/self-improving-agent/_meta.json
+++ /dev/null
@@ -1,6 +0,0 @@
-{
- "ownerId": "kn70cjr952qdec1nx70zs6wefn7ynq2t",
- "slug": "self-improving-agent",
- "version": "3.0.1",
- "publishedAt": 1773230308177
-}
\ No newline at end of file
diff --git a/workspace/skills/self-improving-agent/assets/LEARNINGS.md b/workspace/skills/self-improving-agent/assets/LEARNINGS.md
deleted file mode 100644
index 6993f9b..0000000
--- a/workspace/skills/self-improving-agent/assets/LEARNINGS.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Learnings
-
-Corrections, insights, and knowledge gaps captured during development.
-
-**Categories**: correction | insight | knowledge_gap | best_practice
-**Areas**: frontend | backend | infra | tests | docs | config
-**Statuses**: pending | in_progress | resolved | wont_fix | promoted | promoted_to_skill
-
-## Status Definitions
-
-| Status | Meaning |
-|--------|---------|
-| `pending` | Not yet addressed |
-| `in_progress` | Actively being worked on |
-| `resolved` | Issue fixed or knowledge integrated |
-| `wont_fix` | Decided not to address (reason in Resolution) |
-| `promoted` | Elevated to CLAUDE.md, AGENTS.md, or copilot-instructions.md |
-| `promoted_to_skill` | Extracted as a reusable skill |
-
-## Skill Extraction Fields
-
-When a learning is promoted to a skill, add these fields:
-
-```markdown
-**Status**: promoted_to_skill
-**Skill-Path**: skills/skill-name
-```
-
-Example:
-```markdown
-## [LRN-20250115-001] best_practice
-
-**Logged**: 2025-01-15T10:00:00Z
-**Priority**: high
-**Status**: promoted_to_skill
-**Skill-Path**: skills/docker-m1-fixes
-**Area**: infra
-
-### Summary
-Docker build fails on Apple Silicon due to platform mismatch
-...
-```
-
----
-
diff --git a/workspace/skills/self-improving-agent/assets/SKILL-TEMPLATE.md b/workspace/skills/self-improving-agent/assets/SKILL-TEMPLATE.md
deleted file mode 100644
index 0162134..0000000
--- a/workspace/skills/self-improving-agent/assets/SKILL-TEMPLATE.md
+++ /dev/null
@@ -1,177 +0,0 @@
-# Skill Template
-
-Template for creating skills extracted from learnings. Copy and customize.
-
----
-
-## SKILL.md Template
-
-```markdown
----
-name: skill-name-here
-description: "Concise description of when and why to use this skill. Include trigger conditions."
----
-
-# Skill Name
-
-Brief introduction explaining the problem this skill solves and its origin.
-
-## Quick Reference
-
-| Situation | Action |
-|-----------|--------|
-| [Trigger 1] | [Action 1] |
-| [Trigger 2] | [Action 2] |
-
-## Background
-
-Why this knowledge matters. What problems it prevents. Context from the original learning.
-
-## Solution
-
-### Step-by-Step
-
-1. First step with code or command
-2. Second step
-3. Verification step
-
-### Code Example
-
-\`\`\`language
-// Example code demonstrating the solution
-\`\`\`
-
-## Common Variations
-
-- **Variation A**: Description and how to handle
-- **Variation B**: Description and how to handle
-
-## Gotchas
-
-- Warning or common mistake #1
-- Warning or common mistake #2
-
-## Related
-
-- Link to related documentation
-- Link to related skill
-
-## Source
-
-Extracted from learning entry.
-- **Learning ID**: LRN-YYYYMMDD-XXX
-- **Original Category**: correction | insight | knowledge_gap | best_practice
-- **Extraction Date**: YYYY-MM-DD
-```
-
----
-
-## Minimal Template
-
-For simple skills that don't need all sections:
-
-```markdown
----
-name: skill-name-here
-description: "What this skill does and when to use it."
----
-
-# Skill Name
-
-[Problem statement in one sentence]
-
-## Solution
-
-[Direct solution with code/commands]
-
-## Source
-
-- Learning ID: LRN-YYYYMMDD-XXX
-```
-
----
-
-## Template with Scripts
-
-For skills that include executable helpers:
-
-```markdown
----
-name: skill-name-here
-description: "What this skill does and when to use it."
----
-
-# Skill Name
-
-[Introduction]
-
-## Quick Reference
-
-| Command | Purpose |
-|---------|---------|
-| `./scripts/helper.sh` | [What it does] |
-| `./scripts/validate.sh` | [What it does] |
-
-## Usage
-
-### Automated (Recommended)
-
-\`\`\`bash
-./skills/skill-name/scripts/helper.sh [args]
-\`\`\`
-
-### Manual Steps
-
-1. Step one
-2. Step two
-
-## Scripts
-
-| Script | Description |
-|--------|-------------|
-| `scripts/helper.sh` | Main utility |
-| `scripts/validate.sh` | Validation checker |
-
-## Source
-
-- Learning ID: LRN-YYYYMMDD-XXX
-```
-
----
-
-## Naming Conventions
-
-- **Skill name**: lowercase, hyphens for spaces
- - Good: `docker-m1-fixes`, `api-timeout-patterns`
- - Bad: `Docker_M1_Fixes`, `APITimeoutPatterns`
-
-- **Description**: Start with action verb, mention trigger
- - Good: "Handles Docker build failures on Apple Silicon. Use when builds fail with platform mismatch."
- - Bad: "Docker stuff"
-
-- **Files**:
- - `SKILL.md` - Required, main documentation
- - `scripts/` - Optional, executable code
- - `references/` - Optional, detailed docs
- - `assets/` - Optional, templates
-
----
-
-## Extraction Checklist
-
-Before creating a skill from a learning:
-
-- [ ] Learning is verified (status: resolved)
-- [ ] Solution is broadly applicable (not one-off)
-- [ ] Content is complete (has all needed context)
-- [ ] Name follows conventions
-- [ ] Description is concise but informative
-- [ ] Quick Reference table is actionable
-- [ ] Code examples are tested
-- [ ] Source learning ID is recorded
-
-After creating:
-
-- [ ] Update original learning with `promoted_to_skill` status
-- [ ] Add `Skill-Path: skills/skill-name` to learning metadata
-- [ ] Test skill by reading it in a fresh session
diff --git a/workspace/skills/self-improving-agent/hooks/openclaw/HOOK.md b/workspace/skills/self-improving-agent/hooks/openclaw/HOOK.md
deleted file mode 100644
index df67405..0000000
--- a/workspace/skills/self-improving-agent/hooks/openclaw/HOOK.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-name: self-improvement
-description: "Injects self-improvement reminder during agent bootstrap"
-metadata: {"openclaw":{"emoji":"🧠","events":["agent:bootstrap"]}}
----
-
-# Self-Improvement Hook
-
-Injects a reminder to evaluate learnings during agent bootstrap.
-
-## What It Does
-
-- Fires on `agent:bootstrap` (before workspace files are injected)
-- Adds a reminder block to check `.learnings/` for relevant entries
-- Prompts the agent to log corrections, errors, and discoveries
-
-## Configuration
-
-No configuration needed. Enable with:
-
-```bash
-openclaw hooks enable self-improvement
-```
diff --git a/workspace/skills/self-improving-agent/hooks/openclaw/handler.js b/workspace/skills/self-improving-agent/hooks/openclaw/handler.js
deleted file mode 100644
index 73278ea..0000000
--- a/workspace/skills/self-improving-agent/hooks/openclaw/handler.js
+++ /dev/null
@@ -1,56 +0,0 @@
-/**
- * Self-Improvement Hook for OpenClaw
- *
- * Injects a reminder to evaluate learnings during agent bootstrap.
- * Fires on agent:bootstrap event before workspace files are injected.
- */
-
-const REMINDER_CONTENT = `
-## Self-Improvement Reminder
-
-After completing tasks, evaluate if any learnings should be captured:
-
-**Log when:**
-- User corrects you → \`.learnings/LEARNINGS.md\`
-- Command/operation fails → \`.learnings/ERRORS.md\`
-- User wants missing capability → \`.learnings/FEATURE_REQUESTS.md\`
-- You discover your knowledge was wrong → \`.learnings/LEARNINGS.md\`
-- You find a better approach → \`.learnings/LEARNINGS.md\`
-
-**Promote when pattern is proven:**
-- Behavioral patterns → \`SOUL.md\`
-- Workflow improvements → \`AGENTS.md\`
-- Tool gotchas → \`TOOLS.md\`
-
-Keep entries simple: date, title, what happened, what to do differently.
-`.trim();
-
-const handler = async (event) => {
- // Safety checks for event structure
- if (!event || typeof event !== 'object') {
- return;
- }
-
- // Only handle agent:bootstrap events
- if (event.type !== 'agent' || event.action !== 'bootstrap') {
- return;
- }
-
- // Safety check for context
- if (!event.context || typeof event.context !== 'object') {
- return;
- }
-
- // Inject the reminder as a virtual bootstrap file
- // Check that bootstrapFiles is an array before pushing
- if (Array.isArray(event.context.bootstrapFiles)) {
- event.context.bootstrapFiles.push({
- path: 'SELF_IMPROVEMENT_REMINDER.md',
- content: REMINDER_CONTENT,
- virtual: true,
- });
- }
-};
-
-module.exports = handler;
-module.exports.default = handler;
diff --git a/workspace/skills/self-improving-agent/hooks/openclaw/handler.ts b/workspace/skills/self-improving-agent/hooks/openclaw/handler.ts
deleted file mode 100644
index 9ec23f3..0000000
--- a/workspace/skills/self-improving-agent/hooks/openclaw/handler.ts
+++ /dev/null
@@ -1,62 +0,0 @@
-/**
- * Self-Improvement Hook for OpenClaw
- *
- * Injects a reminder to evaluate learnings during agent bootstrap.
- * Fires on agent:bootstrap event before workspace files are injected.
- */
-
-import type { HookHandler } from 'openclaw/hooks';
-
-const REMINDER_CONTENT = `## Self-Improvement Reminder
-
-After completing tasks, evaluate if any learnings should be captured:
-
-**Log when:**
-- User corrects you → \`.learnings/LEARNINGS.md\`
-- Command/operation fails → \`.learnings/ERRORS.md\`
-- User wants missing capability → \`.learnings/FEATURE_REQUESTS.md\`
-- You discover your knowledge was wrong → \`.learnings/LEARNINGS.md\`
-- You find a better approach → \`.learnings/LEARNINGS.md\`
-
-**Promote when pattern is proven:**
-- Behavioral patterns → \`SOUL.md\`
-- Workflow improvements → \`AGENTS.md\`
-- Tool gotchas → \`TOOLS.md\`
-
-Keep entries simple: date, title, what happened, what to do differently.`;
-
-const handler: HookHandler = async (event) => {
- // Safety checks for event structure
- if (!event || typeof event !== 'object') {
- return;
- }
-
- // Only handle agent:bootstrap events
- if (event.type !== 'agent' || event.action !== 'bootstrap') {
- return;
- }
-
- // Safety check for context
- if (!event.context || typeof event.context !== 'object') {
- return;
- }
-
- // Skip sub-agent sessions to avoid bootstrap issues
- // Sub-agents have sessionKey patterns like "agent:main:subagent:..."
- const sessionKey = event.sessionKey || '';
- if (sessionKey.includes(':subagent:')) {
- return;
- }
-
- // Inject the reminder as a virtual bootstrap file
- // Check that bootstrapFiles is an array before pushing
- if (Array.isArray(event.context.bootstrapFiles)) {
- event.context.bootstrapFiles.push({
- path: 'SELF_IMPROVEMENT_REMINDER.md',
- content: REMINDER_CONTENT,
- virtual: true,
- });
- }
-};
-
-export default handler;
diff --git a/workspace/skills/self-improving-agent/references/examples.md b/workspace/skills/self-improving-agent/references/examples.md
deleted file mode 100644
index 1c1db15..0000000
--- a/workspace/skills/self-improving-agent/references/examples.md
+++ /dev/null
@@ -1,374 +0,0 @@
-# Entry Examples
-
-Concrete examples of well-formatted entries with all fields.
-
-## Learning: Correction
-
-```markdown
-## [LRN-20250115-001] correction
-
-**Logged**: 2025-01-15T10:30:00Z
-**Priority**: high
-**Status**: pending
-**Area**: tests
-
-### Summary
-Incorrectly assumed pytest fixtures are scoped to function by default
-
-### Details
-When writing test fixtures, I assumed all fixtures were function-scoped.
-User corrected that while function scope is the default, the codebase
-convention uses module-scoped fixtures for database connections to
-improve test performance.
-
-### Suggested Action
-When creating fixtures that involve expensive setup (DB, network),
-check existing fixtures for scope patterns before defaulting to function scope.
-
-### Metadata
-- Source: user_feedback
-- Related Files: tests/conftest.py
-- Tags: pytest, testing, fixtures
-
----
-```
-
-## Learning: Knowledge Gap (Resolved)
-
-```markdown
-## [LRN-20250115-002] knowledge_gap
-
-**Logged**: 2025-01-15T14:22:00Z
-**Priority**: medium
-**Status**: resolved
-**Area**: config
-
-### Summary
-Project uses pnpm not npm for package management
-
-### Details
-Attempted to run `npm install` but project uses pnpm workspaces.
-Lock file is `pnpm-lock.yaml`, not `package-lock.json`.
-
-### Suggested Action
-Check for `pnpm-lock.yaml` or `pnpm-workspace.yaml` before assuming npm.
-Use `pnpm install` for this project.
-
-### Metadata
-- Source: error
-- Related Files: pnpm-lock.yaml, pnpm-workspace.yaml
-- Tags: package-manager, pnpm, setup
-
-### Resolution
-- **Resolved**: 2025-01-15T14:30:00Z
-- **Commit/PR**: N/A - knowledge update
-- **Notes**: Added to CLAUDE.md for future reference
-
----
-```
-
-## Learning: Promoted to CLAUDE.md
-
-```markdown
-## [LRN-20250115-003] best_practice
-
-**Logged**: 2025-01-15T16:00:00Z
-**Priority**: high
-**Status**: promoted
-**Promoted**: CLAUDE.md
-**Area**: backend
-
-### Summary
-API responses must include correlation ID from request headers
-
-### Details
-All API responses should echo back the X-Correlation-ID header from
-the request. This is required for distributed tracing. Responses
-without this header break the observability pipeline.
-
-### Suggested Action
-Always include correlation ID passthrough in API handlers.
-
-### Metadata
-- Source: user_feedback
-- Related Files: src/middleware/correlation.ts
-- Tags: api, observability, tracing
-
----
-```
-
-## Learning: Promoted to AGENTS.md
-
-```markdown
-## [LRN-20250116-001] best_practice
-
-**Logged**: 2025-01-16T09:00:00Z
-**Priority**: high
-**Status**: promoted
-**Promoted**: AGENTS.md
-**Area**: backend
-
-### Summary
-Must regenerate API client after OpenAPI spec changes
-
-### Details
-When modifying API endpoints, the TypeScript client must be regenerated.
-Forgetting this causes type mismatches that only appear at runtime.
-The generate script also runs validation.
-
-### Suggested Action
-Add to agent workflow: after any API changes, run `pnpm run generate:api`.
-
-### Metadata
-- Source: error
-- Related Files: openapi.yaml, src/client/api.ts
-- Tags: api, codegen, typescript
-
----
-```
-
-## Error Entry
-
-```markdown
-## [ERR-20250115-A3F] docker_build
-
-**Logged**: 2025-01-15T09:15:00Z
-**Priority**: high
-**Status**: pending
-**Area**: infra
-
-### Summary
-Docker build fails on M1 Mac due to platform mismatch
-
-### Error
-```
-error: failed to solve: python:3.11-slim: no match for platform linux/arm64
-```
-
-### Context
-- Command: `docker build -t myapp .`
-- Dockerfile uses `FROM python:3.11-slim`
-- Running on Apple Silicon (M1/M2)
-
-### Suggested Fix
-Add platform flag: `docker build --platform linux/amd64 -t myapp .`
-Or update Dockerfile: `FROM --platform=linux/amd64 python:3.11-slim`
-
-### Metadata
-- Reproducible: yes
-- Related Files: Dockerfile
-
----
-```
-
-## Error Entry: Recurring Issue
-
-```markdown
-## [ERR-20250120-B2C] api_timeout
-
-**Logged**: 2025-01-20T11:30:00Z
-**Priority**: critical
-**Status**: pending
-**Area**: backend
-
-### Summary
-Third-party payment API timeout during checkout
-
-### Error
-```
-TimeoutError: Request to payments.example.com timed out after 30000ms
-```
-
-### Context
-- Command: POST /api/checkout
-- Timeout set to 30s
-- Occurs during peak hours (lunch, evening)
-
-### Suggested Fix
-Implement retry with exponential backoff. Consider circuit breaker pattern.
-
-### Metadata
-- Reproducible: yes (during peak hours)
-- Related Files: src/services/payment.ts
-- See Also: ERR-20250115-X1Y, ERR-20250118-Z3W
-
----
-```
-
-## Feature Request
-
-```markdown
-## [FEAT-20250115-001] export_to_csv
-
-**Logged**: 2025-01-15T16:45:00Z
-**Priority**: medium
-**Status**: pending
-**Area**: backend
-
-### Requested Capability
-Export analysis results to CSV format
-
-### User Context
-User runs weekly reports and needs to share results with non-technical
-stakeholders in Excel. Currently copies output manually.
-
-### Complexity Estimate
-simple
-
-### Suggested Implementation
-Add `--output csv` flag to the analyze command. Use standard csv module.
-Could extend existing `--output json` pattern.
-
-### Metadata
-- Frequency: recurring
-- Related Features: analyze command, json output
-
----
-```
-
-## Feature Request: Resolved
-
-```markdown
-## [FEAT-20250110-002] dark_mode
-
-**Logged**: 2025-01-10T14:00:00Z
-**Priority**: low
-**Status**: resolved
-**Area**: frontend
-
-### Requested Capability
-Dark mode support for the dashboard
-
-### User Context
-User works late hours and finds the bright interface straining.
-Several other users have mentioned this informally.
-
-### Complexity Estimate
-medium
-
-### Suggested Implementation
-Use CSS variables for colors. Add toggle in user settings.
-Consider system preference detection.
-
-### Metadata
-- Frequency: recurring
-- Related Features: user settings, theme system
-
-### Resolution
-- **Resolved**: 2025-01-18T16:00:00Z
-- **Commit/PR**: #142
-- **Notes**: Implemented with system preference detection and manual toggle
-
----
-```
-
-## Learning: Promoted to Skill
-
-```markdown
-## [LRN-20250118-001] best_practice
-
-**Logged**: 2025-01-18T11:00:00Z
-**Priority**: high
-**Status**: promoted_to_skill
-**Skill-Path**: skills/docker-m1-fixes
-**Area**: infra
-
-### Summary
-Docker build fails on Apple Silicon due to platform mismatch
-
-### Details
-When building Docker images on M1/M2 Macs, the build fails because
-the base image doesn't have an ARM64 variant. This is a common issue
-that affects many developers.
-
-### Suggested Action
-Add `--platform linux/amd64` to docker build command, or use
-`FROM --platform=linux/amd64` in Dockerfile.
-
-### Metadata
-- Source: error
-- Related Files: Dockerfile
-- Tags: docker, arm64, m1, apple-silicon
-- See Also: ERR-20250115-A3F, ERR-20250117-B2D
-
----
-```
-
-## Extracted Skill Example
-
-When the above learning is extracted as a skill, it becomes:
-
-**File**: `skills/docker-m1-fixes/SKILL.md`
-
-```markdown
----
-name: docker-m1-fixes
-description: "Fixes Docker build failures on Apple Silicon (M1/M2). Use when docker build fails with platform mismatch errors."
----
-
-# Docker M1 Fixes
-
-Solutions for Docker build issues on Apple Silicon Macs.
-
-## Quick Reference
-
-| Error | Fix |
-|-------|-----|
-| `no match for platform linux/arm64` | Add `--platform linux/amd64` to build |
-| Image runs but crashes | Use emulation or find ARM-compatible base |
-
-## The Problem
-
-Many Docker base images don't have ARM64 variants. When building on
-Apple Silicon (M1/M2/M3), Docker attempts to pull ARM64 images by
-default, causing platform mismatch errors.
-
-## Solutions
-
-### Option 1: Build Flag (Recommended)
-
-Add platform flag to your build command:
-
-\`\`\`bash
-docker build --platform linux/amd64 -t myapp .
-\`\`\`
-
-### Option 2: Dockerfile Modification
-
-Specify platform in the FROM instruction:
-
-\`\`\`dockerfile
-FROM --platform=linux/amd64 python:3.11-slim
-\`\`\`
-
-### Option 3: Docker Compose
-
-Add platform to your service:
-
-\`\`\`yaml
-services:
- app:
- platform: linux/amd64
- build: .
-\`\`\`
-
-## Trade-offs
-
-| Approach | Pros | Cons |
-|----------|------|------|
-| Build flag | No file changes | Must remember flag |
-| Dockerfile | Explicit, versioned | Affects all builds |
-| Compose | Convenient for dev | Requires compose |
-
-## Performance Note
-
-Running AMD64 images on ARM64 uses Rosetta 2 emulation. This works
-for development but may be slower. For production, find ARM-native
-alternatives when possible.
-
-## Source
-
-- Learning ID: LRN-20250118-001
-- Category: best_practice
-- Extraction Date: 2025-01-18
-```
diff --git a/workspace/skills/self-improving-agent/references/hooks-setup.md b/workspace/skills/self-improving-agent/references/hooks-setup.md
deleted file mode 100644
index 08b5dd1..0000000
--- a/workspace/skills/self-improving-agent/references/hooks-setup.md
+++ /dev/null
@@ -1,223 +0,0 @@
-# Hook Setup Guide
-
-Configure automatic self-improvement triggers for AI coding agents.
-
-## Overview
-
-Hooks enable proactive learning capture by injecting reminders at key moments:
-- **UserPromptSubmit**: Reminder after each prompt to evaluate learnings
-- **PostToolUse (Bash)**: Error detection when commands fail
-
-## Claude Code Setup
-
-### Option 1: Project-Level Configuration
-
-Create `.claude/settings.json` in your project root:
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [
- {
- "matcher": "",
- "hooks": [
- {
- "type": "command",
- "command": "./skills/self-improvement/scripts/activator.sh"
- }
- ]
- }
- ],
- "PostToolUse": [
- {
- "matcher": "Bash",
- "hooks": [
- {
- "type": "command",
- "command": "./skills/self-improvement/scripts/error-detector.sh"
- }
- ]
- }
- ]
- }
-}
-```
-
-### Option 2: User-Level Configuration
-
-Add to `~/.claude/settings.json` for global activation:
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [
- {
- "matcher": "",
- "hooks": [
- {
- "type": "command",
- "command": "~/.claude/skills/self-improvement/scripts/activator.sh"
- }
- ]
- }
- ]
- }
-}
-```
-
-### Minimal Setup (Activator Only)
-
-For lower overhead, use only the UserPromptSubmit hook:
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [
- {
- "matcher": "",
- "hooks": [
- {
- "type": "command",
- "command": "./skills/self-improvement/scripts/activator.sh"
- }
- ]
- }
- ]
- }
-}
-```
-
-## Codex CLI Setup
-
-Codex uses the same hook system as Claude Code. Create `.codex/settings.json`:
-
-```json
-{
- "hooks": {
- "UserPromptSubmit": [
- {
- "matcher": "",
- "hooks": [
- {
- "type": "command",
- "command": "./skills/self-improvement/scripts/activator.sh"
- }
- ]
- }
- ]
- }
-}
-```
-
-## GitHub Copilot Setup
-
-Copilot doesn't support hooks directly. Instead, add guidance to `.github/copilot-instructions.md`:
-
-```markdown
-## Self-Improvement
-
-After completing tasks that involved:
-- Debugging non-obvious issues
-- Discovering workarounds
-- Learning project-specific patterns
-- Resolving unexpected errors
-
-Consider logging the learning to `.learnings/` using the format from the self-improvement skill.
-
-For high-value learnings that would benefit other sessions, consider skill extraction.
-```
-
-## Verification
-
-### Test Activator Hook
-
-1. Enable the hook configuration
-2. Start a new Claude Code session
-3. Send any prompt
-4. Verify you see `<self-improvement-reminder>` in the context
-
-### Test Error Detector Hook
-
-1. Enable PostToolUse hook for Bash
-2. Run a command that fails: `ls /nonexistent/path`
-3. Verify you see `<error-detected>` reminder
-
-### Dry Run Extract Script
-
-```bash
-./skills/self-improvement/scripts/extract-skill.sh test-skill --dry-run
-```
-
-Expected output shows the skill scaffold that would be created.
-
-## Troubleshooting
-
-### Hook Not Triggering
-
-1. **Check script permissions**: `chmod +x scripts/*.sh`
-2. **Verify path**: Use absolute paths or paths relative to project root
-3. **Check settings location**: Project vs user-level settings
-4. **Restart session**: Hooks are loaded at session start
-
-### Permission Denied
-
-```bash
-chmod +x ./skills/self-improvement/scripts/activator.sh
-chmod +x ./skills/self-improvement/scripts/error-detector.sh
-chmod +x ./skills/self-improvement/scripts/extract-skill.sh
-```
-
-### Script Not Found
-
-If using relative paths, ensure you're in the correct directory or use absolute paths:
-
-```json
-{
- "command": "/absolute/path/to/skills/self-improvement/scripts/activator.sh"
-}
-```
-
-### Too Much Overhead
-
-If the activator feels intrusive:
-
-1. **Use minimal setup**: Only UserPromptSubmit, skip PostToolUse
-2. **Add matcher filter**: Only trigger for certain prompts:
-
-```json
-{
- "matcher": "fix|debug|error|issue",
- "hooks": [...]
-}
-```
-
-## Hook Output Budget
-
-The activator is designed to be lightweight:
-- **Target**: ~50-100 tokens per activation
-- **Content**: Structured reminder, not verbose instructions
-- **Format**: XML tags for easy parsing
-
-If you need to reduce overhead further, you can edit `activator.sh` to output less text.
-
-## Security Considerations
-
-- Hook scripts run with the same permissions as Claude Code
-- Scripts only output text; they don't modify files or run commands
-- Error detector reads `CLAUDE_TOOL_OUTPUT` environment variable
-- All scripts are opt-in (you must configure them explicitly)
-
-## Disabling Hooks
-
-To temporarily disable without removing configuration:
-
-1. **Comment out in settings**:
-```json
-{
- "hooks": {
- // "UserPromptSubmit": [...]
- }
-}
-```
-
-2. **Or delete the settings file**: Hooks won't run without configuration
diff --git a/workspace/skills/self-improving-agent/references/openclaw-integration.md b/workspace/skills/self-improving-agent/references/openclaw-integration.md
deleted file mode 100644
index 09f0193..0000000
--- a/workspace/skills/self-improving-agent/references/openclaw-integration.md
+++ /dev/null
@@ -1,248 +0,0 @@
-# OpenClaw Integration
-
-Complete setup and usage guide for integrating the self-improvement skill with OpenClaw.
-
-## Overview
-
-OpenClaw uses workspace-based prompt injection combined with event-driven hooks. Context is injected from workspace files at session start, and hooks can trigger on lifecycle events.
-
-## Workspace Structure
-
-```
-~/.openclaw/
-├── workspace/ # Working directory
-│ ├── AGENTS.md # Multi-agent coordination patterns
-│ ├── SOUL.md # Behavioral guidelines and personality
-│ ├── TOOLS.md # Tool capabilities and gotchas
-│ ├── MEMORY.md # Long-term memory (main session only)
-│ └── memory/ # Daily memory files
-│ └── YYYY-MM-DD.md
-├── skills/ # Installed skills
-│ └── <skill-name>/
-│ └── SKILL.md
-└── hooks/ # Custom hooks
- └── <hook-name>/
- ├── HOOK.md
- └── handler.ts
-```
-
-## Quick Setup
-
-### 1. Install the Skill
-
-```bash
-clawdhub install self-improving-agent
-```
-
-Or copy manually:
-
-```bash
-cp -r self-improving-agent ~/.openclaw/skills/
-```
-
-### 2. Install the Hook (Optional)
-
-Copy the hook to OpenClaw's hooks directory:
-
-```bash
-cp -r hooks/openclaw ~/.openclaw/hooks/self-improvement
-```
-
-Enable the hook:
-
-```bash
-openclaw hooks enable self-improvement
-```
-
-### 3. Create Learning Files
-
-Create the `.learnings/` directory in your workspace:
-
-```bash
-mkdir -p ~/.openclaw/workspace/.learnings
-```
-
-Or in the skill directory:
-
-```bash
-mkdir -p ~/.openclaw/skills/self-improving-agent/.learnings
-```
-
-## Injected Prompt Files
-
-### AGENTS.md
-
-Purpose: Multi-agent workflows and delegation patterns.
-
-```markdown
-# Agent Coordination
-
-## Delegation Rules
-- Use explore agent for open-ended codebase questions
-- Spawn sub-agents for long-running tasks
-- Use sessions_send for cross-session communication
-
-## Session Handoff
-When delegating to another session:
-1. Provide full context in the handoff message
-2. Include relevant file paths
-3. Specify expected output format
-```
-
-### SOUL.md
-
-Purpose: Behavioral guidelines and communication style.
-
-```markdown
-# Behavioral Guidelines
-
-## Communication Style
-- Be direct and concise
-- Avoid unnecessary caveats and disclaimers
-- Use technical language appropriate to context
-
-## Error Handling
-- Admit mistakes promptly
-- Provide corrected information immediately
-- Log significant errors to learnings
-```
-
-### TOOLS.md
-
-Purpose: Tool capabilities, integration gotchas, local configuration.
-
-```markdown
-# Tool Knowledge
-
-## Self-Improvement Skill
-Log learnings to `.learnings/` for continuous improvement.
-
-## Local Tools
-- Document tool-specific gotchas here
-- Note authentication requirements
-- Track integration quirks
-```
-
-## Learning Workflow
-
-### Capturing Learnings
-
-1. **In-session**: Log to `.learnings/` as usual
-2. **Cross-session**: Promote to workspace files
-
-### Promotion Decision Tree
-
-```
-Is the learning project-specific?
-├── Yes → Keep in .learnings/
-└── No → Is it behavioral/style-related?
- ├── Yes → Promote to SOUL.md
- └── No → Is it tool-related?
- ├── Yes → Promote to TOOLS.md
- └── No → Promote to AGENTS.md (workflow)
-```
-
-### Promotion Format Examples
-
-**From learning:**
-> Git push to GitHub fails without auth configured - triggers desktop prompt
-
-**To TOOLS.md:**
-```markdown
-## Git
-- Don't push without confirming auth is configured
-- Use `gh auth status` to check GitHub CLI auth
-```
-
-## Inter-Agent Communication
-
-OpenClaw provides tools for cross-session communication:
-
-### sessions_list
-
-View active and recent sessions:
-```
-sessions_list(activeMinutes=30, messageLimit=3)
-```
-
-### sessions_history
-
-Read transcript from another session:
-```
-sessions_history(sessionKey="session-id", limit=50)
-```
-
-### sessions_send
-
-Send message to another session:
-```
-sessions_send(sessionKey="session-id", message="Learning: API requires X-Custom-Header")
-```
-
-### sessions_spawn
-
-Spawn a background sub-agent:
-```
-sessions_spawn(task="Research X and report back", label="research")
-```
-
-## Available Hook Events
-
-| Event | When It Fires |
-|-------|---------------|
-| `agent:bootstrap` | Before workspace files inject |
-| `command:new` | When `/new` command issued |
-| `command:reset` | When `/reset` command issued |
-| `command:stop` | When `/stop` command issued |
-| `gateway:startup` | When gateway starts |
-
-## Detection Triggers
-
-### Standard Triggers
-- User corrections ("No, that's wrong...")
-- Command failures (non-zero exit codes)
-- API errors
-- Knowledge gaps
-
-### OpenClaw-Specific Triggers
-
-| Trigger | Action |
-|---------|--------|
-| Tool call error | Log to TOOLS.md with tool name |
-| Session handoff confusion | Log to AGENTS.md with delegation pattern |
-| Model behavior surprise | Log to SOUL.md with expected vs actual |
-| Skill issue | Log to .learnings/ or report upstream |
-
-## Verification
-
-Check hook is registered:
-
-```bash
-openclaw hooks list
-```
-
-Check skill is loaded:
-
-```bash
-openclaw status
-```
-
-## Troubleshooting
-
-### Hook not firing
-
-1. Ensure hooks enabled in config
-2. Restart gateway after config changes
-3. Check gateway logs for errors
-
-### Learnings not persisting
-
-1. Verify `.learnings/` directory exists
-2. Check file permissions
-3. Ensure workspace path is configured correctly
-
-### Skill not loading
-
-1. Check skill is in skills directory
-2. Verify SKILL.md has correct frontmatter
-3. Run `openclaw status` to see loaded skills
diff --git a/workspace/skills/self-improving-agent/scripts/activator.sh b/workspace/skills/self-improving-agent/scripts/activator.sh
deleted file mode 100644
index 29eec22..0000000
--- a/workspace/skills/self-improving-agent/scripts/activator.sh
+++ /dev/null
@@ -1,20 +0,0 @@
-#!/bin/bash
-# Self-Improvement Activator Hook
-# Triggers on UserPromptSubmit to remind Claude about learning capture
-# Keep output minimal (~50-100 tokens) to minimize overhead
-
-set -e
-
-# Output reminder as system context
-cat << 'EOF'
-<self-improvement-reminder>
-After completing this task, evaluate if extractable knowledge emerged:
-- Non-obvious solution discovered through investigation?
-- Workaround for unexpected behavior?
-- Project-specific pattern learned?
-- Error required debugging to resolve?
-
-If yes: Log to .learnings/ using the self-improvement skill format.
-If high-value (recurring, broadly applicable): Consider skill extraction.
-</self-improvement-reminder>
-EOF
diff --git a/workspace/skills/self-improving-agent/scripts/error-detector.sh b/workspace/skills/self-improving-agent/scripts/error-detector.sh
deleted file mode 100644
index 3c310dd..0000000
--- a/workspace/skills/self-improving-agent/scripts/error-detector.sh
+++ /dev/null
@@ -1,55 +0,0 @@
-#!/bin/bash
-# Self-Improvement Error Detector Hook
-# Triggers on PostToolUse for Bash to detect command failures
-# Reads CLAUDE_TOOL_OUTPUT environment variable
-
-set -e
-
-# Check if tool output indicates an error
-# CLAUDE_TOOL_OUTPUT contains the result of the tool execution
-OUTPUT="${CLAUDE_TOOL_OUTPUT:-}"
-
-# Patterns indicating errors (case-insensitive matching)
-ERROR_PATTERNS=(
- "error:"
- "Error:"
- "ERROR:"
- "failed"
- "FAILED"
- "command not found"
- "No such file"
- "Permission denied"
- "fatal:"
- "Exception"
- "Traceback"
- "npm ERR!"
- "ModuleNotFoundError"
- "SyntaxError"
- "TypeError"
- "exit code"
- "non-zero"
-)
-
-# Check if output contains any error pattern
-contains_error=false
-for pattern in "${ERROR_PATTERNS[@]}"; do
- if [[ "$OUTPUT" == *"$pattern"* ]]; then
- contains_error=true
- break
- fi
-done
-
-# Only output reminder if error detected
-if [ "$contains_error" = true ]; then
- cat << 'EOF'
-<error-detected>
-A command error was detected. Consider logging this to .learnings/ERRORS.md if:
-- The error was unexpected or non-obvious
-- It required investigation to resolve
-- It might recur in similar contexts
-- The solution could benefit future sessions
-
-Use the self-improvement skill format: [ERR-YYYYMMDD-XXX]
-</error-detected>
-EOF
-fi
diff --git a/workspace/skills/self-improving-agent/scripts/extract-skill.sh b/workspace/skills/self-improving-agent/scripts/extract-skill.sh
deleted file mode 100644
index ccae55a..0000000
--- a/workspace/skills/self-improving-agent/scripts/extract-skill.sh
+++ /dev/null
@@ -1,221 +0,0 @@
-#!/bin/bash
-# Skill Extraction Helper
-# Creates a new skill from a learning entry
-# Usage: ./extract-skill.sh <skill-name> [--dry-run]
-
-set -e
-
-# Configuration
-SKILLS_DIR="./skills"
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-usage() {
- cat << EOF
-Usage: $(basename "$0") <skill-name> [options]
-
-Create a new skill from a learning entry.
-
-Arguments:
- skill-name Name of the skill (lowercase, hyphens for spaces)
-
-Options:
- --dry-run Show what would be created without creating files
- --output-dir Relative output directory under current path (default: ./skills)
- -h, --help Show this help message
-
-Examples:
- $(basename "$0") docker-m1-fixes
- $(basename "$0") api-timeout-patterns --dry-run
- $(basename "$0") pnpm-setup --output-dir ./skills/custom
-
-The skill will be created in: \$SKILLS_DIR/<skill-name>/
-EOF
-}
-
-log_info() {
- echo -e "${GREEN}[INFO]${NC} $1"
-}
-
-log_warn() {
- echo -e "${YELLOW}[WARN]${NC} $1"
-}
-
-log_error() {
- echo -e "${RED}[ERROR]${NC} $1" >&2
-}
-
-# Parse arguments
-SKILL_NAME=""
-DRY_RUN=false
-
-while [[ $# -gt 0 ]]; do
- case $1 in
- --dry-run)
- DRY_RUN=true
- shift
- ;;
- --output-dir)
- if [ -z "${2:-}" ] || [[ "${2:-}" == -* ]]; then
- log_error "--output-dir requires a relative path argument"
- usage
- exit 1
- fi
- SKILLS_DIR="$2"
- shift 2
- ;;
- -h|--help)
- usage
- exit 0
- ;;
- -*)
- log_error "Unknown option: $1"
- usage
- exit 1
- ;;
- *)
- if [ -z "$SKILL_NAME" ]; then
- SKILL_NAME="$1"
- else
- log_error "Unexpected argument: $1"
- usage
- exit 1
- fi
- shift
- ;;
- esac
-done
-
-# Validate skill name
-if [ -z "$SKILL_NAME" ]; then
- log_error "Skill name is required"
- usage
- exit 1
-fi
-
-# Validate skill name format (lowercase, hyphens, no spaces)
-if ! [[ "$SKILL_NAME" =~ ^[a-z0-9]+(-[a-z0-9]+)*$ ]]; then
- log_error "Invalid skill name format. Use lowercase letters, numbers, and hyphens only."
- log_error "Examples: 'docker-fixes', 'api-patterns', 'pnpm-setup'"
- exit 1
-fi
-
-# Validate output path to avoid writes outside current workspace.
-if [[ "$SKILLS_DIR" = /* ]]; then
- log_error "Output directory must be a relative path under the current directory."
- exit 1
-fi
-
-if [[ "$SKILLS_DIR" =~ (^|/)\.\.(/|$) ]]; then
- log_error "Output directory cannot include '..' path segments."
- exit 1
-fi
-
-SKILLS_DIR="${SKILLS_DIR#./}"
-SKILLS_DIR="./$SKILLS_DIR"
-
-SKILL_PATH="$SKILLS_DIR/$SKILL_NAME"
-
-# Check if skill already exists
-if [ -d "$SKILL_PATH" ] && [ "$DRY_RUN" = false ]; then
- log_error "Skill already exists: $SKILL_PATH"
- log_error "Use a different name or remove the existing skill first."
- exit 1
-fi
-
-# Dry run output
-if [ "$DRY_RUN" = true ]; then
- log_info "Dry run - would create:"
- echo " $SKILL_PATH/"
- echo " $SKILL_PATH/SKILL.md"
- echo ""
- echo "Template content would be:"
- echo "---"
- cat << TEMPLATE
-name: $SKILL_NAME
-description: "[TODO: Add a concise description of what this skill does and when to use it]"
----
-
-# $(echo "$SKILL_NAME" | sed 's/-/ /g' | awk '{for(i=1;i<=NF;i++) $i=toupper(substr($i,1,1)) tolower(substr($i,2))}1')
-
-[TODO: Brief introduction explaining the skill's purpose]
-
-## Quick Reference
-
-| Situation | Action |
-|-----------|--------|
-| [Trigger condition] | [What to do] |
-
-## Usage
-
-[TODO: Detailed usage instructions]
-
-## Examples
-
-[TODO: Add concrete examples]
-
-## Source Learning
-
-This skill was extracted from a learning entry.
-- Learning ID: [TODO: Add original learning ID]
-- Original File: .learnings/LEARNINGS.md
-TEMPLATE
- echo "---"
- exit 0
-fi
-
-# Create skill directory structure
-log_info "Creating skill: $SKILL_NAME"
-
-mkdir -p "$SKILL_PATH"
-
-# Create SKILL.md from template
-cat > "$SKILL_PATH/SKILL.md" << TEMPLATE
----
-name: $SKILL_NAME
-description: "[TODO: Add a concise description of what this skill does and when to use it]"
----
-
-# $(echo "$SKILL_NAME" | sed 's/-/ /g' | awk '{for(i=1;i<=NF;i++) $i=toupper(substr($i,1,1)) tolower(substr($i,2))}1')
-
-[TODO: Brief introduction explaining the skill's purpose]
-
-## Quick Reference
-
-| Situation | Action |
-|-----------|--------|
-| [Trigger condition] | [What to do] |
-
-## Usage
-
-[TODO: Detailed usage instructions]
-
-## Examples
-
-[TODO: Add concrete examples]
-
-## Source Learning
-
-This skill was extracted from a learning entry.
-- Learning ID: [TODO: Add original learning ID]
-- Original File: .learnings/LEARNINGS.md
-TEMPLATE
-
-log_info "Created: $SKILL_PATH/SKILL.md"
-
-# Suggest next steps
-echo ""
-log_info "Skill scaffold created successfully!"
-echo ""
-echo "Next steps:"
-echo " 1. Edit $SKILL_PATH/SKILL.md"
-echo " 2. Fill in the TODO sections with content from your learning"
-echo " 3. Add references/ folder if you have detailed documentation"
-echo " 4. Add scripts/ folder if you have executable code"
-echo " 5. Update the original learning entry with:"
-echo " **Status**: promoted_to_skill"
-echo " **Skill-Path**: skills/$SKILL_NAME"
--
Gitblit v1.9.1