openclaw-guardian
Deploy and manage a Guardian watchdog process for OpenClaw Gateway. Provides automated health monitoring, self-repair via `doctor --fix`, git-based workspace rollback, daily snapshots, and optional Discord alerting. Use when a user wants to harden their OpenClaw instance against crashes, config corruption, or bad workspace edits — or when setting up Guardian for the first time on a new server/container.
What this skill does
# OpenClaw Guardian Guardian is a standalone bash watchdog that keeps OpenClaw Gateway alive 24/7. **Repair ladder:** 1. Detect Gateway down (every 30s) 2. Run `openclaw doctor --fix` (up to 3 attempts) 3. If still down → `git reset --hard` to last stable commit, restart Gateway 4. If all fails → cooldown 300s, resume monitoring 5. Daily automatic git snapshot of workspace ## Setup Steps ### 1. Initialize git (required for rollback) ```bash cd ~/.openclaw/workspace git config --global user.email "[email protected]" git config --global user.name "Guardian" git init && git add -A && git commit -m "initial" ``` Skip if repo already exists. Without git, doctor --fix still works; rollback is skipped. ### 2. Install guardian.sh Copy `scripts/guardian.sh` from this skill to `~/.openclaw/guardian.sh`: ```bash cp scripts/guardian.sh ~/.openclaw/guardian.sh chmod +x ~/.openclaw/guardian.sh ``` ### 3. Start Guardian **Container / no systemd (nohup):** ```bash nohup ~/.openclaw/guardian.sh >> /tmp/openclaw-guardian.log 2>&1 & ``` **Linux VPS with systemd:** See `references/setup.md` → Pattern B. ### 4. Auto-start on container restart Add to `~/.openclaw/start-gateway.sh` (before the final `exec` line): ```bash pkill -f "guardian.sh" 2>/dev/null || true nohup /home/ubuntu/.openclaw/guardian.sh >> /tmp/openclaw-guardian.log 2>&1 & ``` ### 5. Optional: Discord alerts ```bash export DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..." ``` Or add to `start-gateway.sh` as a persistent export. ## Verify ```bash pgrep -a -f "guardian.sh" # confirm process running tail -f /tmp/openclaw-guardian.log # watch live logs ``` ## Configuration All settings via environment variables. Defaults work out of the box. See `references/setup.md` for full variable reference, systemd config, and architecture diagram. ## Notes - Guardian coexists with `gw-watchdog.sh` — run both for layered resilience - Rollback targets the 2nd-newest non-auto commit (skips daily-backup, rollback, auto-backup commits) - Log path: `/tmp/openclaw-guardian.log`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.