🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Process Viewer
πŸ¦€ ClawHub✦ BytesAgain

Process Viewer

by @ckchzh

A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and det process-viewer, c, administrator, benchmarking.

Versionv2.0.0
Downloads361
Installs1
#legal
TERMINAL
clawhub install process-viewer

πŸ“– About This Skill

version: "2.0.0" name: Systeminformer description: "A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and det process-viewer, c, administrator, benchmarking."

Process Viewer

A sysops toolkit for scanning, monitoring, and managing system processes. Record observations, track alerts, run benchmarks, and generate reports β€” all from the command line with persistent local storage.

Quick Start

bash scripts/script.sh  [args...]

Commands

Core Operations

  • scan β€” Record a process scan entry (without args: show recent scans)
  • monitor β€” Log a monitoring observation (without args: show recent entries)
  • report β€” Create a report entry (without args: show recent reports)
  • alert β€” Log an alert or warning (without args: show recent alerts)
  • top β€” Record top-process data (without args: show recent entries)
  • usage β€” Track resource usage (without args: show recent entries)
  • check β€” Run or log a health check (without args: show recent checks)
  • fix β€” Document a fix applied (without args: show recent fixes)

    • Maintenance

  • cleanup β€” Record a cleanup action (without args: show recent cleanups)
  • backup β€” Log a backup operation (without args: show recent backups)
  • restore β€” Log a restore operation (without args: show recent restores)
  • log β€” Add a general log entry (without args: show recent logs)

    • Analysis

  • benchmark β€” Record benchmark results (without args: show recent benchmarks)
  • compare β€” Log comparison data (without args: show recent comparisons)

    • Utilities

  • stats β€” Show summary statistics across all entry types
  • export β€” Export all data (formats: json, csv, txt)
  • search β€” Search across all log files for a keyword
  • recent β€” Show the 20 most recent activity log entries
  • status β€” Display health check: version, data dir, entry count, disk usage
  • help β€” Show available commands
  • version β€” Print version (v2.0.0)

    • Each command accepts free-text input. When called without arguments, it displays the most recent 20 entries for that category.

    Data Storage

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

    ~/.local/share/process-viewer/
β”œβ”€β”€ scan.log          # Process scan entries
β”œβ”€β”€ monitor.log       # Monitoring observations
β”œβ”€β”€ report.log        # Reports
β”œβ”€β”€ alert.log         # Alerts and warnings
β”œβ”€β”€ top.log           # Top-process snapshots
β”œβ”€β”€ usage.log         # Resource usage records
β”œβ”€β”€ check.log         # Health check records
β”œβ”€β”€ fix.log           # Applied fixes
β”œβ”€β”€ cleanup.log       # Cleanup actions
β”œβ”€β”€ backup.log        # Backup operations
β”œβ”€β”€ restore.log       # Restore operations
β”œβ”€β”€ log.log           # General log entries
β”œβ”€β”€ benchmark.log     # Benchmark results
β”œβ”€β”€ compare.log       # Comparison data
└── history.log       # Unified activity history

    Each entry is stored as YYYY-MM-DD HH:MM| β€” one line per record. The history.log file tracks all commands chronologically.

    Requirements

  • Bash 4.0+ with set -euo pipefail
  • Standard Unix utilities: date, wc, du, tail, grep, sed, cat, basename
  • No external dependencies, no network access required
  • Write access to ~/.local/share/process-viewer/

    • When to Use

    1. Tracking system processes over time β€” Use scan and monitor to build a log of process observations for later review or trend analysis 2. Incident response documentation β€” Use alert to log warnings, fix to document remediation steps, and report to create post-incident summaries 3. Performance benchmarking β€” Use benchmark and compare to record and contrast performance measurements across different configurations or time periods 4. Backup and recovery auditing β€” Use backup and restore to maintain an audit trail of data protection operations 5. Periodic system health reviews β€” Use status for a quick health check, stats for an overview, and export json to archive data for external analysis

    Examples

    # Scan and record a process observation
process-viewer scan "nginx worker count: 4, memory 128MB"
    Log a monitoring alert
    
process-viewer alert "CPU usage exceeded 90% on web-server-03"
    Document a fix
    
process-viewer fix "Restarted memcached after OOM kill"
    Run a benchmark and record it
    
process-viewer benchmark "Disk I/O test: 450MB/s sequential read"
    View summary statistics across all categories
    
process-viewer stats
    Export everything to JSON for external processing
    
process-viewer export json
    Search all logs for a specific term
    
process-viewer search "nginx"
    Check system status
    
process-viewer status

    Configuration

    Set PROCESS_VIEWER_DIR environment variable to override the default data directory. Default: ~/.local/share/process-viewer/

    Output

    All commands output to stdout. Redirect to a file with process-viewer > output.txt. Export formats (json, csv, txt) write to the data directory and report the output path and file size.

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

    ⚑ When to Use

    TriggerAction
    2. **Incident response documentation** β€” Use `alert` to log warnings, `fix` to document remediation steps, and `report` to create post-incident summaries
    3. **Performance benchmarking** β€” Use `benchmark` and `compare` to record and contrast performance measurements across different configurations or time periods
    4. **Backup and recovery auditing** β€” Use `backup` and `restore` to maintain an audit trail of data protection operations
    5. **Periodic system health reviews** β€” Use `status` for a quick health check, `stats` for an overview, and `export json` to archive data for external analysis

    πŸ’‘ Examples

    # Scan and record a process observation
process-viewer scan "nginx worker count: 4, memory 128MB"
    Log a monitoring alert
    
process-viewer alert "CPU usage exceeded 90% on web-server-03"
    Document a fix
    
process-viewer fix "Restarted memcached after OOM kill"
    Run a benchmark and record it
    
process-viewer benchmark "Disk I/O test: 450MB/s sequential read"
    View summary statistics across all categories
    
process-viewer stats
    Export everything to JSON for external processing
    
process-viewer export json
    Search all logs for a specific term
    
process-viewer search "nginx"
    Check system status
    
process-viewer status

    βš™οΈ Configuration

    Set PROCESS_VIEWER_DIR environment variable to override the default data directory. Default: ~/.local/share/process-viewer/