Equipment Maintenance Log
v0.1.0Track lab equipment calibration dates and send maintenance reminders
⭐ 0· 89·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the code: the script stores equipment records and checks upcoming/overdue maintenance. Minor mismatch: the registry metadata lists no required binaries, but SKILL.md usage and scripts/main.py expect Python to be available (python3).
Instruction Scope
SKILL.md instructs running the included Python script and describes local behavior only. The runtime code reads/writes a file in the user's home directory (~/.openclaw/equipment_log.json); the registry declared no config paths, so the skill will create and persist data in the user's home without that being called out in metadata.
Install Mechanism
No install spec (instruction-only plus an included Python script). This is low-risk from an install perspective — nothing is downloaded at runtime — but the bundled script will be executed locally by the agent and writes files to disk.
Credentials
The skill requests no environment variables or credentials; the operations performed (local read/write of a JSON file) are proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill does not request elevated privileges or modify other skills. It does persist data under ~/.openclaw, which is reasonable for a local tool but is persistent storage in the user's home directory and should be considered by the user.
Assessment
This skill appears to be a simple local Python tool for tracking calibration dates and reminders. Before installing: ensure you have Python available (python3), inspect and trust the included scripts, and be aware the script will create and write ~/.openclaw/equipment_log.json in your home directory (persistent local storage). There are minor metadata mismatches (the registry didn't declare Python or the config path); if you need stricter isolation, run the script in a sandbox/virtualenv or container. Also validate inputs (date format) and back up any important data before use.Like a lobster shell, security has layers — review code before you run it.
latestvk976w1vmm2ve5a7sf3x1smrdnx838jy4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.