Individual skill

exploratory-data-analysis

Analyze scientific data files across 200+ formats at the depth the user requests. Detect file type, assess structure, quality, and statistics, and create reports or visualizations only when they are requested or materially needed. Covers chemistry, bioinformatics, microscopy, spectroscopy, proteomics, metabolomics, and general scientific data formats.

backend/cli/skills/coding/exploratory-data-analysis/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,353
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Exploratory Data Analysis

## Overview

Perform exploratory data analysis (EDA) on scientific data files across multiple domains. Match the depth and output to the request: a narrow calculation should stay a narrow calculation, while a requested full audit can include broader quality assessment and documentation.

## Scope and output contract

- The user's requested scope and output format take precedence over this workflow.
- Do not create a report, figure, artifact, directory, or sidecar file by default.
- Do not write to disk unless the user requested a saved deliverable or the task inherently requires one.
- For a bounded question, inspect only the necessary data and answer inline with the decisive calculation and caveats.
- Recommend a visualization only when it materially clarifies the result; generate one only when requested or necessary for the requested deliverable.