Nm Egregore Uninstall Watchdog
v1.0.0Remove the egregore watchdog daemon and clean up all associated files (plist/unit, pidfile, watchdog log)
⭐ 0· 20·1 current·1 all-time
by@athola
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (uninstall watchdog) match the actions in SKILL.md: unloading launchd, stopping/disabling systemd user timer, and removing specific files under ~/ and ~/.config. No unrelated credentials, binaries, or installs are required.
Instruction Scope
Instructions are limited to stopping the user-level service and removing listed files (plists, unit files, pid/log). This is expected for an uninstall guide, but the steps are destructive (rm -f) and assume tilde expansion and user-level context. The guide does not include safety checks, confirmations, backups, or explicit guidance about not running commands as root (which could change affected paths).
Install Mechanism
No install spec or downloaded code — instruction-only. This is the lowest-risk pattern for this purpose.
Credentials
No environment variables, credentials, or config paths are requested. The SKILL.md only references user home paths and user-level systemd/launchctl, which are proportional to an uninstall operation.
Persistence & Privilege
Skill is not always-included and does not request persistent privileges. It instructs user-level service management only; autonomous invocation is allowed by default but is not combined with broad credential access or other red flags.
Assessment
This skill is coherent for removing the egregore watchdog, but the provided commands are destructive. Before running them: 1) Verify the watchdog is actually installed (use the listed launchctl/systemctl verify commands). 2) Run the checks first, and consider backing up any files you might need (~/.egregore/* and the plist/unit files). 3) Do not run these steps with sudo/root unless you intentionally want to affect system-level locations (running as root can change which home directory is expanded and may remove other users' files). 4) If you're unsure, run the rm commands with ls first (e.g., ls -l <path>) or echo the path to confirm targets. 5) Note that this guide assumes standard install locations; if your installation used custom paths, follow your install records instead.Like a lobster shell, security has layers — review code before you run it.
latestvk97azf2nkpr37jw1dngxqn1bwx84q7gy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis