Parser

Parser - command-line tool for everyday use

Security Scan

The skill's README promises a general-purpose parser and an environment variable for configuring storage, but the included script mostly just records inputs into log files under ~/.local/share/parser and ignores the declared PARSER_DIR — the behavior and claims are inconsistent.

Purpose & Capability

SKILL.md and metadata claim a broad text/data parser (JSON, CSV, XML, logs, custom formats) and describe commands like convert/export; the bundled script, however, primarily appends user inputs to per-command .log files, lists/searches those logs, and performs simple exports. There is little or no real parsing logic for structured formats and several features described (e.g., honoring PARSER_DIR) are not implemented. This is a mismatch between claimed capability and actual code.

Instruction Scope

Runtime instructions are simple CLI usage docs. The script only reads/writes files inside a data directory under the user's HOME (~/.local/share/parser) and uses standard utilities (grep, tail, wc, du). It does not contact external endpoints or request secrets. However SKILL.md suggests configuring PARSER_DIR while the script ignores that env var, which is an inconsistency to be aware of.

Install Mechanism

No install spec; the skill is instruction-only with a single shell script. Nothing is downloaded from external URLs and no package managers are invoked, so install risk is low. The shipped script will be placed on disk if the platform installs skill files—this is expected behavior.

Credentials

The skill declares no required credentials or env vars, which matches the script, but SKILL.md advertises a PARSER_DIR env var for configuration while the script unconditionally uses $HOME/.local/share/parser and does not read PARSER_DIR. This discrepancy is a design inconsistency (not secret-exfiltration), and users expecting to relocate the data directory via PARSER_DIR will be surprised.

Persistence & Privilege

The script creates and writes many persistent files under the user's home directory (~/.local/share/parser) including history.log and per-command logs. It does not change system-wide settings or other skills' configurations and does not require elevated privileges, but it will persist potentially sensitive input data locally.

What to consider before installing

This skill is inconsistent: its description promises a full parser and an environment-configurable data directory, but the shipped script mostly just logs inputs to ~/.local/share/parser and provides simple export/search features. There are no network calls or requested credentials, but the script will create persistent files in your home directory and could store anything you pass to it. Before installing or using it: (1) review the full script (the manifest was truncated in the listing) to ensure no hidden behavior; (2) if you expect PARSER_DIR support or real CSV/JSON/XML parsing, test those features (they appear unimplemented); (3) run it in a sandbox or with a disposable account to see what it writes; and (4) if you plan to store sensitive data, avoid using this tool until you confirm how and where data is written and rotated.

Text and data parser — parse JSON, CSV, XML, logs, and custom formats into structured output.

Commands

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

Usage

parser help
parser run
parser status

Examples

# Get started
parser help

# Run default task
parser run

# Export as JSON
parser export json

Output

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

Configuration

Set PARSER_DIR to change data directory. Default: ~/.local/share/parser/

---

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