data-master skill

Skill and CLI for tables: cleaning with recorded decisions, level-based statistics, a PDF report and a separate audit.

  • 101 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The tool runs Python scripts, downloads dependencies with setup and writes result files to disk.
All reasons and checks

maga2010/data-master

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/data-master

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The tool runs Python scripts, downloads dependencies with setup and writes result files to disk.

This is third-party code. Review the repository files before installing.

What it does

data-master keeps the raw file untouched, records every cleaning decision and runs statistics only at the level the data supports. It then tests the sensitivity of conclusions and delivers a report in Markdown, HTML and PDF with machine-readable evidence. It is a Codex skill and also a standalone cross-platform CLI. Full inference covers one tabular export: CSV, TSV, Excel, JSON, Parquet and single-table SQLite. Timestamped data gets descriptive analysis without forecasting, while text, images, audio and geospatial data get an integrity profile. A separate audit can refuse to declare a report ready even when it looks complete.

Who it is for. Researchers and analysts who need a reproducible data report with evidence for every cleaning and calculation step.

Good fit when

  • An export with codes like 02134 may lose leading zeros on load.
  • Repeated measurements of one subject cannot be counted as independent observations.
  • A report for a paper or management is needed along with the cleaning decision log.
  • An interrupted analysis should resume without recomputing confirmed stages.

Not a fit when

  • You need a time-series forecast, since that mode is descriptive only.
  • Data sits in several linked tables while full inference covers one.
  • Python 3.11 or Node.js 20 cannot be installed in your environment.

Example request

Analyze measurements.csv: group in the treatment column, subject key participant_id, outcomes response_time and accuracy. Build the PDF report and show the audit verdict.

Limitations

You need Node.js 20 or newer and Python 3.11 or newer. The `data-master setup` command downloads Python dependencies into an isolated environment, and it is the only step that downloads anything. Full statistical inference works for one table, time-series analysis is descriptive and nothing is forecast. Pickle and related files are refused because loading them can execute code. Comparisons are labeled exploratory until you declare `--unit-key`, `--group` and `--outcomes` explicitly. The audit does not replace statistical judgment or a study protocol.

How to disable. Remove the installed skill from the agent skills directory and the package with `npm uninstall -g data-master`. The outputs folders with results stay with you.

FAQ

How do I analyze my own table?

`data-master analyze measurements.csv --out outputs/study` creates the report and audit. For a confirmatory analysis add `--group`, `--unit-key` and `--outcomes`.

What if the run stops on a question?

When a decision cannot be inferred safely, the run writes answers.template.json. Fill in the decision IDs and run `data-master resume outputs/study/state.json --answers outputs/study/answers.json`.

How do I verify a delivered run?

`data-master verify outputs/first-demo --json` checks saved artifact hashes and changes nothing.

Does the tool modify my source data?

No. The raw file is preserved as is, and the cleaned copy goes into the cleaned folder with a replayable cleaning script.

Do my data leave the machine?

No, unknown binary formats are profiled locally: bytes, headers and records are never sent to web search. Only `data-master setup` uses the network to download dependencies.

Discussion

No questions or reviews yet.

Skills

High-Stakes Analytics Lab

High-Stakes Analytics & Decision Lab

An evidence-gated analytics skill for high-stakes decisions: profiles data, picks a method the evidence supports, can answer with a data request

SkillExtended access1KRepository stars

31 skills for Claude Code and Codex for the analyst workflow: data checks, cohorts, funnels, A/B tests, dashboards, summaries

SkillMinimal access529Repository stars

A data visualization skill for agents: turns data into polished interactive HTML charts and full reports with one visual language

SkillMinimal access6.8KRepository stars

Excel analysis skill that profiles a sheet, cleans it, reconciles totals against the sheet's own sums and then releases numbers.

SkillMinimal access464Repository stars

A template for data scientists: AGENTS.md, CLAUDE.md and skills for Python, SQL, Polars and model diagnostics.

SkillMinimal access115Repository stars

VisiData opens multiple table formats in a terminal and helps explore, arrange and compare data through keyboard controls.

CLIExtended access9.5KRepository stars

README in short

The tool delivers a bundle of evidence: profile, cleaned data, a replayable cleaning script, charts, three report formats and an audit. State is stored in state.json, so an interrupted run resumes with stage hashes.

README badge

Original SKILL.md

---
name: data-master
description: "Analyze datasets with preserved raw inputs, explicit cleaning decisions, reproducible figures and PDF reports. Full statistics for one tabular file; descriptive time-series analysis; integrity profiling for text, image, audio, geographic and mixed inputs. Use for data cleaning, EDA, group comparisons, statistical reports, 跑数据 or 数据分析 with a traceable evidence trail."
allowed-tools: Bash(python *), Bash(py *), PowerShell(python *), PowerShell(py *), Bash(data-master *), PowerShell(data-master *), WebSearch, WebFetch
---

# data-master — universal data processing pipeline

Turn **any data** into a **cleaned, audited, Nature-grade report + charts** with one command. The agent reads the data, decides modality, picks methods, runs the pipeline, and writes evidence-backed outputs. The user never has to choose a statistical test or a chart type.

## Contract

Installed CLI: `data-master analyze <file> --out <dir>`; use
`data-master doctor --json` to diagnose the environment and
`data-master verify <dir> --json` to check saved artifact hashes.
`data-master demo --out <new-dir>` runs a synthetic example, and
`data-master skill install` installs this skill atomically from the npm or
Python distribution. Existing
`python scripts/run_pipeline.py` commands below remain supported; installing
the CLI alone does not register the skill until `skill install` is run.

- **Input**: `$ARGUMENTS` = a file, a folder, or a glob. Optional flags:
  - `--report nature` (default) | `standard` | `executive` — report template.
  - `--out <dir>` — overrides the output root.
  - `--answers <file>` — answers `answers.template.json` decisions by id; every id and action is validated, and changing the file invalidates the stale cleaning stages on resume. The file may also carry a `run` block declaring `unit_key` / `group` / `outcomes` / `design` / `journal` / `covariates` (validated against the profile; explicit CLI values always win). A decision may name a single `column` of a multi-column flag.
  - `--covariates <a,b>` — declare numeric covariates; the adjusted (ANCOVA) comparison becomes primary, unadjusted stays as cross-check, and the homogeneity-of-slopes assumption is tested and reported.
  - `--unit-key <column>`, `--group <column>`, and `--outcomes <a,b>` — all three must be explicitly declared before the analysis is labelled confirmatory. Automatic group/outcome selection is exploratory.
  - `--max-input-mb <n>` — override the 300 MB in-memory input gate (readers hold files whole, as text).
  - `--export-lockfile` — writes `lockfile.txt` with the exact dependency versions that ran.
- **Output** (all under `<dataset_dir>\outputs\`):
  - `cleaned/` — cleaned data + `cleaning_plan.json` + `cleaning_report.md` + reproducible `clean_*.py`
  - `analysis/` — `profile.json`, `stats.json`, `validation_report.md`, `chart_decisions.json`, `sensitivity.json`
  - `charts/` — `*.png` figures
  - `report.md` — main report (the citable source text)
  - `report.html` — self-contained shareable export of report.md (figures embedded; verification hashes it)
  - `report.pdf` — **primary deliverable**; rendered by a three-tier cascade
  - `executive_summary.md` — 1-page TL;DR
  - `report_build.json` — provenance for every number + PDF backend trail + self-audit + pipeline commit
  - `audit/final_audit.md` — 8-gate + journal-checklist verdict
  - `charts_rendered.json` — per-figure ink ratio and blank-page check
  - `answers.template.json` — the never-automatic decisions this dataset raised, fillable and fed back with `--answers`
  - `lockfile.txt` — (with `--export-lockfile`) exact dependency versions that ran
- **Invariant — additive only**: NEVER modify, move, or delete any raw input file. Re-runs may overwrite `outputs/`.
- **Full-auto with gates**: never block on a method choice; always pick the most defensible default and document. ONLY ask the user when the input itself is ambiguous.
- **Method provenance**: every AI judgment records `rule_source` + `alternative_considered` + `rejected_reason`. Every number cites the script that produced it.

Report a problem