Agent Skills: Exploratory data analysis

Perform comprehensive exploratory data analysis on research data. Automatically analyze data structure, quality, distributions, and generate insights. Use when the user provides a dataset, asks to "explore data", "analyze this file", or needs to understand their data before formal analysis.

UncategorizedID: braselog/researchassistant/exploratory-data-analysis

Install this agent skill to your local

pnpm dlx add-skill https://github.com/braselog/researchAssistant/tree/HEAD/.github/skills/exploratory-data-analysis

Skill Files

Browse the full folder contents for exploratory-data-analysis.

Download Skill

Loading file tree…

.github/skills/exploratory-data-analysis/SKILL.md

Skill Metadata

Name
exploratory-data-analysis
Description
Performs project-aware exploratory analysis that checks data structure, quality, provenance, distributions, dependence, and potential leakage before formal modelling. Use for /exploratory_data_analysis or when a dataset needs inspection.

Exploratory data analysis

Start from the research question, data dictionary, provenance, experimental unit, sampling design, and downstream use. Never apply a generic plotting checklist without first understanding the data.

Workflow

  1. Load data without modifying source files and record the exact input path or version.
  2. Verify dimensions, types, identifiers, units, sample alignment, duplicates, and expected cardinalities.
  3. Examine missingness, censoring, impossible values, batch structure, and exclusions in context.
  4. Summarize distributions and relationships at the correct independent-unit level.
  5. Check repeated measures, clustering, technical replication, leakage, and confounding before group comparisons.
  6. Investigate unusual observations without automatically deleting them.
  7. Create only informative, reproducible figures and tables.
  8. Save analysis code and derived outputs through the project workflow when requested.

Report verified observations separately from interpretations and recommended follow-up. Do not select inferential tests solely from normality tests or treat visual patterns as confirmed effects.