Profile unfamiliar data
Inspect schemas, types, units, ranges, duplicates, category levels, date coverage, missingness, and suspicious values before choosing a method.
Codex Skills for Data Analysis give Codex a dependable process for inspecting datasets, cleaning values, testing assumptions, writing analysis code, creating useful charts, and explaining results. Download the skills to make exploratory and repeatable analysis easier across real projects.
task: explain customer churn
inspect:
- schema and grain
- missing values
- target leakage
verify: tests + charts + findingsUseful analysis begins by understanding what one row represents, where each field came from, how missingness is encoded, and which transformations are justified. Only then should summaries, statistical tests, or predictive models be trusted.
These skills guide Codex through data cleaning, exploratory data analysis, statistical analysis, visualization, and reporting with checks that make the work easier to inspect and repeat.
Inspect schemas, types, units, ranges, duplicates, category levels, date coverage, missingness, and suspicious values before choosing a method.
Standardize fields, resolve types, handle nulls, join tables, reshape records, and preserve a clear account of what changed.
Calculate suitable summaries, compare groups, investigate relationships, test assumptions, and report uncertainty without overstating causation.
Create readable plots, tables, notebooks, scripts, validation checks, and a plain-language account of methods, limitations, and findings.
The workflow records the question and data grain first, then keeps transformations visible so another person can rerun and challenge the result.
Clarify the question, population, unit of analysis, time window, comparison, outcome, and what action the result may inform.
Create a quality report, define missing-value treatment, correct types, check joins, test totals, and save derived fields in code.
Use distributions, grouped summaries, visualizations, statistical tests, or models that fit the question and data-generating process.
Check sensitivity, leakage, residual issues, edge cases, and reproducibility, then explain what the evidence does and does not support.
The skill can adapt its instructions to the files and libraries already used in your repository.
Clean, merge, reshape, aggregate, visualize, and validate tabular data in scripts or notebooks.
Prepare data, run statistical analysis, build graphics, and render repeatable research or business reports.
Check table grain, write readable queries, validate joins, calculate cohorts, and reconcile output with source totals.
Combine code, results, charts, interpretation, assumptions, and limitations in an ordered analysis record.
The workflow supports quick investigations and longer analytical projects without skipping the checks that make conclusions trustworthy.
These skills are useful when the analysis must be clear enough for someone else to inspect, rerun, and act on.
Move from an unclear request to a tested dataset, analysis plan, useful output, and concise explanation.
Document cleaning, assumptions, statistical choices, sensitivity checks, figures, and limitations.
Analyze funnels, cohorts, experiments, service levels, forecasts, and recurring business metrics.
Create reliable transformation scripts, validation checks, reporting jobs, and analysis-ready tables.
The skills assist with analytical work but do not make a weak dataset representative or turn association into causation. Important financial, medical, policy, and scientific decisions require qualified review and independent validation.
Place the skill where it can read the data dictionary, code, validation rules, and expected deliverables.
Keep the SKILL.md file with any analysis checklists, code conventions, and supporting references included in the folder.
Use project scope for one dataset and its business rules, or personal scope for a general analysis workflow.
Add field meanings, units, grain, source systems, refresh dates, known quality issues, sensitive columns, and access restrictions.
Record the language, libraries, environment, output format, testing method, and whether notebooks or production scripts are expected.
Tell Codex the decision, population, period, comparison, desired evidence, and constraints before requesting analysis.
Practical answers about files, statistics, dashboards, machine learning, and sensitive information.
They can guide work with formats supported by your environment, including CSV, TSV, JSON, spreadsheets, Parquet, database tables, and API exports.
They can narrow the options by checking the question, variable types, design, assumptions, and sample structure. A qualified analyst should review consequential results.
Yes. They can structure preprocessing, train-test separation, pipelines, cross-validation, metrics, error analysis, and leakage checks when prediction is the actual goal.
They can help prepare metrics, queries, chart specifications, and dashboard code. The workflow first verifies the calculations and intended decisions behind each view.
Follow your organization's access, retention, de-identification, and approved-tool rules. Do not place protected data in an environment that is not authorized to process it.
Known grain. Tested calculations. Honest uncertainty. Results people can review.