openclaw-invariants-check

Validate OpenClaw invariants and detect configuration drift in scheduled maintenance workflows.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Walliiee/agent-harness --skill openclaw-invariants-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-invariants-check
Source: https://github.com/Walliiee/agent-harness/tree/main/skills/openclaw-invariants-check
Command: npx skills add https://github.com/Walliiee/agent-harness --skill openclaw-invariants-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a stable OpenClaw setup by checking that key invariants, routing rules, feature flags, and memory hygiene remain intact over time.

Core Features & Use Cases

  • Weekly invariant validation: Verifies that the system still behaves as expected after changes, upgrades, or maintenance.
  • Launchd-driven execution: Runs as a scheduled macOS maintenance task through a LaunchAgents plist.
  • Drift and regression guardrail: Useful when you want to detect broken routing, frontmatter regressions, or missing safeguards before they cause user-facing failures.

Quick Start

Ask the agent to run the OpenClaw invariant check and report any failures in the launchd-managed maintenance workflow.

Frequently Asked Questions about openclaw-invariants-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect routing drift and configuration regressions after an upgrade?

Detect routing drift by validating OpenClaw invariants through a launchd-managed maintenance workflow. This checks routing rules, feature flags, and frontmatter to catch regressions before user-facing failures occur.

What is configuration drift detection in feature flags and routing?

Configuration drift detection verifies that feature flags, routing rules, and frontmatter remain intact over time. It validates system invariants to ensure setup stability and expected behavior after system changes or maintenance.

How do I schedule weekly invariant validation on macOS?

Schedule weekly invariant validation using a macOS LaunchAgents plist for launchd-driven execution. This runs scheduled maintenance tasks to verify agent system integrity and root memory hygiene deterministically.

Does invariant checking require launchd execution on macOS?

Yes, invariant checking requires launchd execution and wrapper-based auditing to produce deterministic exit-code driven results. This scheduled macOS maintenance task validates router coverage and memory hygiene.

What is the best way to verify agent system integrity after maintenance?

The best way to verify agent system integrity is running OpenClaw invariant checks via launchd. This applies wrapper-based auditing to validate frontmatter, routing, and root memory hygiene deterministically.