exploratory-data-analysis

Inspect scientific data files with bounded, redacted local EDA reports.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/CliffVale/opencode-free-setup --skill exploratory-data-analysis-cliffvale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploratory-data-analysis
Source: https://github.com/CliffVale/opencode-free-setup/tree/main/skills/exploratory-data-analysis
Command: npx skills add https://github.com/CliffVale/opencode-free-setup --skill exploratory-data-analysis-cliffvale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, h5py, biopython, pillow, tifffile, pandas, polars, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Exploring scientific datasets before modeling often means ad-hoc scripts that leak identifiers, silently truncate data, or make unsupported claims. This Skill performs bounded, local-only exploratory analysis of authorized files with strict safety rules, producing aggregate reports without exposing raw values or making causal claims. ## Core Features & Use Cases - Bounded format inspection: Profile CSV/TSV/JSON with the standard library, and optionally inspect NumPy NPY/NPZ, HDF5 metadata, FASTA/FASTQ sequences, and PNG/JPEG/TIFF image metadata with pinned dependencies. - Data quality audits: Run missingness, group/split leakage, duplicate-row, outlier, and transformation-sensitivity analyses without modifying or imputing the raw data. - Rigorous report scaffolds: Generate Markdown EDA reports with tokenized identifiers, documented limitations, and reproducible commands. - Use Case: A researcher receives a redacted CSV of experimental measurements and needs to check missingness patterns, train/test split leakage by subject, and outlier sensitivity before any modeling—without exposing subject identifiers or altering the raw file. ## Quick Start Use the exploratory-data-analysis skill to profile the file data.csv inside the approved project root and produce a bounded EDA report.

Frequently Asked Questions about exploratory-data-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run exploratory data analysis on a CSV file locally?▼

Run the bundled eda_analyzer.py script with the file path, an approved --root directory, and an optional --max-rows limit. It emits a bounded strict JSON report with schema, missingness, and distribution aggregates without printing raw row values.

What file formats does this EDA skill support?▼

CSV, TSV, and strict JSON are automated core formats using only the Python standard library. NumPy NPY/NPZ, HDF5, FASTA/FASTQ, PNG, JPEG, and TIFF/OME-TIFF are automated with optional pinned packages; all other domain formats are reference-only or fail closed.

How do I check for data leakage between train and test splits?▼

Use missingness_leakage_audit.py with --split-column plus optional --entity-column, --group-column, and --time-column. It flags entities or groups appearing in multiple splits, duplicate rows across splits, and overlapping time intervals as diagnostics, not proof of leakage.

Does the HDF5 inspection read dataset values?▼

No. The HDF5 inspector reports only bounded hierarchy and dataset metadata such as shape, dtype, chunking, and compression. It never reads dataset values, attribute values, soft or external links, or external storage, and it is not semantic validation of H5AD or Loom files.

Why does the skill reject my file or format?▼

Inputs must be regular files inside an explicit root, under the size cap, with no symlinks, URLs, or traversal. Unknown extensions fail closed by design, and formats like Parquet, DICOM, or mzML require separately validated domain tooling described in the references.

Can this skill impute missing values or remove outliers?▼

No. The tools never delete outliers, impute, normalize, or overwrite raw data. IQR fences, MAD, trimmed means, and log diagnostics are sensitivity summaries only; any transformation must be fitted on training data separately.