jupyter-live-kernel

Execute Python code incrementally in a stateful Jupyter kernel.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a stateful Python REPL via a live Jupyter kernel, enabling iterative development and state persistence across code executions.

Core Features & Use Cases

  • Stateful Python REPL: Offers a Python environment where variables persist across executions.
  • Iterative Exploration: Ideal for building up state incrementally, exploring APIs, inspecting DataFrames, or iterating on complex code.
  • Use Case: When you need to experiment with code and see the results immediately, without restarting the environment.

Quick Start

Start a JupyterLab server and execute Python code incrementally using the uv run "$SCRIPT" execute command.

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 persistent across code executions in a REPL?

A stateful Python REPL keeps variables persistent across executions by using a live Jupyter kernel. This enables iterative code exploration without restarting the environment, preserving your state incrementally.

What is the best way to iteratively explore and inspect DataFrames in Python?

Iterative DataFrame exploration is best handled by a stateful Python environment using a live Jupyter kernel. It allows you to build up state incrementally and inspect DataFrames immediately across executions.

Do I need a running JupyterLab server to use a stateful Python REPL?

Yes, a stateful Python REPL requires a running JupyterLab server and a Python environment. You then execute Python code incrementally using the script execution command.

How does a stateful Jupyter kernel compare to a standard Python REPL for data science tasks?

A stateful Jupyter kernel provides persistent variables across executions, unlike a standard Python REPL. This is ideal for data science tasks requiring incremental development and complex code iteration.

When should I use a live Jupyter kernel for Python development instead of restarting the environment?

Use a live Jupyter kernel when you need to experiment with Python code and see results immediately without restarting the environment. It is ideal for exploring APIs and iterating on complex code.

Why does my Python REPL lose state between code executions during iterative development?

Your Python REPL loses state because it lacks a live Jupyter kernel for state persistence. A stateful Python environment resolves this by keeping variables active across executions.

Related Skills