OpenClaw OA Operator

Install, configure, operate, and productize OA monitoring and self-heal workflows for OpenClaw workspaces. Use when Codex needs to set up or repair `oa-cli`,...

This skill appears to be what it claims (an operator for OA) and contains a harmless smoke-test script, but metadata mismatches mean you should be cautious before running it. Before installing or invoking: 1) Verify the 'oa' CLI and 'curl' are present (the package metadata does not list them but the script and docs require them). 2) Inspect the workspace files referenced (config.yaml, self_heal_rules.yaml, any scripts/ or patches/) for embedded credentials, absolute paths, or external endpoints that could be contacted when 'oa collect' runs. 3) Run the smoke test in an isolated or staging environment first (it runs oa collect and queries localhost API endpoints). 4) If you plan to publish or give the skill broader access, update the skill metadata to declare required binaries and any env vars, and follow the release-readiness guidance to scrub machine-specific data. If you want me to, I can list the exact commands to check the workspace files for secrets or run the smoke test safely in a container.

Type: OpenClaw Skill Name: openclaw-oa-operator Version: 0.1.0 The skill bundle is designed to manage and operate 'OA', an observability and self-healing tool for OpenClaw workspaces. It includes a standard health-check script (scripts/oa_workspace_smoke_test.sh) that interacts with local services and documentation (references/release-readiness.md) that explicitly advises users to remove sensitive or machine-specific data before publishing. No indicators of malicious intent, data exfiltration, or unauthorized execution were found.