notebook-cell-python

name	notebook-cell-python
description	Cell-based .py ↔ .ipynb workflow — the .py is source-of-truth, the .ipynb is auto-derived for browser viewing of code + outputs + figures. Use when authoring a script that must run as a script (PR/CI) AND be viewable as a notebook; common home examples/<project>/tasks/<task>/. Trigger: cell-based py, .py to .ipynb, notebook from script, jupytext-style cells.
allowed-tools	Bash, Read, Write, Edit
metadata	{"version":"0.1.0","last_updated":"2026-05-31","summary":"Cell-based .py ↔ .ipynb workflow — the .py is source-of-truth, the .ipynb is auto-derived for browser viewing of code + outputs + figures."}

Skill: notebook-cell-python

Cell-based .py ↔ .ipynb workflow. The .py is the source of truth; the .ipynb is auto-derived for browser viewing of code + outputs + figures.

Used in any project where code must be runnable both as a script (PR review, CI) and as a notebook (Jupyter, embedded figures). Most common home: examples/<project>/tasks/<task>/.

---

When to Use

Trigger this skill when:

• The user asks for cell-based .py files that convert to .ipynb.
• A project has *.py next to a notebook/ folder of derived .ipynb.
• You need to author a script someone will read both as (in diff/PR) and as (with embedded outputs).