Laundry
v2.0.1Track laundry loads, view usage stats, and export reports in multiple formats. Use when logging wash cycles, reviewing patterns, exporting schedules.
⭐ 0· 173·0 current·0 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description, SKILL.md, and scripts/script.sh are coherent: the tool logs laundry entries, shows stats, searches history, and exports JSON/CSV/TXT to a local data directory (~/.local/share/laundry). No unrelated credentials, binaries, or external services are requested.
Instruction Scope
SKILL.md instructs the agent to use the local `laundry` CLI and shows outputs based on $DATA_DIR; the included script reads/writes only to that directory and uses common shell tools (grep, tail, du, wc). I did not find instructions to read unrelated system files or to transmit data externally in the visible content.
Install Mechanism
No install spec is provided and the skill is instruction-first with a helper script. Nothing is downloaded or installed by the skill metadata, which reduces risk.
Credentials
The skill declares no required environment variables or external credentials. The script uses HOME to compute DATA_DIR — appropriate and proportionate for a local CLI tool.
Persistence & Privilege
The skill is not force-included (always:false) and uses normal autonomous invocation defaults. It creates/writes files under the user's home directory (~/.local/share/laundry), which is expected for a local CLI but is persistent on disk — consider that user data will be stored locally and may persist across runs.
Assessment
This appears to be a straightforward offline CLI that stores logs in ~/.local/share/laundry and exports files there. Before installing: (1) Review the complete scripts/script.sh (the provided file in the prompt was truncated) to ensure there are no hidden network calls or unexpected file reads/writes; (2) be aware the tool will create and append to files in your home directory — back up or sandbox if you prefer; (3) avoid running it with untrusted inputs if you pipe arbitrary data into the tool (some grep/printf/echo usage may behave unexpectedly for specially crafted input); (4) if you need higher assurance, run the script in a container or chroot first to confirm behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk97cy0aabn2bya0y374wzbc7as834s9v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.