agent-lifecycle-manager
/agent-lifecycle-manager
Manage full OpenClaw agent lifecycle operations on a node: create/register agents, configure channel bindings, inherit credentials, approve pairing, archive and delete agents, refresh status dashboards, and write lifecycle change logs. Use when a user asks to onboard a new agent, reconfigure an existing agent, retire/archive/delete agents, or maintain agent status boards and lifecycle audit records.
- Author
- LeoYeAI ↗
- Repository
- openclaw-master-skills ↗
- Licence
- MIT
- Last repository change
- 20.07.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 6
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 20.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 6 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/approve-telegram-pairing.sh, scripts/archive-agent.sh, scripts/create-telegram-agent.sh, scripts/delete-agent-safe.sh, scripts/lifecycle-log.sh, scripts/refresh-dashboard.sh
What it does and when to use it
Manage full OpenClaw agent lifecycle operations on a node: create/register agents, configure channel bindings, inherit credentials, approve pairing, archive and delete agents, refresh status dashboards, and write lifecycle change logs. Use when a user asks to onboard a new agent, reconfigure an existing agent, retire/archive/delete agents, or maintain agent status boards and lifecycle audit records.
Original author description
Manage full OpenClaw agent lifecycle operations on a node: create/register agents, configure channel bindings, inherit credentials, approve pairing, archive and delete agents, refresh status dashboards, and write lifecycle change logs. Use when a user asks to onboard a new agent, reconfigure an existing agent, retire/archive/delete agents, or maintain agent status boards and lifecycle audit records.
How it works
- Workflow
- Required inputs by action
- Command playbook
- Execution rules
- Minimal post-change verification
SKILL.md preview
--- name: agent-lifecycle-manager description: "Manage full OpenClaw agent lifecycle operations on a node: create/register agents, configure channel bindings, inherit credentials, approve pairing, archive and delete agents, refresh status dashboards, and write lifecycle change logs. Use when a user asks to onboard a new agent, reconfigure an existing agent, retire/archive/delete agents, or maintain agent status boards and lifecycle audit records." --- # Agent Lifecycle Manager Use this skill to execute repeatable, low-error lifecycle operations for OpenClaw agents. ## Workflow 1. Collect required inputs 2. Run lifecycle action (create/configure/archive/delete/status) 3. Verify runtime status (`openclaw status`, `openclaw agents list`) 4. Refresh dashboard files 5. Append lifecycle log entry If deleting an agent, always archive first and require explicit confirmation. ## Required inputs by action - Create + Telegram bind: - `AGENT_ID` - `TELEGRAM_TOKEN` - optional `WORKSPACE` (default: `~/.openclaw/workspace-<AGENT_ID>`) - Pairing approval (separate step): - `AGENT_ID` - `PAIRING_CODE` (obtained only after user sends `/start` to 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.sh` - `scripts/approve-telegram-pairing.sh` - `scripts/archive-agent.sh` - `scripts/delete-agent-safe.sh` - `scripts/refresh-dashboard.sh` - `scripts/lifecycle-log.sh` ## Execution rules - Prefer `openclaw` CLI 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: ```bash 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
Files in this package (8)
- SKILL.md 3 KB
- references/openclaw-agent-lifecycle-playbook.md 2 KB
- scripts/approve-telegram-pairing.sh 1 KB
- scripts/archive-agent.sh 1 KB
- scripts/create-telegram-agent.sh 2 KB
- scripts/delete-agent-safe.sh 3 KB
- scripts/lifecycle-log.sh 1 KB
- scripts/refresh-dashboard.sh 2 KB
Versions
The database has no other skills named agent-lifecycle-manager.
Database snapshot: 13.11.2026 · package version 9cf4e8aef095 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ai-maestro-agents-management
Creates, manages, and orchestrates AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "rename agent", "hibernate agent", "wake agent", "install plugin", "show agent", "export agent", "restart agent", "install… - 95agent-management
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task. - 95agent-team-builder
Guide users through building a custom multi-agent team on OpenClaw — from role design to workspace files, routing bindings, channel configuration, and collaboration rules. Use this skill whenever the user mentions building an AI team, multi-agent setup, multi-agent… - 95add-openclaw-agent
Create a new OpenClaw agent via exec (openclaw agents add) and configure its identity + operating rules by editing the new workspace files (IDENTITY.md, AGENTS.md). Use when the user wants a new agent and can describe what they want it to do; this skill asks for the purpose… - 100manage-flag-lifecycle
Manage metadata and lifecycle for a Harness FME feature flag: update description, tags, owners, rollout status; assess archive readiness (usage, experiments, dependents); archive/unarchive; delete definitions in one environment; delete the flag. Supports single flags or explicit… - 100manage-agents
Create, edit, list, or delete agent templates. Use when the user wants to add a new agent, modify an agent's prompt, change its specialty/sections, audit which agents are available, or remove an agent.