Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Safely and thoroughly delete an OpenClaw agent and its artifacts. Use when user asks to remove an agent completely, including workspace, agent files under ~/...
Safely and thoroughly delete an OpenClaw agent and its artifacts. Use when user asks to remove an agent completely, including workspace, agent files under ~/...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Permanently remove an agent and its related local config/files.
This is destructive. Always require explicit user confirmation. Enforce 3-step gate: run --dry-run, explicit confirmation for local deletion, separate explicit confirmation for Telegram browser/session-controlled group deletion. Ask user whether to also delete the dedicated Telegram group. Never auto-delete Telegram groups without the separate confirmation. Prefer script execution for local cleanup (stable, low token).
Collect: agent_id (required) delete_workspace (yes/no) delete_telegram_group_config (yes/no; usually yes) delete_telegram_group (yes/no; requires explicit confirmation) delete_cron_jobs (yes/no; usually yes)
Dry-run: python3 scripts/delete_agent.py --agent-id <agent_id> --dry-run Execute (after confirmation): python3 scripts/delete_agent.py --agent-id <agent_id> --yes --delete-workspace --delete-telegram-group-config --delete-cron-jobs
scripts/delete_agent.py validates agent_id format: [a-z0-9-]+. It refuses deletion when target paths are outside allowed directories. Workspace deletion is allowed only when path is under user home and folder name starts with claw-. It creates backup files before writing config changes.
Agent entry in ~/.openclaw/openclaw.json (agents.list) Agent bindings (bindings[] with matching agentId) Telegram group routing entries linked by those bindings channels.telegram.groups.<chat_id> Agent directory: ~/.openclaw/agents/<agent_id> Workspace directory from agent config (if --delete-workspace) Cron jobs owned by this agent from ~/.openclaw/cron/jobs.json (if --delete-cron-jobs)
This skill does not bundle Telegram deletion automation code; it uses external browser automation tooling or manual user actions. After local script deletion and only if user confirmed delete_telegram_group=yes: Require a separate explicit confirmation: user agrees to browser/session control and irreversible group deletion. Identify dedicated group chat_id from removed bindings. Use browser automation (Telegram Web) to open the group and run Delete Group. In Telegram delete dialog, enable Delete for all members when available, then confirm deletion. Report final group status clearly: deleted / left-only / pending-manual.
Surface backup files created by the script (openclaw.json.bak.*, jobs.json.bak.*) so user can retain recovery points. If gateway reload is available, let hot reload apply. If not applied, ask for explicit confirmation before restarting gateway, then verify logs. Return concise summary with removed items.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.