Mileage
v2.0.1Log vehicle mileage, review driving trends, and export trip reports for tracking. Use when logging trips, tracking fuel economy, exporting mileage data.
⭐ 0· 200·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
high confidencePurpose & Capability
The name and description (log mileage, review trends, export reports) match the delivered files and behavior. The script implements a local CLI that stores data in ~/.local/share/mileage and provides add/search/export/stats commands; there are no unrelated credentials, binaries, or cloud integrations requested.
Instruction Scope
SKILL.md and the included script keep all activity local and reference only the data directory. The script logs user inputs verbatim into .log files and history.log. Export and search operate only on those local files. One caveat: the JSON export routine does not escape values, so exported JSON may be invalid or contain unescaped quotes/control characters if you store arbitrary text.
Install Mechanism
No install spec is provided and no external downloads or packages are required. Only a shell script is included; nothing in the repo attempts to fetch or install remote code.
Credentials
The skill requires no environment variables, credentials, or config paths. It only uses $HOME to create its data directory, which is proportionate to a personal local logging tool.
Persistence & Privilege
The skill persistently writes files under ~/.local/share/mileage (log files and history). This is expected for a logging tool and it does not request elevated privileges or system-wide configuration changes. always:false and no global modifications are present.
Assessment
This skill appears to do what it says: a local mileage logger that writes data to ~/.local/share/mileage and does not contact external services or ask for credentials. Before installing, consider: (1) review the included scripts (they will run locally) and keep backups if you rely on the data; (2) data is stored unencrypted — don't log sensitive personal information if others can access your account; (3) exported JSON may be invalid for inputs containing quotes/newlines because values are not escaped — sanitize before sharing; (4) if you want extra isolation, run the script in a sandbox/container or inspect/modify it to suit your security posture.Like a lobster shell, security has layers — review code before you run it.
latestvk976fpba71jxk5kwnr9ve1dqyh835h7p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.