Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fast, explicit terminal execution via OpenClaw exec (direct dispatch; you type the exact command).
Fast, explicit terminal execution via OpenClaw exec (direct dispatch; you type the exact command).
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.
/term is a power-user shortcut: whatever you type after /term is forwarded as-is to OpenClaw’s exec tool. This is intentionally “manual mode”: You (the user) provide the exact shell command. OpenClaw does not rewrite, expand, or “helpfully” change it. It’s useful when you want quick, deterministic terminal actions without a planning loop.
OpenClaw supports command-dispatch: tool skills. When you run: /term ls -la the raw argument string (ls -la) is forwarded to the configured tool (exec) without extra parsing. In tool-dispatch mode, OpenClaw invokes the tool with params shaped like: { command: "<raw args>", commandName: "<slash command>", skillName: "<skill name>" } See the Skills docs section on command-dispatch, command-tool, and command-arg-mode. :contentReference[oaicite:10]{index=10}
Use /term when: You already know the exact command you want. You want a quick read-only check (files, git status, grep). You are debugging OpenClaw itself (skills folder, logs, Peekaboo bridge status). Prefer normal agent flow when: You want the model to decide the best approach. The task may need multiple steps, safety checks, or file edits.
/term is equivalent to letting an assistant type into your terminal. Good defaults: Prefer read-only commands unless you mean to change state. Avoid secrets in command lines (tokens, API keys, cookies). Avoid remote execution one-liners: no curl ... | sh no “download and execute” pipelines If the command could delete or overwrite files, slow down and double-check paths.
Your actual execution environment depends on how you invoke exec in your setup (sandbox vs host). Also note: when a session is sandboxed, environment variables are not automatically inherited by the container; you must inject them via sandbox env settings or bake them into the image. :contentReference[oaicite:11]{index=11}
/term pwd /term ls -la /term git status /term rg -n "TODO|FIXME" .
/term peekaboo bridge status --verbose If the output shows “no such file or directory” for all candidates and “Selected: local (in-process)”, you likely have no bridge host running (see troubleshooting below).
If you want JSON output for parsing: /term python -c 'import json,platform; print(json.dumps({"py":platform.python_version()}))'
The tool runs in whatever PATH your OpenClaw runtime provides. If you rely on Homebrew, ensure the runtime sees /opt/homebrew/bin.
Some tools (screen capture / UI automation) require Screen Recording / Accessibility. Those permissions are per-process context on macOS; using PeekabooBridge is often the reliable path for automation.
Install/use the companion skill terminal-helper (model-invocable) which teaches safe patterns, confirmations, and runbooks.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.