How do I install the Openclaw Ops skill?

Run npx skillmds@latest add scoobydont-666/openclaw-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw Ops?

scoobydont-666 (@scoobydont-666) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw Ops by scoobydont-666 — Agent Skill

Name: Openclaw Ops
Author: scoobydont-666

Openclaw Ops

OpenClaw and NemoClaw operations — sandbox management, inference provider config, policy configuration, Tailscale integration, security hardening, skill vetting. Trigger on: "OpenClaw", "NemoClaw", "OpenShell", "sandbox", "openclaw tui", "agent assistant", "ClawHub", "gateway token", or any task involving personal AI assistant deployment and operations.

File contents

OpenClaw/NemoClaw Operations

Deployment on Primary Host

Component	Status	Port	Access
OpenClaw	v2026.3.13	(loopback)	Tailscale Serve → HTTPS
NemoClaw	v0.1.0 (alpha)	(OpenShell gateway)	Internal
Sandbox	`my-assistant`	—	`nemoclaw my-assistant connect`
Tailscale	Connected		`https://<primary-host>.tail<tailnet>.ts.net/`

Security Posture

All messaging channels disabled (WhatsApp, Telegram, Discord, Slack, Signal, Matrix, IRC)
DM policy: disabled on all channels
Gateway auth: token-based
Gateway bind: loopback only (127.0.0.1:)
UFW: gateway port denied from LAN, allowed via Tailscale interface
NemoClaw sandbox: OpenShell with Landlock + seccomp + network namespace isolation
Inference binding and service ports configured for internal access only

Interaction

Recommended: CLI/TUI via Tailscale SSH (most secure)

# From any device on your tailnet
ssh admin_user@<primary-host>    # via Tailscale
openclaw tui         # interactive chat

# Or inside the sandbox
nemoclaw my-assistant connect
openclaw tui

Web dashboard: https://<primary-host>.tail<tailnet>.ts.net/ (tailnet only)

Inference

Primary: Local Ollama on GPU host (:)

Available models: qwen3:8b/14b, llama3.3:70b, deepseek-r1:70b, mistral-nemo:12b, gemma2:9b
Requires GPU host to be online

Fallback: Anthropic Claude API (if configured)

Known Ollama bugs: cold-start timeouts (#43946), API key after reconfig (#28927)

Key Commands

# Gateway
openclaw gateway status
openclaw gateway restart
systemctl --user status openclaw-gateway

# Sandbox
nemoclaw list
nemoclaw my-assistant status
nemoclaw my-assistant connect
nemoclaw my-assistant logs --follow
nemoclaw my-assistant destroy         # nuclear option

# Config
openclaw config set <key> <value>
openclaw doctor                       # health check
openclaw security audit --deep        # policy drift check

# Tailscale
sudo tailscale serve status
sudo tailscale serve --bg 18789       # re-enable serve
sudo tailscale serve --https=443 off  # disable serve

Security Warnings

CVE-2026-25253 (CVSS 8.8) — patched in >= 2026.1.29. We run 2026.3.13.
29 pages of GitHub Security Advisories — large attack surface from messaging integrations (all disabled).
ClawHub skills — no mandatory vetting. Treat all as untrusted. Audit before installing.
NemoClaw is alpha — expect instability. The sandbox is the security-critical layer.
API keys — never paste in chat. Use env vars or config files with 600 permissions.

Rules

Never enable messaging channels without explicit approval
Never install ClawHub skills without security review
Never expose OpenClaw ports to LAN (Tailscale only)
Always verify sandbox is active before trusting isolation
Rotate gateway token if compromised
Keep OpenClaw updated (check: openclaw --version)

---name: openclaw-opsdescription: OpenClaw and NemoClaw operations — sandbox management, inference provider config, policy configuration, Tailscale integration, security hardening, skill vetting. Trigger on: "OpenClaw", "NemoClaw", "OpenShell", "sandbox", "openclaw tui", "agent assistant", "ClawHub", "gateway token", or any task involving personal AI assistant deployment and operations.---# OpenClaw/NemoClaw Operations## Deployment on Primary Host| Component | Status | Port | Access ||---|---|---|---|| OpenClaw | v2026.3.13 | <service-port> (loopback) | Tailscale Serve → HTTPS || NemoClaw | v0.1.0 (alpha) | <gateway-port> (OpenShell gateway) | Internal || Sandbox | `my-assistant` | — | `nemoclaw my-assistant connect` || Tailscale | Connected | <tailscale-ip> | `https://<primary-host>.tail<tailnet>.ts.net/` |## Security Posture- All messaging channels **disabled** (WhatsApp, Telegram, Discord, Slack, Signal, Matrix, IRC)- DM policy: **disabled** on all channels- Gateway auth: **token-based**- Gateway bind: **loopback only** (127.0.0.1:<service-port>)- UFW: gateway port **denied** from LAN, **allowed** via Tailscale interface- NemoClaw sandbox: OpenShell with Landlock + seccomp + network namespace isolation- Inference binding and service ports configured for internal access only## Interaction**Recommended: CLI/TUI via Tailscale SSH (most secure)**```bash# From any device on your tailnetssh admin_user@<primary-host> # via Tailscaleopenclaw tui # interactive chat# Or inside the sandboxnemoclaw my-assistant connectopenclaw tui```**Web dashboard:** `https://<primary-host>.tail<tailnet>.ts.net/` (tailnet only)## Inference**Primary:** Local Ollama on GPU host (<gpu-host-ip>:<ollama-port>)- Available models: qwen3:8b/14b, llama3.3:70b, deepseek-r1:70b, mistral-nemo:12b, gemma2:9b- Requires GPU host to be online**Fallback:** Anthropic Claude API (if configured)- Known Ollama bugs: cold-start timeouts (#43946), API key after reconfig (#28927)## Key Commands```bash# Gatewayopenclaw gateway statusopenclaw gateway restartsystemctl --user status openclaw-gateway# Sandboxnemoclaw listnemoclaw my-assistant statusnemoclaw my-assistant connectnemoclaw my-assistant logs --follownemoclaw my-assistant destroy # nuclear option# Configopenclaw config set <key> <value>openclaw doctor # health checkopenclaw security audit --deep # policy drift check# Tailscalesudo tailscale serve statussudo tailscale serve --bg 18789 # re-enable servesudo tailscale serve --https=443 off # disable serve```## Security Warnings1. **CVE-2026-25253** (CVSS 8.8) — patched in >= 2026.1.29. We run 2026.3.13.2. **29 pages of GitHub Security Advisories** — large attack surface from messaging integrations (all disabled).3. **ClawHub skills** — no mandatory vetting. Treat all as untrusted. Audit before installing.4. **NemoClaw is alpha** — expect instability. The sandbox is the security-critical layer.5. **API keys** — never paste in chat. Use env vars or config files with 600 permissions.## Rules- Never enable messaging channels without explicit approval- Never install ClawHub skills without security review- Never expose OpenClaw ports to LAN (Tailscale only)- Always verify sandbox is active before trusting isolation- Rotate gateway token if compromised- Keep OpenClaw updated (check: `openclaw --version`)

Frequently asked questions