Workspace Organization - Automated Health Checks
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If pointed at a broad or sensitive directory, the audit may list private file paths, disk usage, and recent changes in its output.
The script runs local filesystem tools over the selected workspace path. This is expected for an audit skill, but the chosen path determines how much local filesystem metadata is scanned and displayed.
if [ -n "$1" ]; then
WS="$1"
...
BROKEN=$(find "$WS" -xtype l 2>/dev/null || true)
...
du -sh "$WS"/* 2>/dev/null | sort -hRun it only against the intended OpenClaw workspace or another directory you deliberately want audited.
Running setup in an existing workspace could replace existing README or cost-tracking placeholder files at the listed paths.
The setup script creates standard directories and placeholder files, including writing fixed content to named files. This is purpose-aligned setup behavior, but it can overwrite those files if they already exist.
cat > "$WS/notes/cost-tracking.md" << 'EOF' # Cost Tracking Log
Use setup.sh mainly for a fresh workspace, or back up/check the target files before running it in an existing workspace.
A maintenance log may accumulate names and paths of private workspace files, which could later be read by users or agents with access to the notes directory.
The recommended scheduled audit stores audit findings in a persistent local notes file. Those findings can include local file paths and recent-change metadata.
--task "Run workspace maintenance audit: bash skills/workspace-organization/maintenance-audit.sh. Log findings to notes/maintenance-log.md"
Review the maintenance log location and avoid logging audit output from directories containing sensitive filenames if that is a concern.
If enabled, the audit will continue running weekly until the cron task is removed.
The skill recommends a recurring scheduled audit. This is disclosed and fits the maintenance purpose, but it introduces ongoing automated activity.
Schedule automated audits (recommended): ```bash openclaw cron add \ --name "Weekly Workspace Audit" \ --schedule "0 4 * * 0"
Only add the cron task if you want recurring audits, and remove or disable it when no longer needed.