Tencent SkillHub · Communication & Collaboration

OpenClaw Ops

Use when diagnosing, repairing, or maintaining an OpenClaw Gateway on the same machine. Designed for rescue agents to fix a down gateway or check operational...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Use when diagnosing, repairing, or maintaining an OpenClaw Gateway on the same machine. Designed for rescue agents to fix a down gateway or check operational...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: README.md, README_CN.md, SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.2.1

Provenance

Publisher: dinstein
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 21 sections Open source page

Design Philosophy

This skill serves two core scenarios and nothing else: Rescue — The main OpenClaw Gateway is down or broken. You (the rescue agent) need to diagnose the root cause, fix it, and bring the gateway back online. Health Check — The main OpenClaw Gateway is running. You need to verify its operational health, clean up resources, or perform maintenance tasks like upgrades. What this skill is NOT for: Day-to-day business configuration (adding channels, configuring agents, setting up integrations) Application-level issues (agent behavior, prompt tuning, skill management) Initial deployment or first-time setup (use openclaw daemon install and openclaw configure) Principle: Diagnose → Judge → Act → Verify. Never skip steps.

Platform Detection

Detect the platform first — commands differ between Linux (systemd) and macOS (launchd): OS=$(uname -s) # "Linux" or "Darwin" echo "Platform: $OS"

Port Detection

Do NOT assume port 18789. Detect the actual configured port first: PORT=$(openclaw config get gateway.port 2>/dev/null | grep -oE '[0-9]+') PORT=${PORT:-18789} # fallback to default only if config unavailable echo "Gateway port: $PORT" Use $PORT in all port-related commands throughout this guide.

Scenario A: Rescue (Gateway Down)

Follow these sections in order when the main gateway is not running.

A1. Assess the Situation

# Is the service running at all? # Linux: systemctl --user status openclaw-gateway # macOS: launchctl list | grep openclaw # Is the process alive? pgrep -af openclaw # Is the port listening? # Linux: ss -tlnp | grep $PORT # macOS: lsof -iTCP:$PORT -sTCP:LISTEN

A2. Check Logs for Root Cause

Common crash patterns

Log patternMeaningFixEADDRINUSEPort already in useFind conflicting process: ss -tlnp | grep $PORT (Linux) or lsof -iTCP:$PORT (macOS), kill it or change portENOMEM / JavaScript heapOut of memoryCheck free -h (Linux) / vm_stat (macOS), kill memory hogs or increase Node heapSyntaxError in configBad JSON in openclaw.jsonSee A3 Config RepairMODULE_NOT_FOUNDMissing dependencycd $(npm root -g)/openclaw && npm install --productionInvalid token / 401 / 403Auth failureCheck tokens in env file or systemd drop-inECONNREFUSEDUpstream unreachableCheck network, Tailscale, API endpoints

A3. Config Repair

Always backup first: cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak.$(date +%s) JSON syntax validation: python3 -c "import json; json.load(open('$HOME/.openclaw/openclaw.json'))" Common JSON issues: trailing comma, missing quotes, unescaped characters. The error message shows line/position. Config schema validation: openclaw config get gateway # check gateway config section openclaw config get channels # check channels config section Common config errors: SymptomLikely causeFix"device identity mismatch"Service env token ≠ config tokenSync tokens between env file and openclaw.jsonAgent not routingbindings misconfiguredBindings go at top-level, not inside agents.list[].routing After fixing, validate: python3 -c "import json; json.load(open('$HOME/.openclaw/openclaw.json')); print('JSON OK')" openclaw status

A4. Check Resources

# Disk space df -h ~ # Memory (Linux) free -h # Memory (macOS) vm_stat | head -5 # Node.js available? node -v which openclaw openclaw --version

A5. Restart and Verify

Only restart after identifying and fixing the root cause. Linux: systemctl --user restart openclaw-gateway sleep 3 systemctl --user status openclaw-gateway journalctl --user -u openclaw-gateway -n 20 --no-pager macOS: launchctl kickstart -k "gui/$(id -u)/com.openclaw.gateway" sleep 3 launchctl list | grep openclaw tail -20 ~/.openclaw/logs/gateway.log If service won't start at all: # Manual foreground start for better error output openclaw gateway start Final verification: openclaw status openclaw doctor --non-interactive

Scenario B: Health Check (Gateway Running)

Follow these sections for routine operational checks on a running gateway.

B1. Quick Health Check

# Comprehensive check — start here openclaw doctor # If issues found, auto-fix safe ones openclaw doctor --fix

B2. Update & Upgrade

# Check versions CURRENT=$(openclaw --version) LATEST=$(npm view openclaw version) echo "Current: $CURRENT Latest: $LATEST" Perform update: # 1. Save doctor baseline openclaw doctor --non-interactive 2>&1 | tee /tmp/doctor-before.txt # 2. Backup config cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.pre-upgrade.$(date +%s) # 3. Update npm update -g openclaw openclaw --version # 4. Restart # Linux: systemctl --user restart openclaw-gateway # macOS: launchctl kickstart -k "gui/$(id -u)/com.openclaw.gateway" # 5. Compare doctor output sleep 5 openclaw doctor --non-interactive 2>&1 | tee /tmp/doctor-after.txt diff /tmp/doctor-before.txt /tmp/doctor-after.txt Rollback: npm install -g openclaw@<previous_version> cp ~/.openclaw/openclaw.json.pre-upgrade.<timestamp> ~/.openclaw/openclaw.json # Restart (platform-appropriate command above)

B3. Session & Disk Cleanup

# Check disk usage per agent for agent_dir in ~/.openclaw/agents/*/; do agent=$(basename "$agent_dir") size=$(du -sh "$agent_dir/sessions/" 2>/dev/null | cut -f1) count=$(find "$agent_dir/sessions/" -name "*.jsonl" 2>/dev/null | wc -l) echo "$agent: $size ($count transcripts)" done # Auto-fix orphans openclaw doctor --fix # Manual cleanup: old transcripts (>30 days) find ~/.openclaw/agents/*/sessions/ -name "*.jsonl" -mtime +30 -exec ls -lh {} \; # Review, then delete if safe: find ~/.openclaw/agents/*/sessions/ -name "*.jsonl" -mtime +30 -delete

B4. Backup

BACKUP_DIR=~/openclaw-backup-$(date +%Y%m%d-%H%M%S) mkdir -p "$BACKUP_DIR" # Core files cp ~/.openclaw/openclaw.json "$BACKUP_DIR/" [ -f ~/.openclaw/env ] && cp ~/.openclaw/env "$BACKUP_DIR/" || echo "No env file (tokens may be in systemd drop-in or plist)" cp -r ~/.openclaw/agents "$BACKUP_DIR/" cp -r ~/.openclaw/devices "$BACKUP_DIR/" cp -r ~/.openclaw/workspace "$BACKUP_DIR/" # Service config if [ "$(uname -s)" = "Linux" ]; then cp ~/.config/systemd/user/openclaw-gateway.service "$BACKUP_DIR/" 2>/dev/null cp -r ~/.config/systemd/user/openclaw-gateway.service.d "$BACKUP_DIR/" 2>/dev/null elif [ "$(uname -s)" = "Darwin" ]; then cp ~/Library/LaunchAgents/com.openclaw.gateway.plist "$BACKUP_DIR/" 2>/dev/null fi echo "Backup saved to $BACKUP_DIR"

B5. Tailscale Serve Check

If OpenClaw uses Tailscale Serve as reverse proxy: tailscale status tailscale serve status curl -s -o /dev/null -w "%{http_code}" http://localhost:$PORT/healthz || echo "Gateway not reachable on localhost" Reconfigure if broken: tailscale serve reset tailscale serve https / http://localhost:$PORT tailscale serve status

Troubleshooting Quick Index

SymptomPathGateway won't startA1 → A2 → A3 → A5Gateway crashedA2 (logs) → A4 (resources) → A3 (config) → A5 (restart)Config broken after editA3 → A5Disk filling upB3After upgrade something brokeB2 (rollback)Tailscale not proxyingB5

openclaw doctor Reference

FlagEffect(none)Interactive health check--fixApply safe repairs (orphan cleanup, stale locks)--forceAggressive repairs (may overwrite custom service config)--deepScan system for extra gateway installs--non-interactiveNo prompts, safe migrations only --fix repairs: orphan transcripts, stale session locks, legacy key migration. --fix does NOT: modify openclaw.json, change service files (unless --force), delete workspace files.

Key Commands

CommandPurposeopenclaw statusQuick status: running, version, basic infoopenclaw doctorDeep health check: state, channels, plugins, skillsopenclaw doctor --fixHealth check + auto-repair safe issuesopenclaw gateway startStart gateway in foreground (for debugging)openclaw daemon installInstall as persistent service (systemd/launchd)openclaw daemon restartRestart the serviceopenclaw config get <path>Read config valueopenclaw config set <path> <value>Write config value

Safety Rules

Always check logs before changing anything — understand the problem first Always backup before editing config — cp with timestamp suffix Always validate JSON after editing — one bad comma kills the service Never print secrets — check env file exists, don't cat it Never delete workspace files — use trash if you must remove something Always verify after restart — status + logs, don't assume it worked Destructive operations require confirmation — ask the user before wiping data

File Layout

~/.openclaw/ ├── openclaw.json # Main config ├── openclaw.json.bak # Auto-backup ├── env # Environment variables (secrets) ├── logs/ # macOS: launchd log output ├── agents/ # Per-agent configs │ └── <agent>/agent/ │ ├── auth-profiles.json │ └── models.json ├── devices/ │ └── paired.json ├── workspace/ # Agent workspace └── sessions/ # Session logs # Linux: ~/.config/systemd/user/ ├── openclaw-gateway.service └── openclaw-gateway.service.d/ └── env.conf # macOS: ~/Library/LaunchAgents/ └── com.openclaw.gateway.plist

Category context

Messaging, meetings, inboxes, CRM, and teammate communication surfaces.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

3 Docs

SKILL.md Primary doc
README_CN.md Docs
README.md Docs