What problem does it solve? Jupyter notebooks often become unreproducible, unreviewable, and unsafe to commit—hidden state, unpinned dependencies, leaked secrets, and messy diffs undermine analysis and research work. This Skill provides a disciplined workflow for authoring, running, reviewing, and shipping notebooks that stay reproducible. ## Core Features & Use Cases - Reproducible scaffolding: Set up projects with uv or poetry, pinned dependencies, locked environments, seeds, and version-printing first cells. - Headless CI execution: Run notebooks with papermill, export to HTML/PDF via nbconvert, and keep notebooks tested on every pull request. - Review and hygiene tooling: Use nbstripout, nbqa ruff, nbqa mypy, and nbdime for clean diffs, linting, and typechecking. - Use Case: A data scientist needs a quarterly report notebook that runs nightly in CI, exports HTML for stakeholders, and passes code review with readable diffs—this Skill defines the exact layout, tooling, and verification checklist. ## Quick Start Ask the assistant to scaffold a reproducible Jupyter notebook project with pinned dependencies, papermill CI execution, and output-stripping pre-commit hooks.