传感器
Sensor
by BytesAgain
Read and manage IoT sensor data from the terminal. Use when polling readings, checking device connectivity, converting units, analyzing telemetry trends.
安装
claude skill add --url github.com/openclaw/skills/tree/main/skills/ckchzh/sensor文档
Sensor
A terminal-first utility toolkit for managing sensor data. Log readings, check device status, analyze telemetry, generate reports, and export data — all with timestamped logging and full export support.
Why Sensor?
- Works entirely offline — your data never leaves your machine
- Simple command-line interface, no GUI needed
- Export to JSON, CSV, or plain text anytime
- Automatic history and activity logging
- Each command maintains its own dedicated log file
Commands
| Command | Description |
|---|---|
sensor run <input> | Run a sensor task (or view recent runs with no args) |
sensor check <input> | Check sensor readings or device connectivity |
sensor convert <input> | Convert between units or data formats |
sensor analyze <input> | Analyze telemetry trends and patterns |
sensor generate <input> | Generate sensor configurations or test data |
sensor preview <input> | Preview a sensor operation before executing |
sensor batch <input> | Batch-process multiple sensor readings |
sensor compare <input> | Compare sensor readings across devices or time periods |
sensor export <input> | Log an export operation (or view recent exports) |
sensor config <input> | Store or review sensor configuration settings |
sensor status <input> | Log a device status update (or view recent status entries) |
sensor report <input> | Generate or log a sensor data report |
sensor stats | Show summary statistics across all categories |
sensor export <fmt> | Export all data (formats: json, csv, txt) |
sensor search <term> | Search across all logged entries |
sensor recent | Show the 20 most recent activity log entries |
sensor status | Health check — version, data dir, entry count, disk usage |
sensor help | Show full usage information |
sensor version | Show version (v2.0.0) |
Each action command works in two modes:
- With arguments: saves the input with a timestamp to
<command>.logand logs to history - Without arguments: displays the 20 most recent entries for that command
Data Storage
All data is stored locally in ~/.local/share/sensor/. Each command writes to its own dedicated log file (e.g., run.log, check.log, analyze.log). A unified history.log tracks all activity with timestamps. Data never leaves your machine.
Directory structure:
~/.local/share/sensor/
├── run.log
├── check.log
├── convert.log
├── analyze.log
├── generate.log
├── preview.log
├── batch.log
├── compare.log
├── export.log
├── config.log
├── status.log
├── report.log
└── history.log
Requirements
- Bash (with
set -euo pipefail) - Standard Unix utilities:
date,wc,du,tail,grep,sed,cat - No external dependencies or network access required
When to Use
- Logging IoT sensor readings from the field — use
runandcheckto record temperature, humidity, pressure, or other sensor readings with automatic timestamps - Analyzing telemetry trends across devices — use
analyzeandcompareto identify patterns in sensor data and spot anomalies between devices or time periods - Converting sensor data between units — use
convertto log unit conversions (Celsius to Fahrenheit, PSI to bar, etc.) and keep a record of transformations - Generating periodic sensor reports — use
report,stats, andexportto compile sensor data into JSON, CSV, or text formats for dashboards or stakeholder reviews - Batch-processing multi-device sensor data — use
batchandconfigto handle bulk sensor operations and maintain device configuration records
Examples
# Log a temperature reading
sensor run "Sensor-A3: 23.5°C at warehouse zone B"
# Check device connectivity status
sensor check "Gateway-01: online, 12 sensors connected, latency 45ms"
# Analyze a telemetry trend
sensor analyze "Temperature drift: +0.3°C/hour over last 6 hours in cold storage"
# Export all sensor data as CSV for analysis
sensor export csv
# Search for all entries related to a specific sensor
sensor search "Sensor-A3"
Configuration
Set the SENSOR_DIR environment variable to change the data directory. Default: ~/.local/share/sensor/
Output
All commands output results to stdout. Redirect to a file with > output.txt if needed. The export command writes directly to ~/.local/share/sensor/export.<fmt>.
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
相关 Skills
PDF处理
by anthropics
遇到 PDF 读写、文本表格提取、合并拆分、旋转加水印、表单填写或加解密时直接用它,也能提取图片、生成新 PDF,并把扫描件通过 OCR 变成可搜索文档。
✎ PDF杂活别再来回切工具了,文本表格提取、合并拆分到OCR识别一次搞定,连扫描件也能变可搜索。
Word文档
by anthropics
覆盖Word/.docx文档的创建、读取、编辑与重排,适合生成报告、备忘录、信函和模板,也能处理目录、页眉页脚、页码、图片替换、查找替换、修订批注及内容提取整理。
✎ 搞定 .docx 的创建、改写与精排版,目录、批量替换、批注修订和图片更新都能自动化,做正式文档尤其省心。
PPT处理
by anthropics
处理 .pptx 全流程:创建演示文稿、提取和解析幻灯片内容、批量修改现有文件,支持模板套用、合并拆分、备注评论与版式调整。
✎ 涉及PPTX的创建、解析、修改到合并拆分都能一站搞定,连备注、模板和评论也能处理,做演示文稿特别省心。
相关 MCP 服务
文件系统
编辑精选by Anthropic
Filesystem 是 MCP 官方参考服务器,让 LLM 安全读写本地文件系统。
✎ 这个服务器解决了让 Claude 直接操作本地文件的痛点,比如自动整理文档或生成代码文件。适合需要自动化文件处理的开发者,但注意它只是参考实现,生产环境需自行加固安全。
by wonderwhy-er
Desktop Commander 是让 AI 直接执行终端命令、管理文件和进程的 MCP 服务器。
✎ 这工具解决了 AI 无法直接操作本地环境的痛点,适合需要自动化脚本调试或文件批量处理的开发者。它能让你用自然语言指挥终端,但权限控制需谨慎,毕竟让 AI 执行 rm -rf 可不是闹着玩的。
EdgarTools
编辑精选by dgunning
EdgarTools 是无需 API 密钥即可解析 SEC EDGAR 财报的开源 Python 库。
✎ 这个工具解决了金融数据获取的痛点——直接让 AI 读取结构化财报,比如让 Claude 分析苹果的 10-K 文件。适合量化分析师或金融开发者快速构建数据管道。但注意,它依赖 SEC 网站稳定性,高峰期可能延迟。