360 Secure SkillHub
360 安全技能中心

Self Improver Lite

用于 OpenClaw 运行自审：采集网关与 Ollama 的服务状态和近期日志，按模式归类重复故障并统计次数，定位前 1-3 个根因，提出最小可回滚修复；仅自动执行会话清理、网关重启、参数微调等低风险动作，高风险操作需用户确认，并输出周度自审报告。

分类：自动化
utromaya-code
utromaya-code
热度 29.63
最近更新 2026-05-11 17:35:15

安装

发给 Agent
帮我安装这个技能：npx secure-skills-cli add utromaya-code/agent-self-improver
兼容性
OpenClaw 专属
联网要求
联网要求未确认
数据出网
数据不出本机
Metadata
name
self-improver-lite
description
Runs lightweight self-audits of OpenClaw behavior, finds repeated failures, proposes safe config/process improvements, and tracks what changed. Use after incidents, silent-bot periods, rate-limit spikes, or weekly maintenance.

Self Improver Lite

Goal

Continuously improve reliability without risky autonomous changes.

Trigger Cases

  • Bot is silent or unstable
  • Same error appears repeatedly (rate_limit, orphaned, timeout, sendMessage failed)
  • After major config updates
  • Scheduled weekly health review

Audit Steps

  1. Collect evidence:
systemctl is-active openclaw-gateway ollama
journalctl -u openclaw-gateway -n 120 --no-pager
  1. Group failures by pattern and count.
  2. Identify top 1-3 root causes.
  3. Propose minimal, reversible fixes.
  4. Apply only low-risk fixes automatically.
  5. Record summary and next actions.

Auto-Allowed Changes

  • Session cleanup when orphaned user message loops
  • Gateway restart for stuck polling
  • Context window/maxTokens tuning within known-safe ranges
  • Fallback chain reordering (no key changes)

Requires Explicit User Approval

  • New API provider onboarding
  • Social network account actions
  • Financial/crypto operations
  • Credential rotation or deletion
  • Any destructive file cleanup beyond sessions/log rotation

Weekly Review Template

## Weekly Self-Audit
- Period: <dates>
- Uptime notes: <short>

### Top Errors
1. <error> — <count>
2. <error> — <count>

### Changes Applied
- <change 1>
- <change 2>

### Measured Impact
- Response latency: <before -> after>
- Failed runs: <before -> after>

### Next Improvements
- <single highest-impact next step>

Guardrails

  • Never expose secrets in reports.
  • Always keep a rollback path (backup old config before edits).
  • Prefer one change per cycle to keep causality clear.