LeoYeAI Agent Lifecycle Manager
Use this skill to execute repeatable, low-error lifecycle operations for OpenClaw agents.
Workflow
- Collect required inputs
- Run lifecycle action (create/configure/archive/delete/status)
- Verify runtime status (
openclaw status,openclaw agents list) - Refresh dashboard files
- Append lifecycle log entry
If deleting an agent, always archive first and require explicit confirmation.
Required inputs by action
- Create + Telegram bind:
AGENT_IDTELEGRAM_TOKEN- optional
WORKSPACE(default:~/.openclaw/workspace-<AGENT_ID>)
- Pairing approval (separate step):
AGENT_IDPAIRING_CODE(obtained only after user sends/startto the bot)
- Reconfigure:
AGENT_ID- changed fields (model/routes/channel token/etc.)
- Archive/Delete:
AGENT_ID- archive destination (default under
state/archive/<AGENT_ID>/)
Command playbook
Read references/openclaw-agent-lifecycle-playbook.md before running uncommon operations.
For deterministic execution, use scripts in this skill:
scripts/create-telegram-agent.shscripts/approve-telegram-pairing.shscripts/archive-agent.shscripts/delete-agent-safe.shscripts/refresh-dashboard.shscripts/lifecycle-log.sh
Execution rules
- Prefer
openclawCLI over ad-hoc file edits. - Configure bindings via
openclaw config get/set(append entry; do not overwrite blindly). - Do not restart gateway by default after binding/config changes.
- Use pairing command with explicit channel flag:
openclaw pairing approve <PAIRING_CODE> --channel telegram. - Never hard-delete before successful archive.
- For deletion, prefer
scripts/delete-agent-safe.sh(archive verification + explicit confirmation + cleanup + logging). - After every lifecycle change, run dashboard refresh + lifecycle logging.
Minimal post-change verification
Run:
openclaw agents list --json
openclaw status --json
openclaw gateway status --json
Confirm:
- target agent exists (or is absent after deletion)
- expected bindings/routes are present
- gateway runtime is healthy and RPC probe is ok