jupyter-live-kernel

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jupyterlab, uv.

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 DataFrames 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 objects persist between calls, ideal for incremental data exploration. - Variable Inspection: List and preview live kernel variables to inspect DataFrames, model outputs, or intermediate results without re-running code. - Notebook Cell Editing: View, insert, replace, and delete notebook cells programmatically, plus restart-and-run-all verification for clean top-to-bottom execution. - Use Case: A data scientist exploring a new dataset can load a CSV into a DataFrame, iteratively test cleaning transformations, inspect column statistics, and build up an analysis step by step without losing any state. ## 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 in a persistent Jupyter kernel from the command line?▼

Use the jupyter_live_kernel.py script with the execute subcommand, passing --path to a notebook and --code with your Python code. State persists across calls, so variables and imports survive between executions.

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

Use a live kernel when you need state to persist across steps, such as iterative data exploration, DataFrame inspection, or building up complex code incrementally. Use one-shot execution for stateless scripts that need direct tool access.

What are the prerequisites for running a Jupyter kernel programmatically?▼

You need uv installed, JupyterLab installed via uv tool install, and a running Jupyter server. You must also create a kernel session through the Jupyter REST API before executing code against a notebook.

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 default 30-second timeout. Retry the call or pass a larger timeout such as --timeout 120 for initial setup or heavy computation.

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

Use the variables subcommand with list to see all live variables, or preview with --name to inspect a specific variable's contents. Add --compact to reduce verbose JSON output and save tokens.