delete-agent-with-telegram-groupSafely and thoroughly delete an OpenClaw agent and its artifacts. Use when user asks to remove an agent completely, including workspace, agent files under ~/...
Install via ClawdBot CLI:
clawdbot install Sheetaa/delete-agent-with-telegram-groupGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 21, 2026
A developer managing multiple AI agents on an OpenClaw platform needs to decommission an outdated or unused agent. This scenario involves safely removing the agent's local files, configurations, and associated Telegram group to free up resources and maintain a clean system, ensuring no residual artifacts cause conflicts.
A business shutting down a customer support or notification bot built with OpenClaw requires complete deletion. This includes removing the agent's code, workspace, and dedicated Telegram group to prevent unauthorized access and ensure data privacy, with careful confirmation steps to avoid accidental loss.
During development or testing cycles, a team needs to delete temporary AI agents and their Telegram groups to reset environments. This scenario emphasizes using dry-run checks and explicit confirmations to safely clean up test artifacts without affecting production systems or active communications.
An organization must delete an AI agent due to regulatory requirements or data retention policies. This involves thorough cleanup of local files, configurations, and Telegram groups to ensure compliance, with backups created for audit trails and recovery if needed.
A system administrator optimizing an OpenClaw deployment by removing redundant or underperforming agents. This scenario focuses on deleting agents and their Telegram groups to streamline operations, reduce maintenance overhead, and improve overall system performance through careful artifact removal.
Companies offering platforms for building and managing AI agents can use this skill to provide safe deletion features. This enhances user trust by ensuring clean removal of agents and associated resources, reducing support tickets related to leftover artifacts and improving platform reliability.
Businesses providing managed Telegram bot services leverage this skill for decommissioning bots upon client request or contract end. It ensures complete cleanup of agent files and Telegram groups, maintaining data security and operational efficiency while minimizing manual intervention.
Consultants specializing in AI and automation integrate this skill into client systems for lifecycle management. They offer deletion services to help clients safely remove agents, with revenue from project-based fees or ongoing maintenance agreements, ensuring compliance and system hygiene.
💬 Integration Tip
Integrate this skill into existing CI/CD pipelines for automated testing cleanup, and ensure Telegram group deletion steps are documented for manual execution to avoid automation risks.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.