jupyter-live-kernel

Execute Python code in a stateful REPL via a live Jupyter kernel.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/afel6/scal-ai-pipeline --skill jupyter-live-kernel-afel6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupyter-live-kernel
Source: https://github.com/afel6/scal-ai-pipeline/tree/main/hermes_skills_library/data-science/jupyter-live-kernel
Command: npx skills add https://github.com/afel6/scal-ai-pipeline --skill jupyter-live-kernel-afel6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Allows users to run and evolve Python code in a stateful REPL powered by a live Jupyter kernel, enabling iterative experimentation without losing context.

Core Features & Use Cases

  • Stateful Python REPL with persistent variables across executions.
  • Ideal for data science, ML experimentation, API exploration, and building complex code step-by-step.
  • Terminal-based workflow with commands to discover servers, execute code, inspect variables, and manage notebooks.

Quick Start

Start a JupyterLab kernel and run iterative Python code against a live session using the hamelnb-based CLI.

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 multiple code executions for iterative data exploration?

To keep Python variables persistent across executions, you can use a stateful Python REPL powered by a live Jupyter kernel. This preserves your working context so you can iteratively refine code and explore data without losing variables between runs.

What is the best way to prototype machine learning models step-by-step without losing context?

The best way to prototype ML models step-by-step is using a live Jupyter kernel that provides a stateful Python REPL. This approach supports iterative ML experimentation by maintaining your variables and execution state as you build complex code incrementally.

Do I need a Jupyter server to run a stateful Python REPL for data science?

Yes, you need a Jupyter server to run this stateful Python REPL. The workflow requires Jupyter server tooling, specifically using uv and hamelnb, to discover servers, execute code, inspect variables, and manage notebooks for data science tasks.

Can I inspect variables and manage notebooks via a terminal-based workflow?

Yes, you can inspect variables and manage notebooks through a terminal-based workflow. The live Jupyter kernel REPL provides CLI commands to execute code, inspect variables, edit notebooks, and discover available servers directly from the terminal.

Does a live Jupyter kernel work for API exploration and complex code prototyping?

A live Jupyter kernel works well for API exploration and complex code prototyping. By providing a stateful Python REPL, it allows you to test API calls incrementally and build complex code step-by-step while preserving your execution context and variables.