safe-exec
Safe command execution for OpenClaw Agents with automatic danger pattern detection, risk assessment, user approval workflow, and audit logging. Use when agents need to execute shell commands that may be dangerous (rm -rf, dd, fork bombs, system directory modifications) or require human oversight. Provides multi-level risk assessment (CRITICAL/HIGH/MEDIUM/LOW), in-session notifications, pending request management, and non-interactive environment support for agent automation.
What this skill does
# SafeExec - Safe Command Execution Provides secure command execution capabilities for OpenClaw Agents with automatic interception of dangerous operations and approval workflow. ## Features - ๐ **Automatic danger pattern detection** - Identifies risky commands before execution - ๐จ **Risk-based interception** - Multi-level assessment (CRITICAL/HIGH/MEDIUM/LOW) - ๐ฌ **In-session notifications** - Real-time alerts in your current terminal/session - โ **User approval workflow** - Commands wait for explicit confirmation - ๐ **Complete audit logging** - Full traceability of all operations - ๐ค **Agent-friendly** - Non-interactive mode support for automated workflows - ๐ง **Platform-agnostic** - Works independently of communication tools (Feishu, Telegram, etc.) ## Quick Start ### Installation (One Command) **The easiest way to install SafeExec:** Just say in your OpenClaw chat: ``` Help me install SafeExec skill from ClawdHub ``` OpenClaw will automatically download, install, and configure SafeExec for you! ### Alternative: Manual Installation If you prefer manual installation: ```bash # Using ClawdHub CLI export CLAWDHUB_REGISTRY=https://www.clawhub.ai clawdhub install safe-exec # Or download directly from GitHub git clone https://github.com/OTTTTTO/safe-exec.git ~/.openclaw/skills/safe-exec chmod +x ~/.openclaw/skills/safe-exec/safe-exec*.sh ``` ### Enable SafeExec After installation, simply say: ``` Enable SafeExec ``` SafeExec will start monitoring all shell commands automatically! ## How It Works Once enabled, SafeExec automatically monitors all shell command executions. When a potentially dangerous command is detected, it intercepts the execution and requests your approval through **in-session terminal notifications**. **Architecture:** - Requests stored in: `~/.openclaw/safe-exec/pending/` - Audit log: `~/.openclaw/safe-exec-audit.log` - Rules config: `~/.openclaw/safe-exec-rules.json` ## Usage **Enable SafeExec:** ``` Enable SafeExec ``` ``` Turn on SafeExec ``` ``` Start SafeExec ``` Once enabled, SafeExec runs transparently in the background. Agents can execute commands normally, and SafeExec will automatically intercept dangerous operations: ``` Delete all files in /tmp/test ``` ``` Format the USB drive ``` SafeExec detects the risk level and displays an in-session prompt for approval. ## Risk Levels **CRITICAL**: System-destructive commands (rm -rf /, dd, mkfs, etc.) **HIGH**: User data deletion or significant system changes **MEDIUM**: Service operations or configuration changes **LOW**: Read operations and safe file manipulations ## Approval Workflow 1. Agent executes a command 2. SafeExec analyzes the risk level 3. **In-session notification displayed** in your terminal 4. Approve or reject via: - Terminal: `safe-exec-approve <request_id>` - List pending: `safe-exec-list` - Reject: `safe-exec-reject <request_id>` 5. Command executes or is cancelled **Example notification:** ``` ๐จ **Dangerous Operation Detected - Command Intercepted** **Risk Level:** CRITICAL **Command:** `rm -rf /tmp/test` **Reason:** Recursive deletion with force flag **Request ID:** `req_1769938492_9730` โน๏ธ This command requires user approval to execute. **Approval Methods:** 1. In terminal: `safe-exec-approve req_1769938492_9730` 2. Or: `safe-exec-list` to view all pending requests **Rejection Method:** `safe-exec-reject req_1769938492_9730` ``` ## Configuration Environment variables for customization: - `SAFE_EXEC_DISABLE` - Set to '1' to globally disable safe-exec - `OPENCLAW_AGENT_CALL` - Automatically enabled in agent mode (non-interactive) - `SAFE_EXEC_AUTO_CONFIRM` - Auto-approve LOW/MEDIUM risk commands ## Examples **Enable SafeExec:** ``` Enable SafeExec ``` **After enabling, agents work normally:** ``` Delete old log files from /var/log ``` SafeExec automatically detects this is HIGH risk (deletion) and displays an in-session approval prompt. **Safe operations pass through without interruption:** ``` List files in /home/user/documents ``` This is LOW risk and executes without approval. ## Global Control **Check status:** ``` safe-exec-list ``` **View audit log:** ```bash cat ~/.openclaw/safe-exec-audit.log ``` **Disable SafeExec globally:** ``` Disable SafeExec ``` Or set environment variable: ```bash export SAFE_EXEC_DISABLE=1 ``` ## Reporting Issues **Found a bug? Have a feature request?** Please report issues at: ๐ **https://github.com/OTTTTTO/safe-exec/issues** We welcome community feedback, bug reports, and feature suggestions! When reporting issues, please include: - SafeExec version (run: `grep "VERSION" ~/.openclaw/skills/safe-exec/safe-exec.sh`) - OpenClaw version - Steps to reproduce - Expected vs actual behavior - Relevant logs from `~/.openclaw/safe-exec-audit.log` ## Audit Log All command executions are logged with: - Timestamp - Command executed - Risk level - Approval status - Execution result - Request ID for traceability Log location: `~/.openclaw/safe-exec-audit.log` ## Integration SafeExec integrates seamlessly with OpenClaw agents. Once enabled, it works transparently without requiring changes to agent behavior or command structure. The approval workflow is entirely local and independent of any external communication platform. ## Platform Independence SafeExec operates at the **session level**, working with any communication channel your OpenClaw instance supports (webchat, Feishu, Telegram, Discord, etc.). The approval workflow happens through your terminal, ensuring you maintain control regardless of how you're interacting with your agent. ## Support & Community - **GitHub Repository:** https://github.com/OTTTTTO/safe-exec - **Issue Tracker:** https://github.com/OTTTTTO/safe-exec/issues - **Documentation:** [README.md](https://github.com/OTTTTTO/safe-exec/blob/master/README.md) - **ClawdHub:** https://www.clawhub.ai/skills/safe-exec ## License MIT License - See [LICENSE](https://github.com/OTTTTTO/safe-exec/blob/master/LICENSE) for details.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.