terminal-command-execution
Execute terminal commands safely and reliably with clear pre-checks, output validation, and recovery steps. Use when users ask to run shell/CLI commands, inspect system state, manage files, install dependencies, start services, debug command failures, or automate command-line workflows.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/1215656/terminal-command-execution-1-0-0Terminal Command Execution
Overview
Use this skill to run terminal commands with minimal risk and predictable outcomes. Prefer fast inspection, explicit intent checks, and verification after each state-changing step.
Workflow
- Clarify goal and scope.
- Infer the exact command target from context (path, service, tool, environment).
- If request is ambiguous and risky, ask one concise clarifying question.
- Pre-flight checks.
- Confirm working directory and required binaries.
- Inspect current state before changing it (for example
ls,git status, process/listen state). - Prefer non-destructive probes first.
- Execute commands incrementally.
- Run the smallest command that advances the task.
- For multi-step tasks, validate each step before continuing.
- Use reproducible commands and avoid interactive flows when non-interactive options exist.
- Handle failures systematically.
- Read stderr first and identify root cause class: permission, path, missing dependency, syntax, network, or runtime state.
- Apply one fix at a time, then re-run only the affected command.
- If privileged/destructive action is required, request user approval before proceeding.
- Verify outcomes.
- Check exit status and observable state changes.
- For installs, verify with a version/health command.
- For edits, verify resulting files and behavior.
- Report clearly.
- Summarize what ran, what changed, and current status.
- Include exact next command only when additional user action is required.
Safety Rules
- Avoid destructive commands by default (
rm -rf, force resets, broad chmod/chown) unless explicitly requested. - Never assume network, permissions, or package managers are available; test first.
- Prefer scoped operations (specific files/paths/services) over global changes.
- Keep secrets out of command output and logs.
Command Patterns
- Discovery:
pwd,ls -la,rg --files,which <tool> - Validation:
<tool> --version, health/status commands, targeted smoke tests - Diagnostics: inspect logs/errors first, then adjust one variable at a time
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-1215656-terminal-command-execution-1-0-0": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
filesystem
Advanced filesystem operations - listing, searching, batch processing, and directory analysis for Clawdbot
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
botlearn-healthcheck
Autonomously inspects a live OpenClaw instance across 5 health domains (hardware, config, security, skills, autonomy) and delivers a quantified traffic-light report with actionable fix guidance.
Puppeteer
Automate Chrome and Chromium with Puppeteer for scraping, testing, screenshots, and browser workflows.