C Task Cleanup

v1.0.0

Automatically scans and cleans completed C tasks weekly, compressing insights into MEMORY.md and generating cleanup reports.

0· 66·1 current·1 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
Name/description match the implementation. The handler reads a C-task markdown file, extracts completed items, compresses 'insights' into a MEMORY.md, clears the completed section, and writes a cleanup report — all consistent with the declared purpose.
Instruction Scope
SKILL.md and handler.js expect specific user-local paths (e.g., ~/Desktop/任务流/C-待办任务池.md and ~/.openclaw/workspace/memory). The script reads and overwrites the task file and writes logs; SKILL.md shows a concrete manual run path and a cron file location. This is expected for a local cleanup tool but you should note it will modify your files and there is no built-in backup step.
Install Mechanism
No install spec; the skill is instruction-only with a single JS handler. No external downloads or package installs are performed by the skill itself.
Credentials
No credentials or environment variables are requested. The code uses process.env.HOME implicitly to build file paths — normal for a local utility but worth noting because it will operate on files under your HOME directory.
Persistence & Privilege
The skill does not request 'always: true', does not modify other skills or global agent settings, and does not require elevated privileges. It will run only when invoked (or scheduled by a host cron), which matches its purpose.
Assessment
This skill appears coherent and local-only, but it will read and overwrite files in your HOME (the C task markdown, a MEMORY.md under ~/.openclaw, and log files on your Desktop). Before enabling or scheduling it: (1) review the paths in handler.js and update them if they don't match your environment, (2) create backups of your C-待办任务池.md, (3) consider testing on a copy to confirm parsing/clearing behaves as you expect, and (4) if you want safety, add a pre-check or backup step to the script so you can revert accidental changes.

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

latestvk9777j0rb5213hcqxzem98f27x83x98e

License

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

Comments