2.6k
GitHub Stars
5
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill workspace-organization- _meta.json335 B
- maintenance-audit.sh3.6 KB
- README.md5.0 KB
- setup.sh2.1 KB
- SKILL.md8.3 KB
Overview
This skill automates workspace health checks and enforces organization standards for OpenClaw deployments. It detects common entropy sources—broken symlinks, empty folders, oversized files, and malformed names—and provides actionable cleanup guidance. Use it to keep deployments tidy, reduce backup size, and avoid script breakage caused by messy file layouts.
How this skill works
A maintenance-audit.sh script scans a target workspace (auto-detected or passed as an argument) and reports findings: broken symlinks, empty directories (with exclusions), files above a configurable size threshold, malformed names, disk usage by top-level folder, and recent modifications. A setup.sh initializes a recommended directory structure and docs with naming and cleanup standards. Scripts are cron-friendly so audits can run on a schedule and log results for review before any cleanup actions.
When to use it
- Initialize a new OpenClaw workspace with a standard structure
- Run weekly or monthly automated health checks to prevent entropy
- Perform pre-deployment or pre-backup audits to reduce size and risk
- Debug workspace issues like broken symlinks or scripts failing due to names
- Identify large files and disk bloat for storage optimization
Best practices
- Run the audit regularly via cron and log results to notes/maintenance-log.md
- Do not auto-delete during scheduled audits—review recommendations and approve changes
- Adopt naming conventions (kebab-case) and document exceptions in workspace notes
- Exclude known benign directories (node_modules, .git, .cache) from empty-dir checks
- Adjust the large-file threshold in the script to match your project's needs
Example use cases
- Set a weekly cron job to audit and append results to a maintenance log before CI runs
- Run the audit before creating a backup to identify and offload large artifacts
- Use setup.sh to standardize directories when onboarding a new machine
- Run on-demand audits while troubleshooting a broken subagent or script
- Scan multiple workspaces in a loop when managing several OpenClaw instances
FAQ
No — the audit reports problems and suggests fixes. Cleanup is deliberately user-approved to avoid accidental data loss.
How do I change the large file size threshold?
Edit maintenance-audit.sh and modify the find command size parameter (e.g., change +10M to +50M).