code-notebooks
/code-notebooks
Generated, step-by-step tutorial and workflow notebooks - a build script writes each .ipynb, every section explains the theory with equations, every claim is a print plus an assert, the notebook executes clean and writes a gate JSON. Use when creating or changing any notebook, when a workflow needs a walkthrough, or when a notebook output looks stale.
- Author
- Benz-Poobua ↗
- Repository
- benz-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Generated, step-by-step tutorial and workflow notebooks - a build script writes each .ipynb, every section explains the theory with equations, every claim is a print plus an assert, the notebook executes clean and writes a gate JSON. Use when creating or changing any notebook, when a workflow needs a walkthrough, or when a notebook output looks stale.
Original author description
Generated, step-by-step tutorial and workflow notebooks - a build script writes each .ipynb, every section explains the theory with equations, every claim is a print plus an assert, the notebook executes clean and writes a gate JSON. Use when creating or changing any notebook, when a workflow needs a walkthrough, or when a notebook output looks stale.
How it works
- Rules
- Structure of a generated notebook
SKILL.md preview
---
name: code-notebooks
description: Generated, step-by-step tutorial and workflow notebooks - a build script writes each .ipynb, every section explains the theory with equations, every claim is a print plus an assert, the notebook executes clean and writes a gate JSON. Use when creating or changing any notebook, when a workflow needs a walkthrough, or when a notebook output looks stale.
---
# code-notebooks
A notebook is a check, not a picture: one that is not executed is not a check, and a claim without an
assert is an opinion. Notebooks walk a workflow step by step: input -> operation -> output -> check.
## Rules
- **Generated, never hand-edited.** `scripts/build_<name>_nb.py` (nbformat) writes `notebooks/<name>.ipynb`.
Edit the generator and re-run it. Hand-authored legacy notebooks stay as they are until rewritten.
- **Executed clean.** `jupyter nbconvert --to notebook --execute --inplace notebooks/<name>.ipynb`
(or the repo's `make nb`); 0 errors before anything is quoted. In a venv whose scripts carry stale
shebangs, call `<env>/bin/python -m jupyter`.
- **Every claim**: `print("[A3] <what is claimed> = <value>")` **and** `assert <condition>, "<message>"`.
Each notebook writes `results/nb/<name>_gates.json`; quoted numbers go through the tracer (`benz:paper-numbers`).
- **Theory in the markdown, step by step**: define every symbol, derive the equation, cite the source with
page and equation number (`benz:paper-read`), state assumptions and the regime where the method holds.
- **Reproducible**: the house rcParams block in the first code cell (`benz:code-house-style`), seeds fixed,
paths relative to the repo, no hidden state (cells run top to bottom), data read-only.
- **Small outputs**: no giant arrays printed; animations through `to_jshtml()` inside
`mpl.rc_context({"savefig.dpi": 100})` (jshtml frames use `savefig.dpi`, 300 by default: 5x bloat).
## Structure of a generated notebook
```
# <Title> — <one-line purpose>
> Data: <paths> | Config: <file> | Env: <venv> | Generated by scripts/build_<name>_nb.py — do not edit
## (A) <first step: load / inspect> markdown theory -> code -> figure -> [A1..] print+assert
## (B) <next step> ...
## (Z) Summary table of every gate id with its value; write gates JSON
```
Completion: the generator runs, the notebook executes with 0 errors, every gate id appears in the JSON,
and the book link (if the notebook supports a book section) is refreshed with
`mypaper/mybible/scripts/link_notebooks_to_book.py --write`.
Versions
The database has no other skills named code-notebooks.
Database snapshot: 13.11.2026 · package version 277444c8990d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95jupyter-notebook
Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script `new_notebook.py` to generate a clean starting notebook. - 90jupyter-notebook
Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials. - 100jupyter-notebook
Use when the user asks to create, scaffold, or edit Jupyter notebooks (`.ipynb`) for experiments, explorations, or tutorials; prefer the bundled templates and run the helper script `new_notebook.py` to generate a clean starting notebook. - 100wolfram-notebooks
Reads and writes Wolfram notebook (.nb) files. Use this skill when the user needs to create, read, or convert Wolfram notebooks, including converting between markdown and notebook format. - 100jupyter-notebooks
Programmatically build and run Jupyter .ipynb notebooks end-to-end via the jupyter-notebooks MCP server — add/delete/move/update cells, execute cells or whole notebooks, manage kernel state, capture outputs, and export to HTML/PDF/Python. Use when authoring or executing a… - 95new-notebook
Scaffold a new notebook in this repo - creates the py:percent source in src/, registers it in notebooks.json with an accelerator, and builds it. Use when adding a notebook to the JAX-on-TPU series.