cwd-guardian

Monitors and restores the evolver process working directory. Use when evolver crashes with uv_cwd ENOENT errors or when the evolver process loses its cwd.

Security Scan

The skill's description and runtime instructions claim it will stamp, restore, and start the evolver cwd, but the included code does not implement those actions and instead uses a hardcoded user path — the pieces are inconsistent and the package is likely either broken or mispackaged.

Purpose & Capability

The README/SKILL.md and package description claim the guardian will stamp the cwd, recreate a missing cwd, and start the evolver daemon. The shipped code only verifies a hardcoded path, writes a JSON state file, and checks for running processes; it does not recreate arbitrary missing cwd directories nor start the evolver. The code also hardcodes WORKSPACE = '/Users/foras/.openclaw/workspace', which is user-specific and not declared or configurable in the skill metadata.

Instruction Scope

SKILL.md usage examples point at node skills/cwd-guardian/scripts/guardian.js (start/check) but the package contains index.js and package.json scripts that invoke index.js — the referenced scripts file does not exist. The documentation promises actions (recreate cwd, start evolver) that the code does not perform. The code does execute a shell command (pgrep) to detect processes, which is consistent with process-checking but the overall instruction set and implementation diverge.

Install Mechanism

No install spec; this is instruction + small Node script only. No external downloads or package installs are requested, so install mechanism risk is low.

Credentials

The skill declares no required environment variables or secrets, which matches the lack of credential usage. However, the code uses a hardcoded absolute workspace path under a specific user ('/Users/foras/...') instead of respecting declared or configurable paths, making it non-portable and potentially surprising (it will only work on that specific filesystem layout).

Persistence & Privilege

The skill does not request permanent 'always' inclusion, does not modify other skills, and only writes a JSON state file under the workspace path. Autonomous invocation is allowed by default (normal for skills) but there is no evidence of privileged or system-wide modifications beyond its own state file.

What to consider before installing

Do not install or run this as-is on production systems. The package is inconsistent: SKILL.md points to non-existent scripts and promises behavior (recreating the cwd, starting evolver) that the included index.js does not implement. The code is hardcoded to a specific user path (/Users/foras/.openclaw/workspace), so it will only work on that environment and could fail or write state in unexpected places on other machines. Before using: (1) ask the author for a corrected, documented version or a configurable WORKSPACE via env var; (2) verify the script's behavior locally in a safe environment (check exactly what files it writes and that it won't remove anything); (3) if you expect automatic starting/recreating functionality, request confirmation and a code update implementing that behavior; (4) prefer code that uses configurable paths and avoids hardcoded user directories. If you don't trust the source, avoid running the script at all.

Protects the evolver daemon from uv_cwd ENOENT crashes by:

1. Stamping the current valid cwd to a pidfile
2. On restart, verifying the cwd exists before launching evolver
3. Rebuilding the cwd from the stamped path if it was deleted

Usage

node skills/cwd-guardian/scripts/guardian.js start
node skills/cwd-guardian/scripts/guardian.js check

Logic

• start: Records current working directory to ~/.openclaw/workspace/memory/evolution/cwd_guardian.pid, then starts the evolver daemon
• check: Reads the pidfile, verifies the cwd exists, recreates it if missing, then starts the evolver daemon if not running
• verify: Returns exit code 0 if cwd is valid, 1 if recreated