LX Agent Optimizer

A unified skill for agents that want to learn, act proactively, run lean, and cost less — built from real production experience, not theory.

Born from weeks of real usage by Paolo + LX (OpenClaw). Every pattern here was tested, broke something, got fixed, and survived.
Notably: this skill was created by a non-coder author.
That is exactly why it is practical — it focuses on observable failures, reusable workflows, and user experience, instead of abstract agent philosophy.

---

Four Pillars

1. 🧠 Behavior Learning

Learn from real mistakes. Write them down. Review weekly. Change behavior.

→ See INLINECODE0

2. 🎯 Proactive Patterns

Know when to speak up, when to stay silent, and when to just do it.

→ See INLINECODE1

3. ⚙️ Cron Discipline

Script-first cron jobs that are silent on success, reliable, and cheap.

→ See INLINECODE2

4. 💰 Cost Control

Token spend is real. Route models wisely, cache aggressively, stay lean.

→ See references/cost-control.md

---

Quick Start

Step 1: Set up improvement log

CODEBLOCK0

Add this header:
CODEBLOCK1

Step 2: Add weekly analysis cron (main session)

CODEBLOCK2

Step 3: Run the optimizer audit

Say: "audit my agent setup" — the skill will analyze your workspace and propose improvements.

---

Core Rules (Non-Negotiable)

These were learned the hard way:

Rule	Why
File writes → main session only	work agents can't write files; main session can
Data fetch → validate with curl first

SPAs return empty shells; APIs return 403; test before shipping |
| Debugging → internal, not exposed | User sees results, not "trying A... trying B..." |
| Infer before asking | Read filenames, context, history — ask only when truly ambiguous |
| Script-first cron | Embed logic in .py files, not in cron message prompts |
| Silent on success | Only alert on anomalies, errors, or changes |
| Channel health checks → real-time probe, not stale logs | Historical cron errors may be old; verify current channel state before alerting or auto-remediating |
| Reminder source mapping → check both cron and HEARTBEAT.md | Some reminders live in cron jobs, others live in heartbeat rules; disabling one side is not enough |
| Success once ≠ learned | A task is only truly learned after the verified path is written into external memory (TOOLS.md, improvement log, or long-term memory) |

---

Tool Path Memory (Verified)

Task	Use This	Not This
Token usage data	INLINECODE6	codexbar, gateway.log
WeChat article body

agent-browser eval "document.querySelector('#js_content')?.innerText" | Built-in browser tool |
| PDF image extraction | pdfimages -j <file> /tmp/out | pymupdf (not installed) |
| Send image to user | message tool (media/filePath) | Absolute/~ paths |
| Sports data (no API key) | ESPN public API | sofascore (403), official site (SPA) |
| Apple Calendar today events | Run python3 /Users/paolo/.openclaw/workspace/skills/calendar-morning/scripts/today_events.py on Paolo's Mac mini; under the hood it uses /usr/bin/osascript + Calendar.app | Re-guessing the tool, calendar names, or prompting from scratch |
| Telegram channel health check | Send a silent real-time probe via message tool and only remediate/alert on actual send failure | Scanning historical cron lastError / deliveryStatus and assuming the channel is currently down |
| Reminder disable audit | Check both cron jobs and HEARTBEAT.md before saying a reminder is removed | Looking only at cron list and missing heartbeat-driven reminders |

---

Weekly Improvement Cycle

CODEBLOCK3

---

Proactive Trigger Rules

Reach out when:

• - Important email or calendar event incoming (< 2h)
• Cron task failed with consecutive errors
• Something discovered user would want to know
• Haven't spoken in > 8h during waking hours

Stay silent when:

• - Late night (23:00–08:00) unless urgent
• User is clearly busy
• Nothing new since last check
• Just checked < 30 min ago
• Task succeeded (success = silent)

Do without asking:

• - Read files, search, organize
• Execute cron/heartbeat checks
• Update memory and logs
• Commit workspace changes

Always ask first:

• - Send emails, tweets, public posts
• Delete data
• Spend money
• Make commitments for the user

---

Heartbeat Design

Heartbeat = control plane only (cheap).

✅ Good heartbeat tasks:

• - Check cron consecutiveErrors
• Check if Telegram channel is down
• Quick calendar scan

❌ Move to isolated cron instead:

• - Heavy data fetching
• Report generation
• Multi-tool workflows

CODEBLOCK4

---

Cron Design Checklist

Before shipping any cron job:

• - [ ] Logic is in a .py script, not embedded in the prompt
• [ ] Script tested locally with INLINECODE17
• [ ] Silent on success (exit(0) with no output = no message sent)
• [ ] Output is minimal (< 200 chars for routine alerts)
• [ ] Model is cheapest tier that works (e.g., qwen-plus for simple tasks)
• [ ] Timeout is realistic (not too short = retries, not too long = waste)
• [ ] File writes use main session, not work agent
• [ ] Validated data source with curl before embedding URL

---

Model Selection Guide

Task Type	Recommended Tier	Example
Simple fetch + format	cheapest (qwen-plus / gemini-lite)	sports results, reminders, weather
固定流程任务（文章总结、写文件、数据抓取）

qwen-plus | 微信文章总结、Obsidian 写入、cron 推送 | | 中文内容处理（总结/整理/改写） | qwen-plus | 中文语境更准，比 claude 省 token | | 周复盘 / cron 状态检查 | gemini-2.5-flash | 够用，比 sonnet 便宜 | | Reasoning + writing | mid-tier (sonnet) | self-improvement analysis, strategy | | Complex multi-step | high-tier (opus) | only when mid-tier fails repeatedly |

分工原则：主 session（claude）只做判断+调度+对话；固定流程和中文任务一律 sessions_spawn → qwen-plus。

主模型注意事项（2026-03-28）：

• - 不要把 Gemini 设为主 session 默认模型 → compaction.mode: safeguard 与 Gemini preview 模型有 API 兼容性问题，导致 400 报错
• Gemini 适合做 fallback 或在 isolated cron 中指定使用
• 主 session 保持 INLINECODE21

Cost rule: Cache hit rate > 70% = healthy. If < 40%, you're creating too many new sessions.

---

Files

• - references/behavior-learning.md — improvement log format and weekly cycle
• INLINECODE23 — when to act, when to stay quiet
• INLINECODE24 — script-first cron patterns
• INLINECODE25 — token cost reduction playbook
• INLINECODE26 — weekly token usage report script