S
SkillNav

Omni Tools

by ckchzh

Self-hosted collection of powerful web-based tools for everyday tasks. No ads, no tracking, just fas omni tools, typescript, alternative, converter.

View Chinese version with editor review

安装

claude skill add --url github.com/openclaw/skills/tree/main/skills/ckchzh/omni-tools

文档

Omni Tools

Self-hosted terminal toolkit providing a collection of powerful utility commands for everyday tasks. Omni Tools offers 12 core action commands plus built-in statistics, data export, search, and health-check capabilities — all backed by local log-based storage. No ads, no tracking, just fast accessible utilities.

Commands

All commands follow the pattern: omni-tools <command> [input]

When called without arguments, each command displays its most recent 20 log entries. When called with arguments, it records the input with a timestamp.

Core Action Commands

CommandDescription
run <input>Record and execute a run entry
check <input>Record a check / verification entry
convert <input>Record a conversion task
analyze <input>Record an analysis entry
generate <input>Record a generation task
preview <input>Record a preview action
batch <input>Record a batch processing task
compare <input>Record a comparison entry
export <input>Record an export operation
config <input>Record a configuration change
status <input>Record a status update
report <input>Record a report entry

Utility Commands

CommandDescription
statsShow summary statistics across all log files (entry counts, disk usage)
export <fmt>Export all data to a file — supported formats: json, csv, txt
search <term>Search across all log files for a keyword (case-insensitive)
recentShow the 20 most recent entries from the activity history
statusHealth check — version, data directory, total entries, disk usage, last activity
helpDisplay the full help message with all available commands
versionPrint the current version (omni-tools v2.0.0)

Data Storage

All data is stored locally in plain-text log files:

  • Location: ~/.local/share/omni-tools/
  • Format: Each entry is a line of YYYY-MM-DD HH:MM|<input> in the corresponding <command>.log file
  • History: Every action is also appended to history.log with a timestamp and command label
  • Export formats: JSON (array of objects), CSV (with headers), plain text (grouped by command)
  • No external dependencies — pure bash, runs anywhere

Requirements

  • Bash 4.0+ (uses set -euo pipefail)
  • Core utilities: date, wc, du, tail, grep, sed, cat, basename
  • No network access required — fully offline
  • No configuration needed — works out of the box

When to Use

  1. Quick task logging — capture run results, check outcomes, or conversion records from the terminal without opening a separate app
  2. Batch processing workflows — use omni-tools batch to log batch job details, then omni-tools stats to review totals
  3. Data analysis pipelines — record analysis steps with omni-tools analyze, then omni-tools export json for downstream processing
  4. Configuration auditing — track config changes with omni-tools config and search history with omni-tools search
  5. Cross-entry reporting — combine omni-tools report with omni-tools stats and omni-tools export csv to produce summary reports across all command categories

Examples

Record a run and view recent entries

bash
# Log a task
omni-tools run "deploy staging v2.3.1"

# View recent run entries
omni-tools run

Analyze, then export results

bash
# Record analysis entries
omni-tools analyze "CPU usage spike on node-3"
omni-tools analyze "Memory leak in worker pool"

# Export everything to JSON
omni-tools export json

Search and report

bash
# Search across all logs
omni-tools search "staging"

# Check overall statistics
omni-tools stats

# View recent activity
omni-tools recent

Batch processing workflow

bash
# Log batch operations
omni-tools batch "process images batch-042"
omni-tools batch "resize thumbnails batch-042"

# Review and export
omni-tools stats
omni-tools export csv

Health check and comparison

bash
# System health overview
omni-tools status

# Record comparisons
omni-tools compare "prod-v2 vs staging-v2.1 latency"

# View comparison history
omni-tools compare

Output

All commands output to stdout. Redirect to a file with:

bash
omni-tools stats > report.txt
omni-tools export json   # writes to ~/.local/share/omni-tools/export.json

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com