Cache
v2.0.0Manage a local key-value cache store using bash and Python. Use when caching API responses, session data, or computed results with TTL support.
⭐ 0· 153·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (local key-value cache with TTL) matches the provided script and SKILL.md: commands (set/get/list/flush/ttl/stats/import/export/search/config) and storage in ~/.cache-tool are coherent with the stated purpose.
Instruction Scope
Runtime instructions direct the agent to run bash scripts/script.sh and the script persistently writes/reads files under ~/.cache-tool (data.jsonl and config.json). This is expected for a cache tool, but users should note that data is stored on disk and 'get' prints raw values to stdout. The script exports ARGS into the environment for embedded Python parsers, which may affect how argument quoting/spaces are handled.
Install Mechanism
No install spec or external downloads; the skill is instruction-only with a bundled script. Nothing is fetched from remote URLs or installed system-wide.
Credentials
The skill declares no required environment variables or credentials and the script only uses internally-defined DATA_FILE/CONFIG_FILE derived from $HOME. No unrelated secrets or external service credentials are requested.
Persistence & Privilege
The skill is user-invocable and not 'always:true'. It creates and writes files under the user's home directory (~/.cache-tool). This is normal for a local cache but does mean persistent data will remain on disk until removed.
Assessment
This skill appears to do exactly what it says: a lightweight, local file-backed cache. Before installing, be aware that (1) it creates and maintains data/config files in ~/.cache-tool which will persist on disk; (2) 'get' prints raw stored values (so do not store secrets you don't want exposed); (3) the tool does not request or use external credentials or network access; and (4) the script uses simple file writes without locking, so concurrent access could result in races. If you need to store sensitive data, consider encrypting values or using a different secure store. If you want absolute assurance, review the full script (scripts/script.sh) for the remaining truncated sections before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97dmp03tj41avgebh9tfhn0nn835x8f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.