skills.rest
shammun
shammunCOMMUNITY
Explore all skills by this author →
GitHub

notebook-chapter

Rebuilds and headlessly executes one chapter's teaching notebook with optional change requests.

Updated Sep 13, 2026
Search Tags:#automation#validation#jupyter#teaching#notebook#rebuild#fluid mechanics
One-click install
npx skills add https://github.com/shammun/fluidpy --skill notebook-chapter-shammun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: notebook-chapter
Source: https://github.com/shammun/fluidpy/tree/main/.claude/skills/notebook-chapter
Command: npx skills add https://github.com/shammun/fluidpy --skill notebook-chapter-shammun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rebuilding a chapter's teaching notebook after physics fixes, new explainers, or teaching feedback requires re-briefing the builder agent, re-executing the notebook, and re-validating embeds by hand, which is repetitive and error-prone. ## Core Features & Use Cases - Change Request Handling: Appends the user's requested change to the chapter's design document under a dated Revisions section before rebuilding. - Agent-Orchestrated Rebuild: Briefs the notebook-builder agent using the phase 8 brief format from the /do-chapter workflow. - Execution Gates: Runs tools/run_notebook.py and tools/embed_check.py headlessly and requires OK output before committing. - Use Case: After fixing a derivation in Chapter 7, run the skill with a change note, and it rebuilds, executes, validates, commits, and republishes the chapter notebook and its Colab twin. ## Quick Start Rebuild chapter 7's teaching notebook and add a tiny worked example for group velocity before executing and validating it.

Frequently Asked Questions about notebook-chapter

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

FAQPage Schema
How do I rebuild a chapter notebook after making physics fixes?▼

Run /notebook-chapter with the chapter number, optionally followed by a quoted change request. The skill briefs the notebook-builder agent, executes the notebook headlessly with run_notebook.py, and validates embeds before committing.

How do I add a change request when rebuilding a teaching notebook?▼

Pass the change as a quoted string after the chapter number, for example /notebook-chapter 7 "add a tiny example for group velocity". The request is appended to the chapter's design document under a dated Revisions section before the rebuild.

What validation gates must pass before the notebook is committed?▼

Two gates must print OK: tools/run_notebook.py chNN executes the notebook headlessly, and tools/embed_check.py chNN verifies all explainers are embedded. Only then is progress.json updated and the commit made.

Does rebuilding a notebook update the published web page and Colab version?▼

Yes, if the chapter was already published, the skill runs /publish-chapter N afterward so the HTML page, the executed .ipynb, and the Colab twin all stay in sync.

Why does the notebook rebuild stop before committing?▼

The commit is gated on validation: if run_notebook.py or embed_check.py does not print OK, the workflow halts. Fix the notebook content or missing explainers, then rerun the skill.

Related Skills

Explore More Education & Research Skills→
RebeccaStevensonRebeccaStevenson
13

quarto-books

Create multi-chapter Quarto book projects with HTML and PDF outputs.

Community
Intermediate
M4n5terM4n5ter
3

ipynb-notebooks

Organize ipynb notebooks into reusable project structures with uv/venv environments.

Community
Intermediate
asifhussain60asifhussain60

journal

Automate multi-chapter first-person memoir writing with voice and continuity governance.

Community
Advanced
gakonstgakonst

data

Automate headless execution and editing of Jupyter notebooks using uv and nbformat v4/jtool.

Community
Advanced