Custodian

Autonomously monitors OpenClaw system health, fixes log errors, initializes skills, registers tasks, and performs overnight maintenance to surface unresolved...

Custodian's behavior is internally consistent with a system-maintenance role, but it performs high-impact operations: it will read gateway logs and many skill data dirs, edit cron entries, create/rotate JSONL files, and can generate gateway tokens or refresh OAuth. Before installing: (1) verify you trust the source repository (the SKILL.md references a GitHub repo); (2) back up your cron/jobs.json, gateway config, and any critical skill data; (3) run the skill manually (custodian.scan.light / custodian.scan.deep) in a controlled environment to review proposed fixes rather than allowing full autonomous repair; (4) inspect references/known_issues.json and custodian-repair.plan to confirm auto-fix commands are acceptable for your environment; (5) consider disabling autonomous invocation until satisfied, and ensure downstream collaborator skills (Sift, Vesper, Mentor) are also trustworthy. If you want a stricter assessment, provide the actual openclaw binary implementations for 'openclaw doctor/cron' or logs showing how tokens are stored/used — that would raise confidence to high.

Type: OpenClaw Skill Name: ocas-custodian Version: 1.0.0 The ocas-custodian skill is classified as suspicious due to its high-privilege administrative capabilities, including the ability to modify cron jobs, generate gateway authentication tokens, and execute shell commands for autonomous repairs (SKILL.md, known_issues.json). While these functions support its stated purpose of system maintenance, the broad control over the environment and the potential for shell injection via log-based triggers pose a security risk. Furthermore, the inclusion of a self-update mechanism and a web-search-based learning protocol (README.md) introduces additional supply chain and prompt-injection vectors.