exploratory-data-analysis

Profiles new datasets through grain, null, distribution, and relationship checks before analysis.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Nandansai08/skillz --skill exploratory-data-analysis-nandansai08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploratory-data-analysis
Source: https://github.com/Nandansai08/skillz/tree/main/skills/data-analytics/exploratory-data-analysis
Command: npx skills add https://github.com/Nandansai08/skillz --skill exploratory-data-analysis-nandansai08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analysts routinely build reports and models on datasets they have never verified, so grain bugs, sentinel values, and missing time ranges silently corrupt every downstream number. This Skill enforces a structured first pass over any new dataset so defects are caught in exploration rather than in the executive review. ## Core Features & Use Cases - Grain Verification: Confirms what one row actually represents using uniqueness checks before any aggregation, catching versioned rows and join fan-out. - Systematic Profiling: Covers column types, null rates, disguised sentinel values, distributions, time coverage, cross-column invariants, and outlier characterization. - Written Deliverables: Produces a one-page findings note plus a cleaning worklist for downstream pipelines instead of an unstructured notebook of plots. - Use Case: Given a subscriptions table for churn analysis, the workflow reveals the grain is status-changes rather than subscriptions, finds a two-week pipeline outage, and flags internal test accounts — before the churn rate is ever computed. ## Quick Start Ask the agent to run exploratory data analysis on your dataset, for example: "Profile this subscriptions table and tell me what one row represents, what's missing, and what looks suspicious."

Frequently Asked Questions about exploratory-data-analysis

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

FAQPage Schema
How do I do exploratory data analysis on a new dataset?▼

Start by verifying the grain with a uniqueness check on the supposed key, then profile columns with info, describe, and value_counts. Plot distributions and time coverage, test domain invariants, and finish with a written findings note and cleaning worklist.

How do I check if a column is a unique key in pandas?▼

Use df['column'].is_unique to test whether a column can serve as the table's key. If it returns False, inspect duplicates with df[df.duplicated('column', keep=False)] to discover whether the grain is finer than expected.

Why does my data have nulls that pandas does not show?▼

Sentinel values like -999, empty strings, "N/A", and placeholder dates such as 1900-01-01 appear as real data, not nulls. Run value_counts(dropna=False) on categorical and numeric columns to expose these disguised missing values.

Should I remove outliers during exploratory data analysis?▼

No — locate and characterize outliers first, because some are data errors, some are unit mixups or test accounts, and some are genuinely important records. The classification decision is an EDA deliverable; deletion belongs to the later cleaning step.

When should I not use exploratory data analysis?▼

Skip it when executing known fixes on already-profiled data — that work belongs to a data-cleaning pipeline that consumes the EDA worklist. EDA is for first contact with a dataset or re-validation after a pipeline change.