OpenClaw OA Operator

Use this skill to operate OA as an observability and self-heal layer for OpenClaw. Focus on stable workflows, explain what the data means, and keep public packaging separate from machine-specific local setup.

Quick Start

• Inspect the workspace for config.yaml, self_heal_rules.yaml, scripts/, patches/, pipelines/, and any dashboard override such as dashboard-zh/.
• Determine whether the user wants local operations, dashboard refinement, or publishable packaging. Do not switch UI structure without explicit approval once the user picks a preferred layout.
• Prefer the simplest stable path: use upstream OA behavior unless the workspace already carries justified overrides.
• Run the smallest useful verification after each meaningful change: API check, script smoke check, or dashboard screenshot.
• Use scripts/oa_workspace_smoke_test.sh for a minimal end-to-end workspace check when OA is already configured.

Operate OA Locally