JoeVault

Audit, classify, and quarantine stale paths after a profile switch, account migration, reset, or workspace move. Use when OpenClaw, Claude, WSL, Windows home...

Security Scan

The skill's code and instructions match its stated purpose: it audits file paths for references to an old location and moves (quarantines) chosen paths into an archive with a manifest — there is no network exfiltration or unrelated credential access requested.

Purpose & Capability

The name and description describe auditing and quarantining stale paths; the included scripts (audit_paths.py and quarantine_path.py) perform exactly those tasks (scanning paths, reporting metadata, and moving paths into an archive). There are no unrelated requirements (no external credentials or binaries).

Instruction Scope

SKILL.md instructs running the two scripts and to inspect results before moving. The audit script scans the provided search-root paths and reads file contents to find references to the stale root — this is expected for the stated purpose but means the script will read arbitrary files under the supplied search roots (which can include sensitive configuration). The instructions do not send data elsewhere.

Install Mechanism

No install spec — instruction-only with included Python scripts. Nothing is downloaded or installed from external URLs. This is low-risk from an installation-perspective; the only runtime requirement is a Python 3 interpreter present on the system.

Credentials

The skill requests no environment variables, credentials, or config paths. The scripts operate solely on paths supplied by the user — proportional to the stated purpose.

Persistence & Privilege

always:false (default) and no special privileges requested. However, the scripts do modify the filesystem (shutil.move) and will move/rename user data when invoked. While autonomous invocation is allowed by default, that is a platform behavior rather than a property of the skill; exercise caution if you permit the agent to run skills autonomously because this skill can change or move files.

Assessment

This skill appears coherent and does what it claims, but it will read and move files you point it at — including configuration files under the search roots. Before running: 1) inspect the audit output (it prints a JSON report) and limit --search-root to only the directories you want scanned; 2) do not run the quarantine script on large or ambiguous trees without inventorying them first; 3) run a safe test (small dummy folder) to confirm behavior; 4) do not run as an elevated user (root/Administrator) unless absolutely necessary; 5) keep backups of important data before moving anything; and 6) if you do not trust the agent to act autonomously, disable autonomous skill invocation or only invoke the scripts manually.

Archive old state without breaking live state.

Quick start

1. Run scripts/audit_paths.py with the current root, stale root, and candidate relative paths.
2. Classify each stale path as quarantine now, leave for inventory, or keep active.
3. Quarantine only small, clearly inactive state first.
4. Inventory large stale workspaces before moving them.
5. When moving anything, use scripts/quarantine_path.py so the archive gets a manifest entry.

Workflow

1. Audit first

Run the audit script before any move:

python3 scripts/audit_paths.py \
  --current-root /mnt/c/Users/Joseph \
  --stale-root /mnt/c/Users/Joe \
  --candidate .openclaw \
  --candidate openclaw-workspace \
  --search-root /mnt/c/Users/Joseph/.openclaw \
  --search-root /mnt/c/Users/Joseph/openclaw-workspace

What to look for:

• stale paths that still exist
• live configs that still reference stale paths
• symlinks that still point at old homes
• large directories that should not be moved blindly
• recent activity inside stale paths

2. Classify the stale paths

Use references/classification.md when deciding what to do.

Default rules:

• small old state directories like .openclaw or .claude are usually safe to quarantine first
• large workspaces, model folders, training outputs, or media trees must be inventoried before moving
• anything still referenced by live config is not ready for quarantine

3. Quarantine conservatively

Use quarantine for paths that are clearly inactive:

python3 scripts/quarantine_path.py \
  --source /mnt/c/Users/Joe/.openclaw \
  --archive-root /mnt/c/Users/Joseph/Archives/profile-switch-2026-03-31 \
  --label old-joe-openclaw

The script:

• creates the archive root if needed
• refuses to overwrite an existing target
• moves the source into the archive
• appends a manifest entry to MANIFEST.md

4. Inventory large trees before touching them

For large stale workspaces, get a top-level size view first:

du -sh /path/to/stale-workspace/* 2>/dev/null | sort -h | tail -n 30

Do not move a massive stale workspace until you know whether it contains:

• model weights
• voice assets
• training outputs
• media renders
• reference repos
• recent work

5. Verify the live system after every move

After any quarantine step, check:

• current symlinks still resolve correctly
• active configs no longer reference old paths
• the live service still starts
• the archive manifest records what moved and why

Notes

• Prefer rename-and-quarantine over deletion.
• Prefer one small safe move over one giant risky move.
• If the user asks to “clean it all up,” still audit first.
• If a stale workspace had recent activity, treat it as a reference archive candidate, not trash.