Claude Skill

digitalknk/openclaw-runbook

OpenClaw Runbook repository with 574 stars and 51 forks. A runbook/operational guide last updated in 2026 for system documentation and procedures.

Overview

Stars1,099
Forks98
LanguageAstro
Last pushed2026-05-26
Last synced2026-07-03
View on GitHub

Repository

Ownerdigitalknk
Repositoryopenclaw-runbook
Full namedigitalknk/openclaw-runbook
Repo ID1,154,147,877

Install this Skill

git clone https://github.com/digitalknk/openclaw-runbook.git

Registry

Typeopenclaw_skill
Quality score80/100
Verificationreadme_parsed
Last verified2026-06-04
Platforms
OpenClaw
Capabilities
code-reviewpdfmemorysearchvideoterminalworkflowai-agentsopenclawrunbook
Detected files
README.mdexamplespackage.json
Config keys
PACKAGE_JSON

Summary

OpenClaw Runbook is a GitHub repository with 574 stars and 51 forks, last updated in February 2026. It appears to be a runbook or operational guide, likely related to the OpenClaw project or system.

Chinese description

非官方OpenClaw操作手册,用于日常运行代理,避免烧钱、暴露网关或信任随机自动化。

Key features

  • Runbook/operational guide format
  • Popular repository with 574 stars
  • Active with recent updates (2026)
  • 51 forks indicating community usage

Use cases

  • System operation documentation
  • Incident response procedures
  • Administrative task guidance
  • Team knowledge sharing

README excerpt

# OpenClaw Runbook > Checked against OpenClaw at commit `5dccba7405` (`2026-05-25`) > Example config based on a working `2026.5.x` setup This repo is a practical runbook for running OpenClaw day to day without burning money, exposing your gateway, or trusting random automation you did not inspect. It is not official OpenClaw documentation. It is not a universal best setup. It is the way I run OpenClaw after enough broken configs, noisy agents, and avoidable risk to want something predictable. ## What this is - A runbook for people who want OpenClaw to run for weeks, not minutes - Opinionated guidance on models, access, memory, automation, and guardrails - Tailscale-first for dashboard/control access - Skeptical of third-party skills by default - Written from the post-honeymoon phase ## What this is not - A beginner replacement for the official docs - A model leaderboard - A ClawHub install guide - A claim that my exact config is right for everyone ## Access stance My setup uses Tailscale as the normal access path, including when I am local. The Gateway stays loopback-bound, and Tailscale handles remote access. If you do not want to sign up for Tailscale, keep OpenClaw local and use a messaging channel such as Telegram for remote use. Avoid public ports and casual LAN exposure unless you know exactly what boundary you are accepting. ## Skills stance I do not recommend blindly installing third-party skills from ClawHub. Use ClawHub as a discovery and source-reading tool. Find an idea, inspect the source, then ask your agent to rebuild a local skill for your setup. That is slower than clicking install, but it is safer than trusting unknown code, broad tool assumptions, hidden behavior, or token-heavy abstractions. The example config keeps `clawhub` disabled o

Topics

Explore more

Data from GitHub. Synced on 2026-07-03