← ClaudeAtlas

jupyter-live-kernellisted

Run iterative, stateful Python through a live Jupyter kernel (hamelnb script) when you need variables to persist across steps for data-science or exploratory work.
aashutosh396/mindpalace · ★ 0 · AI & Automation · score 78
Install: claude install-skill aashutosh396/mindpalace
# Jupyter Live Kernel (hamelnb) Gives you a **stateful Python REPL** via a live Jupyter kernel. Variables persist across executions. Use this instead of one-shot `python -c` / `python script.py` runs when you need to build up state incrementally, explore APIs, inspect DataFrames, or iterate on complex code. ## When to Use This vs Plain Bash | Approach | Use When | |------|----------| | **This skill** | Iterative exploration, state across steps, data science, ML, "let me try this and check" | | `python script.py` / `python -c` (via bash) | One-shot scripts. State does not persist between runs. | | Plain shell commands (via bash) | Builds, installs, git, process management | **Rule of thumb:** If you'd want a Jupyter notebook for the task, use this skill. ## Prerequisites 1. **uv** must be installed (check: `which uv`) 2. **JupyterLab** must be installed: `uv tool install jupyterlab` 3. A Jupyter server must be running (see Setup below) ## Setup The hamelnb script location: ``` SCRIPT="$HOME/.agent-skills/hamelnb/skills/jupyter-live-kernel/scripts/jupyter_live_kernel.py" ``` If not cloned yet: ``` git clone https://github.com/hamelsmu/hamelnb.git ~/.agent-skills/hamelnb ``` ### Starting JupyterLab Check if a server is already running: ``` uv run "$SCRIPT" servers ``` If no servers found, start one: ``` jupyter-lab --no-browser --port=8888 --notebook-dir=$HOME/notebooks \ --IdentityProvider.token='' --ServerApp.password='' > /tmp/jupyter.log 2>&1 & sleep 3 ``` Not