openCLAW Manager

Validate openCLAW gateway profiles for health, parity, and sandbox readiness.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cgk-platform/cgk --skill openclaw-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openCLAW Manager
Source: https://github.com/cgk-platform/cgk/tree/main/openclaw-skills/nova/openclaw-manager
Command: npx skills add https://github.com/cgk-platform/cgk --skill openclaw-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, python3, and includes scripts (resource) components.

What problem does it solve?

Cross-profile health, parity, post-update, and sandbox validation for openCLAW gateway deployments, enabling teams to detect drift, misconfigurations, and readiness issues across all three profiles.

Core Features & Use Cases

  • Unified cross-profile health checks across cgk, rawdog, and vitahustle gateways.
  • Parity and post-update validation to ensure consistent configurations and sane update flows.
  • Sandbox- and environment-check automation to verify docker env variables and deployment readiness.

Quick Start

Run the oc-health.sh script to perform a full cross-profile health check across all three openCLAW gateways.

Frequently Asked Questions about openCLAW Manager

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

FAQPage Schema
How do I check openCLAW gateway health across multiple profiles?

To check openCLAW gateway health across multiple profiles, run the oc-health.sh script to perform a full cross-profile health check for cgk, rawdog, and vitahustle deployments in local or CI environments.

What is cross-profile configuration parity validation for openCLAW gateways?

Cross-profile configuration parity validation verifies that configurations remain consistent across cgk, rawdog, and vitahustle openCLAW gateways. The oc-parity.sh script detects configuration drift and misconfigurations to ensure deployment uniformity.

How do I automate post-update readiness checks for openCLAW deployments?

To automate post-update readiness checks for openCLAW deployments, use the oc-post-update.sh script. It validates sane update flows and confirms gateway readiness across all profiles after routine updates are applied.

Do I need python3 and jq to run openCLAW sandbox checks?

Yes, you need python3 and jq installed as dependencies to run openCLAW sandbox checks. The oc-sandbox-check.sh script requires these tools to verify docker environment variables and ensure deployment readiness.

Can I use these openCLAW validation scripts in automated CI environments?

Yes, you can use these openCLAW validation scripts in automated CI environments. The discrete scripts for health, parity, sandbox checks, and log management support both local execution and automated CI routine checks.

What is the best way to detect configuration drift in openCLAW gateways?

The best way to detect configuration drift in openCLAW gateways is using the unified parity checks. The oc-parity.sh script compares cross-profile configurations across cgk, rawdog, and vitahustle deployments to identify inconsistencies and drift.