OC Evolver Restart Loop Fix

Repair Evolver restart storms caused by singleton lock/PID false positives and service restart policy mismatch.

This skill appears to do what it claims, but the instructions are intentionally vague and imply privileged on-host changes (clearing lock files, patching guard logic, restarting services). Before installing or letting an agent run this skill: 1) require the agent to present exact commands and file paths it will run and get explicit human approval for each privileged step; 2) run fixes first in a staging/test environment or take backups/snapshots; 3) constrain the scope by specifying the service manager (systemd/upstart), service name, and exact lock/PID file locations; 4) ask the skill (or author) for a sample patch diff and verification steps; and 5) ensure any external artifacts redact infrastructure/identity details as recommended. If you don't have a retained, trusted human operator to vet changes, treat this as higher risk.

Type: OpenClaw Skill Name: oc-evolver-restart-loop-fix Version: 0.1.0 The skill bundle describes a legitimate system administration task: fixing a service restart loop caused by PID/lock file issues. The instructions in SKILL.md outline steps like inspecting service state, clearing stale locks, patching a lock guard, and restarting the service. While these actions involve system-level interaction, they are directly aligned with the stated benign purpose. There is no evidence of data exfiltration, malicious execution, persistence, or prompt injection designed to harm or mislead the agent. The 'Safety' section even reinforces benign intent by advising minimal, reversible changes and redaction of sensitive details.