jupyter-python

Create, execute, and verify reproducible Python Jupyter notebooks with nbformat and nbclient.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill jupyter-python-schattenspiegel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jupyter-python
Source: https://github.com/schattenspiegel/skill-foundry-skills/tree/main/skills/jupyter-python
Command: npx skills add https://github.com/schattenspiegel/skill-foundry-skills --skill jupyter-python-schattenspiegel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nbformat, nbclient, and includes references (resource) components.

What problem does it solve? Jupyter notebooks often fail silently due to hidden kernel state, out-of-order cell execution, wrong kernel selection, or leaked credentials in outputs, making results impossible to reproduce. This Skill provides a disciplined workflow for inspecting, executing, and verifying .ipynb artifacts so a clean top-to-bottom run actually proves the notebook works. ## Core Features & Use Cases - Notebook Inspection: Check nbformat version, kernelspec, execution counts, parameters, secrets, and oversized outputs before trusting any saved results. - Deterministic Execution: Run notebooks with nbclient using an explicit kernel, working directory, timeout, and stop-on-error behavior, writing results to a separate executed artifact. - Reproducibility Verification: Re-run from clean inputs, compare material artifacts, set random seeds, and move reusable logic into tested modules. - Use Case: A colleague shares analysis.ipynb that worked on their machine. Use this Skill to select the correct project kernel, restart and execute all cells top-to-bottom, detect hidden-state failures, and produce a verified executed notebook artifact. ## Quick Start Review and execute the notebook analysis.ipynb top-to-bottom with the project kernel, then save the verified executed copy to a separate artifact.

Frequently Asked Questions about jupyter-python

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

FAQPage Schema
How do I execute a Jupyter notebook from Python code?▼

Use nbclient with nbformat to execute notebooks programmatically. Read the notebook with nbformat.read, create a NotebookClient with an explicit kernel_name, timeout, and working directory, call execute(), then write the result to a separate output file with nbformat.write.

How to make a Jupyter notebook reproducible?▼

Restart the kernel and run all cells top-to-bottom in a clean process as the minimum reproducibility test. Set random seeds, control clock and network inputs, use parameter cells instead of scattered manual edits, and re-run from clean inputs to compare artifacts.

Why does my notebook work interactively but fail on a fresh run?▼

The kernel retains variables, imports, and state from earlier cells, so out-of-order interactive execution can hide missing definitions. A clean top-to-bottom run after restart exposes this hidden-state failure, which saved outputs and execution counts alone cannot prove absent.

When should I move notebook code into a Python module?▼

Move reusable transformations, models, and validation into modules with unit tests whenever logic is reused or needs verification. Keep the notebook for orchestration, explanation, and display, and prefer a script or pipeline for unattended recurring execution.

What should I check before sharing a notebook file?▼

Inspect outputs for credentials, personal row data, and large binary or base64 content, and verify error outputs and execution counts. Confirm the kernelspec and language metadata match the intended environment so recipients can reproduce the run.