jupyter-live-kernel

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jupyterlab, uv, 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. This Skill provides a persistent Python REPL backed by a live Jupyter kernel so variables, imports, and objects survive across executions. ## 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 debug and explore data interactively. - Notebook Cell Editing: Insert, replace, and delete notebook cells, plus restart-and-run-all verification for clean top-to-bottom runs. - Use Case: While exploring a large CSV dataset, load it into a pandas DataFrame once, then iteratively filter, aggregate, and plot across multiple executions without reloading the data each time. ## Quick Start Start a JupyterLab server and use the jupyter-live-kernel skill to run Python code in a persistent scratch notebook so I can explore my data step by step.

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 on a running JupyterLab server and each execution shares the same kernel session.

Jupyter kernel vs one-shot Python script execution, which should I use?▼

Use a live Jupyter kernel for iterative exploration, data science, and tasks where state must persist between steps. Use one-shot execution for stateless scripts that need no memory of prior runs, such as single file operations or web searches.

How do I inspect variables in a running Jupyter kernel?▼

Run the variables subcommand with the notebook path to list all live variables, or use variables preview with a specific name to inspect one value. Both return structured JSON output, and the --compact flag reduces token usage.

Why does the first Jupyter kernel execution time out?▼

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

Can I install packages for the Jupyter kernel environment?▼

The kernel uses JupyterLab's Python environment, so packages must be installed into that environment before use. Install JupyterLab itself with uv tool install jupyterlab, then add any additional packages to the same tool environment.