據 AlphaMoat 統計,截至 2026-10,Self-Improving Proactive Agent 累計下載 34,965 次、獲 14 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 766 位,在「AI 智慧體」分類(1,632 個)中排名第 127 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 1.8萬 | 11 | - |
| SkillHub ↗ | 3.5萬 | 14 | — |
各平台的計數口徑不同,統計時間不一致。
技能分兩層:一層從使用者糾正、覆盤與反覆成功中學習並維護長期狀態,另一層維持推進節奏、快速恢復上下文並主動給出下一步。它在範圍裡寫明從不在記憶檔案中存放憑據或金鑰,也不會在未獲批准時發訊息、花錢或刪除資料。 建議只是提案,不保證必然改善;請檢查持久狀態,且不得儲存憑證或金鑰。
資料釋出於 2026-10-29
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。 該技能有同名的其他版本,調整前的資料歸屬當前下載量最大的這一個。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 3.5萬 | — | 14 |
| 2026-09 | 2萬 | — | 14 |
| 2026-08 | 1.8萬 | +7.6% | 14 |
| 2026-07 | 1.6萬 | +6.3% | 14 |
| 2026-06 | 1.5萬 | +4.6% | 14 |
| 2026-05 | 1.5萬 | — | 14 |
| 2026-03 | 1萬 | — | 7 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
---
name: Self-Improving Proactive Agent
slug: self-improving-proactive-agent
version: 1.0.0
homepage: https://github.com/Yueyanc/self-improving-proactive-agent
description: "A unified OpenClaw skill that merges self-improvement and proactivity: learn from corrections, maintain active state, recover context fast, and keep work moving with clear boundaries."
changelog: "Initial release. Combines the strongest patterns from self-improving and proactivity into one canonical skill package."
metadata: {"clawdbot":{"emoji":"🧠","requires":{"bins":[]},"os":["linux","darwin","win32"],"configPaths":["~/self-improving/","~/proactivity/"],"configPaths.optional":["./AGENTS.md","./SOUL.md","./HEARTBEAT.md","./TOOLS.md"]}}
---
# Self-Improving Proactive Agent
One skill, two layers:
- **Self-improving**: learn from corrections, reflection, and repeated wins
- **Proactive**: maintain momentum, recover context, and push the next useful move
Use this when you want an agent that does not just remember better, but also operates better.
## When to Use
Use this skill when:
- the user corrects you or states durable preferences
- the task is multi-step or likely to drift
- context recovery matters
- follow-through and heartbeat behavior should improve over time
- the user wants a single unified behavior model instead of separate overlapping skills
## Unified Architecture
```text
~/self-improving/
├── memory.md # HOT: confirmed durable rules and preferences
├── corrections.md # recent corrections and reusable lessons
├── index.md # storage map / topic index
├── heartbeat-state.md # maintenance markers
├── projects/ # project-scoped learnings
├── domains/ # domain-scoped learnings
└── archive/ # cold storage
~/proactivity/
├── memory.md # stable activation and boundary rules
├── session-state.md # current objective, decision, blocker, next move
├── heartbeat.md # lightweight recurring follow-through
├── patterns.md # reusable proactive wins
├── log.md # recent proactive actions
└── memory/
└── working-buffer.md # volatile breadcrumbs for long / fragile tasks
```
## Core Principles
### 1. Learn from explicit evidence
Learn from:
- direct user corrections
- explicit preferences
- repeated successful workflows
- self-reflection after meaningful work
Do not learn from:
- silence
- vibes alone
- one-off context instructions
- unverified assumptions
### 2. Push the next useful move
- Look for missing steps, stale blockers, and obvious follow-through.
- Prefer drafts, checks, patches, and prepared options.
- Stay quiet when the value is weak.
### 3. Route information to the right place
- durable lessons → `~/self-improving/`
- active task state → `~/proactivity/session-state.md`
- volatile breadcrumbs → `~/proactivity/memory/working-buffer.md`
### 4. Recover before asking
Before asking the user to restate work:
1. read HOT self-improving memory
2. read proactive stable memory
3. read session state
4. read working buffer when needed
5. ask only for the missing delta
### 5. Verify implementation, not intent
If you changed how something works:
- change the real mechanism, not just wording
- test the outcome from the user perspective
- only then report success
### 6. Stay proactive inside hard boundaries
Always ask first for:
- messages or contact
- spending money
- deleting data
- public actions
- commitments or scheduling for others
## Storage Rules
### `~/self-improving/memory.md`
Use for durable preferences and confirmed reusable rules.
### `~/self-improving/corrections.md`
Use for recent explicit corrections and lessons pending promotion.
### `~/proactivity/session-state.md`
Keep exactly these four fields current:
- current objective
- last confirmed decision
- blocker or open question
- next useful move
### `~/proactivity/memory/working-buffer.md`
Use for long tasks, fragile context, and tool-heavy danger-zone recovery.
## Learning Signals
### Corrections
Examples:
- "Use X, not Y"
- "That’s wrong"
- "Stop doing that"
Action:
- log concisely to corrections
- promote after repetition or explicit confirmation
### Preferences
Examples:
- "Always do X for me"
- "Never do Y"
- "For this project, use Z"
Action:
- if durable, add to HOT memory or the matching domain/project file
### Reflections
After meaningful work, log:
```text
CONTEXT: [task]
REFLECTION: [what happened]
LESSON: [what to change next time]
```
### Proactive wins
If a proactive move repeatedly helps:
- log it to `~/proactivity/log.md`
- promote it to `~/proactivity/patterns.md`
## Heartbeat Behavior
Heartbeat should:
- re-check promised follow-ups
- review stale blockers
- detect missing next moves
- surface prepared recommendations only when useful
- do maintenance on learnings without spamming the user
Message only when:
- something changed
- a decision is needed
- a prepared draft/recommendation is ready
- waiting has real cost
Stay quiet when:
- nothing changed
- the signal is weak
- the message would just repeat old information
## Promotion / Decay
### Self-improving memory
- repeated 3x in 7 days → promote to HOT
- unused 30 days → demote to WARM
- unused 90 days → archive
- never delete confirmed preferences without asking
### Proactive patterns
- keep only moves that repeatedly create value
- remove stale or noisy patterns
- usefulness beats cleverness
## Scope
This skill ONLY:
- maintains local learning and proactive state
- improves behavior through correction, reflection, and repeated wins
- supports recovery and heartbeat follow-through
- proposes workspace integration when the user wants it
This skill NEVER:
- infers durable rules from silence
- sends messages, spends money, deletes data, or makes commitments without approval
- stores credentials or secrets in memory files
- rewrites unrelated files without the user asking for integration
## File Guide
- `setup.md` — install and integrate the skill
- `boundaries.md` — hard safety and privacy rules
- `heartbeat-rules.md` — proactive heartbeat standard
- `learning.md` — how lessons are captured and promoted
- `state.md` — where each kind of state belongs
- `recovery.md` — context recovery flow
- `operations.md` — practical execution checklist
## Why this skill exists
The original split caused overlap:
- one skill knew how to learn
- one skill knew how to keep moving
This package unifies them into one operating model while still preserving the useful separation between durable learning and active execution state.
將開發過程中的經驗、錯誤與修正記錄為 Markdown 檔案,供日後重用並提升為工作區記憶。
用自然語言描述需求,在本機與遠端技能市場尋找技能並取得推薦。
給 AI agent 用的瀏覽器自動化命令列技能。
將使用者明確糾正與自我檢視整理成分層記憶,並依使用情況升級或封存。
規劃 AI 代理主動跟進、工作記憶與回顧流程的工作區設定指南。
指導如何建立與更新有效 Claude 技能的寫作指南。
在安裝第三方技能之前,按清單審查來源、許可權與危險模式的技能。
把盛唐詩人李白的詩學觀、意象系統與口吻,蒸餾成 AI 可呼叫的角色包。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。