Process

Process - command-line tool for everyday use

Security Scan

The skill's code and instructions are coherent with a local command-line 'process' utility that stores data under the user's home directory; there are no external network calls or credential requests, but it logs arbitrary inputs so avoid sending secrets to it.

Purpose & Capability

Name/description match the shipped script: a local process/ops utility that lists, logs, monitors, and exports entries. The skill does not request unrelated credentials, binaries, or system access beyond the user's home directory.

Instruction Scope

Runtime script writes and reads log files under $HOME/.local/share/process and implements many local commands (scan, monitor, export, status, etc.). It does not call external endpoints or read unrelated system config. Caution: commands append arbitrary user-provided input to log files ("$ts|$input"), so sensitive input (passwords, tokens) passed as arguments will be recorded locally.

Install Mechanism

There is no install spec and no network downloads; the skill is instruction-only with an included shell script. Nothing will be fetched from external URLs during installation. The contained script will operate on the local filesystem if run.

Credentials

The skill declares no required environment variables or credentials and uses only HOME to construct a per-user data directory. Minor inconsistency: SKILL.md claims PROCESS_DIR can be set to change the data directory, but the script hard-codes DATA_DIR='${HOME}/.local/share/process' and does not read PROCESS_DIR.

Persistence & Privilege

always is false and the skill is user-invocable; it only creates and modifies files inside its own data directory under the user's home. It does not modify system-wide agent settings or other skills.

Assessment

This skill appears to do what it says — a local CLI that stores logs under ~/.local/share/process and can export them. Before installing or running: (1) review the script yourself (it will write logs in your home directory); (2) avoid passing secrets or credentials as command arguments because they will be saved to logs; (3) if you want a custom data location, note that SKILL.md mentions PROCESS_DIR but the script ignores it — modify the script or move the data directory as needed; (4) run it in a contained environment if you prefer (or inspect permissions on the data dir). If you need networked backups or integrations, verify any external endpoints separately — the shipped code currently makes no network calls.

Process manager — list, filter, kill, monitor, and log system processes.

Commands

Command	Description
process help	Show usage info
process run	Run main task
process status	Check state
process list	List items
process add <item>	Add item
process export <fmt>	Export data

Usage

process help
process run
process status

Examples

process help
process run
process export json

Output

Results go to stdout. Save with process run > output.txt.

Configuration

Set PROCESS_DIR to change data directory. Default: ~/.local/share/process/

---

Powered by BytesAgain | bytesagain.com Feedback & Feature Requests: https://bytesagain.com/feedback

Features

• Simple command-line interface for quick access
• Local data storage with JSON/CSV export
• History tracking and activity logs
• Search across all entries
• Status monitoring and health checks
• No external dependencies required

Quick Start

# Check status
process status

# View help and available commands
process help

# View statistics
process stats

# Export your data
process export json

How It Works

Process stores all data locally in ~/.local/share/process/. Each command logs activity with timestamps for full traceability. Use stats to see a summary, or export to back up your data in JSON, CSV, or plain text format.

Support

• Feedback: https://bytesagain.com/feedback/
• Website: https://bytesagain.com
• Email: [e-mail]

Powered by BytesAgain | bytesagain.com