auditing-jupyter-execution-order
CommunityCatch notebook run-order bugs before sharing
Data & Analytics#jupyter#reproducibility#data-science#notebook#papermill#execution-count#notebook-audit
Authorrocklambros
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill audits Jupyter notebooks for execution-order mistakes that can make results unreproducible, misleading, or unsafe to share. It helps you catch cells that ran out of order, were edited but not re-run, or silently depend on stale notebook state.
Core Features & Use Cases
- Run-order validation: Detects non-monotonic execution counts that indicate the kernel executed cells in a different order than the notebook layout.
- Stale-state detection: Flags unrun cells that downstream cells still reference, helping expose hidden dependence on old bindings.
- Notebook safety checks: Surfaces errored cells, cleared-output notebooks, and papermill-produced notebooks so you can choose the right review path.
- Sharing and grading readiness: Ideal before sending a notebook to teammates, committing it, submitting it for class, or turning it into a paper or report.
Quick Start
Ask this Skill to audit the attached Jupyter notebook for out-of-order, unrun, or stale cells and tell you whether it is safe to share.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: auditing-jupyter-execution-order Download link: https://github.com/rocklambros/rcs/archive/main.zip#auditing-jupyter-execution-order Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 537,000+ vetted skills library on demand.