Workspace Hygiene Publish

v0.1.0

Audit and maintain workspace file structure, memory quality, and project documentation. Use when: cleaning up the workspace, running a file audit, checking m...

0· 151·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the included Python audit script and documentation: the skill scans workspace structure, memory files, and project READMEs and can produce/modify local hygiene reports. Required binary (python3) and no credentials are proportionate to the stated task.
Instruction Scope
SKILL.md and audit.md explicitly describe filesystem checks and the script implements those checks. The instructions limit actions to the workspace directory (reading files, flagging issues, writing a report, and optionally merging timestamped memory files). There are no instructions to read unrelated system config, secret stores, or to send data externally.
Install Mechanism
No install spec (instruction-only + bundled script). That minimizes install-time risk; the only runtime action is executing the included hygiene.py with python3.
Credentials
No environment variables, credentials, or external endpoints are requested. The script operates on files within the specified workspace path only, which is appropriate for a workspace hygiene tool.
Persistence & Privilege
always is false and the skill is user-invocable; the SKILL.md suggests installing into skills/ but that is normal for a tool intended to run per-workspace. The tool writes reports and (with --fix) can merge memory files, but it does not modify other skills or global agent configs.
Assessment
This skill appears coherent: it reads and writes files only inside the provided workspace and does not contact external services or request credentials. Before installing or running: (1) review the hygiene.py source yourself or run it with --report-only to inspect findings without applying fixes; (2) back up the workspace (or run against a copied workspace) before using --fix, since the fix mode may merge timestamped memory files into date files and write a report at projects/system/hygiene-YYYY-MM-DD.md; (3) avoid running it against workspaces containing secrets you don't want scanned or modified; and (4) if you plan to install globally, be aware the script will be available to any agent that can run it—use normal least-privilege practices. Overall: coherent and appears safe for local use with standard precautions.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ac89txw7qy6jr7zhmma8fx182xrjx

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🧹 Clawdis
OSLinux · macOS
Binspython3

Comments