jupyter-live-kernel

Executes Python code in a stateful live Jupyter kernel with persistent variables.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill jupyter-live-kernel-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupyter-live-kernel
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/skills/data-science/jupyter-live-kernel
Command: npx skills add https://github.com/xu1713/openhorse --skill jupyter-live-kernel-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jupyterlab.

What problem does it solve? One-shot code execution loses all state between runs, forcing you to re-import libraries, reload data, and redefine variables on every step. This Skill provides a persistent Python REPL backed by a live Jupyter kernel so you can build up state incrementally while exploring data, APIs, or ML workflows. ## Core Features & Use Cases - Stateful Code Execution: Run Python code against a live Jupyter kernel where variables, imports, and objects persist across executions. - Variable Inspection: List and preview live kernel variables to inspect DataFrames, models, and intermediate results without re-running code. - Notebook Cell Editing: View, insert, replace, and delete notebook cells, plus restart-and-run-all verification for clean top-to-bottom execution. - Use Case: While exploring a new dataset, load it into a pandas DataFrame once, then iteratively filter, plot, and transform it across many steps without reloading, and finally verify the full notebook runs cleanly end to end. ## Quick Start Start a JupyterLab server, create a scratch notebook session, then ask the agent to execute Python code in the live kernel and inspect the resulting variables.

Frequently Asked Questions about jupyter-live-kernel

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

FAQPage Schema
How do I run Python code with persistent state between executions?

Use a live Jupyter kernel as a stateful REPL: execute code against a notebook session and variables, imports, and objects survive across calls. The jupyter_live_kernel.py script exposes execute, variables, and edit subcommands returning structured JSON.

When should I use a Jupyter kernel instead of one-shot code execution?

Use a live kernel for iterative exploration, data science, and ML tasks where you build state incrementally. Use one-shot execution for stateless scripts, and a terminal for shell commands, installs, and process management.

What are the prerequisites for running a live Jupyter kernel?

You need uv installed, JupyterLab installed via uv tool install, and a running Jupyter server. A kernel session must be created through the Jupyter REST API before code can execute.

Why does the first Jupyter kernel execution time out?

The kernel needs time to initialize after the server starts, so the first execution may exceed the 30-second default timeout. Retry once, or pass a larger timeout such as --timeout 120 for setup or heavy computation.

Can I install extra Python packages for the Jupyter kernel?

The kernel uses JupyterLab's Python environment, so packages must be installed into that environment. Install additional packages into the JupyterLab tool environment before importing them in executed code.