jupyter-live-kernel

Execute stateful Python code through a live Jupyter kernel with persistent variables.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/maopujie10-sys/Bailongma --skill jupyter-live-kernel-maopujie10-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupyter-live-kernel
Source: https://github.com/maopujie10-sys/Bailongma/tree/main/skills/hermes-skills/data-science/jupyter-live-kernel
Command: npx skills add https://github.com/maopujie10-sys/Bailongma --skill jupyter-live-kernel-maopujie10-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, jupyterlab, and includes scripts (resource) components.

What problem does it solve? One-shot code execution loses all state between runs, forcing you to re-import libraries, reload data, and recompute intermediate results on every step. This Skill provides a persistent Python REPL backed by a live Jupyter kernel, so variables, imports, and objects survive across executions for true iterative exploration. ## Core Features & Use Cases - Stateful Code Execution: Run Python code against a live kernel where variables, imports, and DataFrames persist across calls. - Variable Inspection: List and preview live kernel variables to inspect 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 dataset, load a CSV into a pandas DataFrame, inspect its shape, try several cleaning transformations, and preview the results step by step without ever reloading the data. ## Quick Start Start a JupyterLab server, create a scratch notebook session, then ask the agent to run 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 via the jupyter_live_kernel.py script's execute command, which keeps variables, imports, and objects alive across calls. Point it at a notebook path with an active kernel session and pass code with the --code flag.

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

Use a live kernel for iterative exploration, data science work, and building state incrementally across steps. Use one-shot execution for stateless scripts that need tool access like web search or file operations, and the terminal for shell commands and installs.

How do I inspect variables in a running Jupyter kernel?

Run the variables subcommand with the notebook path to list all live variables, or add preview with a variable name to inspect a specific object's contents. Always include the --compact flag to reduce verbose JSON output.

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 the command, or pass a larger value such as --timeout 120 for setup and 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 before use. Install them into the JupyterLab tool environment first, then they become importable in kernel executions.