BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 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

View on ClawHub →

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.

⚡ When to Use

Trigger	Action
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/

Trigger	Action
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