Sensor

v2.0.0

Read and manage IoT sensor data from the terminal. Use when polling readings, checking device connectivity, converting units, analyzing telemetry trends.

0· 133·0 current·0 all-time
byBytesAgain2@ckchzh
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 ask for a local sensor CLI. The included script implements local logging, exports, searches, and status checks — all coherent with the stated purpose. No unrelated cloud credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md and the script operate only on local files (default ~/.local/share/sensor or overridden by SENSOR_DIR), standard Unix utilities, and stdout. Instructions don't request reading other system config or transmitting data externally. Note: the tool logs any input it is given (including arbitrary strings) into multiple .log files and history.log.
Install Mechanism
No install spec is provided (instruction-only). A single bash script is bundled; nothing is downloaded from the network or written to system locations outside the user's home directory. This is low-risk and proportional for the described CLI utility.
Credentials
The skill requires no environment variables or credentials. It optionally honors SENSOR_DIR to change its local data directory — this is reasonable and proportionate.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide agent settings, and is user-invocable only. It creates and writes only to its own data directory under the user's home.
Assessment
This skill appears to be a local CLI logger/analyzer and does not contact external services. Before installing or using it, note: (1) it will create and append logs under ~/.local/share/sensor (or SENSOR_DIR if set) and will record any text you pass to it — avoid entering secrets into commands you log; (2) exports aggregate all .log files from that directory, so any sensitive entries there could be exported locally; (3) while no network calls are present, you should still review the bundled script if you want to be certain it fits your privacy needs. If you prefer logs elsewhere, set SENSOR_DIR to a controlled location. Minor non-security issues: JSON export formatting has a small newline/formatting bug but this does not affect privacy.

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

latestvk97crcehsx64brqehc6sr1ef5s8357jq

License

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

Comments