workspace-maintenance

What This Skill Does

The workspace-maintenance skill is a sophisticated toolkit designed to preserve organizational integrity within your project directories. As projects scale, the accumulation of markdown notes, outdated snapshots, and progress logs often leads to 'documentation sprawl,' which diminishes discoverability and cognitive efficiency. This skill provides an automated, non-destructive framework to audit, categorize, and archive stale files while maintaining the visibility of critical control files. By adhering to a strict, reversible workflow, it ensures that your root directory remains clean and actionable without ever risking the permanent deletion of project assets.

Installation

To integrate this skill into your environment, use the OpenClaw terminal to run the following installation command:

clawhub install openclaw/skills/skills/houseofjuici/workspace-maintenance

This command fetches the necessary scripts and dependencies from the openclaw/skills repository, ensuring your agent has access to the specialized audit scripts required for safe directory management.

Use Cases

This skill is ideal for:

• Developers managing long-running projects with excessive documentation.
• Technical writers needing to update project indexes after significant architectural shifts.
• Teams requiring structured, versioned storage for historical progress snapshots and session-specific hygiene logs.
• Maintaining root directory cleanliness during intensive development sprints where task trackers and control files must remain constant.

Example Prompts

1. "Perform a workspace maintenance cycle, move outdated snapshots to the archive, and generate the final dry-run deletion list for my review."
2. "Update the project index for the new documentation categories and reconcile the task tracker with the latest session history."
3. "Scan the root directory for stale progress logs and prepare a manifest for archival in the general-progress bucket."

Tips & Limitations

• The workspace-maintenance skill is inherently safe because it never performs permanent deletions; it only generates recommendations for human review.
• Always review the 'dry-run' report before finalizing any batch moves to ensure that critical files are not inadvertently archived.
• Keep identity and root-level control files as is; the skill is hard-coded to ignore these items to prevent system instability.
• Ensure your environment variables are configured correctly so the skill has read/write access to the specific archive paths within your project structure.