Create structured notebooks
Organize setup, data loading, exploration, analysis, figures, interpretation, checks, and conclusions into a readable flow.
Codex Skills for Jupyter Notebook help Codex create, repair, run, and organize notebooks for analysis, experiments, teaching, reports, and reproducible research. Download the skills for notebooks with a clear execution order, visible assumptions, useful outputs, and an environment another person can recreate.
task: complete jupyter notebook workflows task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffReliable notebooks combine code, narrative, data, environment information, figures, and execution state in one reviewable artifact.
These skills guide Codex to inspect the kernel, dependencies, data sources, cell order, stored outputs, metadata, and intended audience before changing the notebook.
Organize setup, data loading, exploration, analysis, figures, interpretation, checks, and conclusions into a readable flow.
Use Python or the declared kernel to clean data, run experiments, build models, visualize results, and extract reusable functions.
Find hidden state, broken imports, missing files, out-of-order cells, stale outputs, excessive memory use, and environment mismatches.
Record dependencies and parameters, control randomness, restart and run all cells, validate outputs, and prepare clean exports.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Identify the kernel, language, package versions, working directory, data paths, widgets, extensions, secrets, and expected outputs.
Define the input, assumptions, method, comparison, metric, figure, and conclusion the notebook must support.
Separate setup from analysis, keep cells focused, remove accidental state, add explanations, and preserve useful intermediate evidence.
Execute from a clean kernel, check warnings and figures, confirm deterministic behavior where needed, and export the requested format.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Clean, explore, summarize, visualize, model, and explain datasets with traceable transformations.
Document hypotheses, methods, parameters, experiments, evidence, limitations, and reproducible results.
Create guided explanations, examples, exercises, expected outputs, and learner-friendly progression.
Combine code, tables, charts, narrative, and conclusions for sharing as notebooks, HTML, PDF, or slides.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable jupyter notebook workflows work with a visible process.
Build understandable analyses with visible transformations, figures, checks, and conclusions.
Keep methods, code, parameters, evidence, and limitations together in a reproducible record.
Create notebooks that teach concepts through clear narrative, runnable examples, and exercises.
Move exploratory work toward tested modules, tracked environments, and reviewable results.
The skills can execute and edit notebooks when the environment and data are available. Sensitive data, expensive computation, consequential conclusions, and external publication require appropriate access, review, and validation.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with notebook structure, execution, analysis, visualization, reproducibility, and export guidance.
Use project scope for one dataset and environment, or personal scope for reusable notebook practices.
Provide language, kernel, package manager, dependency file, extensions, data locations, hardware needs, and export tools.
State the command or process for restarting, running all cells, testing outputs, controlling randomness, and handling secrets.
Practical answers about capabilities, limits, setup, and review.
Yes. They can work with notebook cells and metadata while preserving the notebook format and intended outputs.
Yes. The workflow restarts the kernel, runs cells in order, and removes dependencies on accidental interactive state.
Yes, when the required Jupyter kernel and tools are available and clearly identified.
Yes. They can extract reusable logic into modules or scripts while keeping the notebook focused on explanation and results.
Not always. Randomness, hardware, concurrency, external data, and package versions can affect results, so those factors are recorded and controlled where possible.
Clear context. Purposeful work. Relevant checks. A result others can understand.