jupyter-live-kernel

Runs a stateful Python REPL on a live Jupyter kernel preserving variables across executions.

31|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill jupyter-live-kernel-markwang2658
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupyter-live-kernel
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/skills/data-science/jupyter-live-kernel
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill jupyter-live-kernel-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Stateful Python execution becomes challenging when you need to build up state across steps. This skill provides a live Jupyter kernel that preserves variables between executions, enabling iterative exploration and rapid prototyping.

Core Features & Use Cases

  • Stateful Python REPL via a live Jupyter kernel with persistent variables across commands.
  • Headless, script-driven interaction using a deterministic workflow to execute code and inspect results.
  • Use cases include data science exploration, API prototyping, and debugging workflows that benefit from session state.

Quick Start

Install uv and JupyterLab, ensure a running Jupyter server, and start the kernel via the hamelnb script to begin an interactive session.

Frequently Asked Questions about jupyter-live-kernel

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

FAQPage Schema
How do I preserve Python variables across multiple executions?

A stateful Python REPL via a live Jupyter kernel preserves variables across executions, enabling iterative data exploration and rapid API prototyping. Session state is maintained in the kernel, allowing subsequent commands to access previously defined variables.

What is a stateful Python REPL and when do I need it for data science?

A stateful Python REPL is an interactive environment that retains variables and objects between sequential code executions. It is needed for data science exploration, API prototyping, and debugging workflows that require building up session state across multiple iterative steps.

Do I need JupyterLab installed to run a stateful Python kernel?

Yes, you need JupyterLab and uv installed to run this stateful Python kernel. You must also ensure a running Jupyter server managed by the hamelnb tool located under ~/.agent-skills/hamelnb to execute commands and inspect results in the interactive session.

What's the best way to debug Python code with persistent session state?

The best way to debug Python code with persistent session state is using a live Jupyter kernel. It allows you to execute code iteratively via script-driven interaction, preserving variables so you can inspect and troubleshoot results across multiple sequential steps without restarting.

Are there limitations to using a live Jupyter kernel for interactive Python?

Using a live Jupyter kernel for interactive Python requires a continuously running Jupyter server managed by the hamelnb tool. If the server stops or restarts, the persistent variables and session state are lost, requiring you to reinitialize your environment.