jupyter-live-kernel

Execute Python code in a live Jupyter kernel with persistent state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates the friction of re-running stateless code by giving you a persistent, stateful Python environment where variables and objects survive across steps.

Core Features & Use Cases

  • Stateful Python REPL via live Jupyter kernel: Keep variables, imports, and objects across multiple executions for true iterative workflows.
  • Notebook-aware execution and editing: Discover servers/notebooks, execute code inside a selected notebook, and manage cells (insert, replace, delete) to evolve the notebook as you work.
  • Live inspection of runtime data: List variables and preview specific values to quickly verify assumptions during exploration.

Use this when you are exploring APIs, iterating on ML/data analysis code, inspecting DataFrames, or progressively building a notebook-like solution instead of running one-shot scripts.

Quick Start

Ask the agent to start a live Jupyter kernel session, create or select a scratch notebook, and iteratively run your Python code while keeping state across calls.

Frequently Asked Questions about jupyter-live-kernel

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

FAQPage Schema
How do I keep Python variables and imports persistent across multiple executions?

You can keep Python variables persistent across executions by using a stateful Jupyter kernel. This live environment retains your imports, DataFrames, and objects in memory, enabling true iterative workflows without restarting the session.

What is the best way to iteratively explore DataFrames without running one-shot scripts?

The best way to iteratively explore DataFrames without one-shot scripts is using a live Jupyter kernel. This stateful REPL lets you execute code progressively, list variables, and preview specific DataFrame values to verify assumptions during exploration.

Do I need a local Jupyter server running to use a stateful Python kernel?

Yes, you need a running local Jupyter server reachable by REST or WebSocket. You also need uv and JupyterLab installed to utilize the hamelnb toolchain for executing code and managing notebook cells within a target notebook.

Can I execute Python code and manage notebook cells through a live kernel?

Yes, you can execute Python code inside a selected notebook and manage its cells. The live kernel supports basic cell management operations including insert, replace, and delete to help you evolve the notebook as you work.

How do I list and preview live variables during Python data analysis?

To list and preview live variables during Python data analysis, use the live inspection features of the Jupyter kernel. This allows you to list active variables and preview specific values to verify your assumptions during exploration.

Why does my Python exploration code lose state when running multiple steps?

Your Python exploration code loses state because standard execution is stateless. Using a stateful Jupyter kernel eliminates this friction by keeping variables, imports, and objects alive across multiple execution steps for true iterative development.