Dataview

Explore CSV and JSON files with quick queries, filters, and aggregation. Use when inspecting data, running queries, filtering rows, aggregating.

Security Scan

The skill's code and instructions are internally consistent: it is a local-only CLI logger/viewer for CSV/JSON workflows that stores and searches logs under ~/.local/share/dataview and does not request credentials or network access — but verify the full script before installing because the provided file was truncated in the review input.

Purpose & Capability

The name/description (DataView: inspect/query/filter/aggregate CSV/JSON) matches the provided SKILL.md and script: commands create/read local logs and produce exports. Required tools (date, wc, du, grep, tail, cat, sed) are exactly the standard utilities the script uses.

Instruction Scope

SKILL.md instructs only on using local commands and the script implements those commands. The runtime behavior is limited to reading/writing files under the user's HOME data directory and searching those logs — it does not attempt to read system config, other users' data, or call external endpoints in the visible code.

Install Mechanism

There is no install spec (instruction-only), and the included script is a plain shell script. Nothing is downloaded from external URLs or extracted; no additional packages are installed by the skill itself.

Credentials

No environment variables or credentials are required. The script relies on HOME to determine the data directory (standard and proportional). There are no requests for unrelated secrets or service tokens.

Persistence & Privilege

always:false and user-invocable; the skill only creates and writes files in its own data directory (~/.local/share/dataview). It does not request elevated privileges or attempt to modify other skills or system-wide agent settings in the visible code.

Assessment

This skill appears coherent and local-only: it logs actions and stores/exports them under ~/.local/share/dataview and does not ask for credentials or perform network calls in the visible code. Before installing, consider: (1) inspect the complete script file on disk — the script content in the review input was truncated, so confirm the remainder contains no unexpected behavior; (2) avoid writing sensitive data (passwords, API keys, or PII) into dataview entries since they are stored and searchable in plain text and exported to files; (3) the JSON export code uses simple text assembly and may have formatting quirks — verify exported files before sharing. If you need higher assurance, run the script in a sandboxed account or review the full file contents locally prior to installation.

A data processing toolkit for ingesting, transforming, querying, and managing data entries from the command line. All operations are logged with timestamps and stored locally.

Commands

Data Operations

Each data command works in two modes: run without arguments to view recent entries, or pass input to record a new entry.

Command	Description
dataview ingest <input>	Ingest data — record a new ingest entry or view recent ones
dataview transform <input>	Transform data — record a transformation or view recent ones
dataview query <input>	Query data — record a query or view recent ones
dataview filter <input>	Filter data — record a filter operation or view recent ones
dataview aggregate <input>	Aggregate data — record an aggregation or view recent ones
dataview visualize <input>	Visualize data — record a visualization or view recent ones
dataview export <input>	Export data — record an export entry or view recent ones
dataview sample <input>	Sample data — record a sample or view recent ones
dataview schema <input>	Schema management — record a schema entry or view recent ones
dataview validate <input>	Validate data — record a validation or view recent ones
dataview pipeline <input>	Pipeline management — record a pipeline step or view recent ones
dataview profile <input>	Profile data — record a profile or view recent ones

Utility Commands

Command	Description
dataview stats	Show summary statistics — entry counts per category, total entries, disk usage
dataview export <fmt>	Export all data to a file (formats: json, csv, txt)
dataview search <term>	Search all log files for a term (case-insensitive)
dataview recent	Show last 20 entries from activity history
dataview status	Health check — version, data directory, entry count, disk usage, last activity
dataview help	Show available commands
dataview version	Show version (v2.0.0)

Data Storage

All data is stored locally at ~/.local/share/dataview/:

• Each data command writes to its own log file (e.g., ingest.log, transform.log)
• Entries are stored as timestamp|value pairs (pipe-delimited)
• All actions are tracked in history.log with timestamps
• Export generates files in the data directory (export.json, export.csv, or export.txt)

Requirements

• Bash (with set -euo pipefail)
• Standard Unix utilities: date, wc, du, grep, tail, cat, sed
• No external dependencies or API keys required

When to Use

• To log and track data processing operations (ingest, transform, query, etc.)
• To maintain a searchable history of data viewing and analysis activities
• To export accumulated records in JSON, CSV, or plain text format
• As part of larger automation or data inspection workflows
• When you need a lightweight, local-only data operation tracker

Examples

# Record a new ingest entry
dataview ingest "loaded sales_report.csv 2500 rows"

# View recent transform entries
dataview transform

# Record a query
dataview query "top 10 products by revenue"

# Filter data
dataview filter "region=APAC"

# Search across all logs
dataview search "sales"

# Export everything as CSV
dataview export csv

# Check overall statistics
dataview stats

# View recent activity
dataview recent

# Health check
dataview status

---

Powered by BytesAgain | bytesagain.com | [e-mail] 💬 Feedback & Feature Requests: https://bytesagain.com/feedback