Neura Market Logo

ground-control

Verify OpenClaw after upgrades against an operator-maintained model, cron, and channel ground truth. Use for report-only config integrity, provider liveness, cron integrity, sessio…

Jonathan Jing

@jonathanjing

Install

$ openclaw skills install @jonathanjing/ground-control

ground-control

Post-upgrade verification for OpenClaw. Keeps your system honest after every upgrade.

🛠️ Installation

1. Ask OpenClaw (Recommended)

Tell OpenClaw: "Install the ground-control skill." Installation does not authorize runtime config or cron changes.

2. Manual Installation (CLI)

If you prefer the terminal, run:

openclaw skills install @jonathanjing/ground-control

Permissions & Privileges

This skill requires the following OpenClaw capabilities:

  • gateway config.get — read current config (all phases)
  • gateway config.patch — apply an operator-approved config repair (Phase 1 only)
  • cron list / cron update — verify cron jobs and apply operator-approved repairs (Phase 3)
  • sessions_spawn — smoke test sessions (Phase 2, 4, 5)
  • message send — channel liveness test + summary report (Phase 5)

Change-control behavior: Every run is report-only by default. Present a redacted repair plan and obtain explicit operator approval immediately before any gateway config.patch or cron update.

Security & Redaction: This skill enforces a Zero-Secret Logging protocol.

  • Immediate Redaction: Sensitive nodes (auth, plugins) are stripped from memory after fetching runtime config.
  • Redacted Drift: Mismatches in sensitive fields are reported as [REDACTED_SENSITIVE_MISMATCH].
  • Functional Validation: API keys are tested through functional calls (Phase 2), never through literal comparison.
  • No Persistence: Literal credentials are never written to memory/ files or messaging channels.

Environment variables: None.

When to use

  • After running openclaw update or npm install -g openclaw@latest
  • When you suspect config drift (model changed, cron broken, channel down)
  • Periodic health check via /verify command

Setup

  1. Copy {baseDir}/templates/MODEL_GROUND_TRUTH.md to your workspace root
  2. Fill in your actual config values (models, cron jobs, channels)
  3. (Optional) For large configs, split into refs/ground-truth/*.md sub-files
  4. Add the GROUND_TRUTH sync rule to your AGENTS.md (see README)
  5. Run /verify to test

Files

  • {baseDir}/templates/MODEL_GROUND_TRUTH.md — Ground truth template (copy to workspace root)
  • {baseDir}/scripts/post-upgrade-verify.md — Agent execution prompt for 5-phase verification
  • {baseDir}/scripts/UPGRADE_SOP.md — Upgrade standard operating procedure

Top skills in this category

Free Ride - Unlimited free AI

@shaivpidadi

Manages free AI models from OpenRouter for OpenClaw. Automatically ranks models by quality, configures fallbacks for rate-limit handling, and updates opencla...

49172k

Playwright (Automation + MCP + Scraper)

@ivangdavila

Automates, tests, and debugs browsers with Playwright: locators, auto-waiting, traces, CI runs, and MCP browser control. Use when a test is flaky, times out, or fails only in CI or headless; when a locator matches multiple elements or the wrong one (strict mode violation); when clicks need force, waits become sleeps, or networkidle never settles; for storageState and login setup, request mocking and HAR replay, uploads and downloads, iframes and shadow DOM, popups and dialogs, screenshot diffs that change per machine, trace and report artifacts, sharding a slow suite, device and permission emulation, accessibility checks, driving a real browser through Playwright MCP, extracting data from JS-rendered pages, or porting a Cypress, Puppeteer, or Selenium suite to Playwright. Not for maintaining an existing Cypress or Puppeteer suite (cypress, puppeteer) or for work a plain HTTP request answers (http).

13043k

n8n

@thomasansems

Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.

6121k

google-slides

@byungkyu

Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

3420k

Superpowers Dev Workflow

@wlshlad85

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan → subagent executi...

2129k