Skill Detail

Run Agent-Assisted Notebook Workflows in JupyterLab With Notebook Intelligence

Use Notebook Intelligence to add chat, inline edit, autocomplete, MCP tools, Claude Code mode, and coding-agent launchers directly inside JupyterLab.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 322 GitHub stars ⬇ 475/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-agent-assisted-notebook-workflows-in-jupyterlab-with-notebook-intelligence Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Python environment with JupyterLab, notebook-intelligence, optional Node.js for Claude Code and MCP server launchers, and an LLM provider such as GitHub Copilot, OpenAI-compatible/LiteLLM endpoint, Ollama, or Claude Code
Install & setup
Install with pip install notebook-intelligence, restart JupyterLab, open the NBI panel, configure a provider or enable Claude mode, and optionally add MCP servers in ~/.jupyter/nbi/mcp.json or use launcher tiles for installed agent CLIs.
Author
Mehmet Bektas
Publisher
Individual
Last updated
Jul 21, 2026
Quick brief

Notebook Intelligence is a JupyterLab extension for agent-assisted notebook work. The operator installs the extension, opens the NBI panel in JupyterLab, connects GitHub Copilot, an OpenAI-compatible endpoint, LiteLLM, Ollama, or Claude mode, then uses chat, inline edits, autocomplete, MCP tools, rulesets, and coding-agent launcher tiles while working inside notebooks.

How it works

What this skill actually does

Use this instead of using a separate chat product or terminal agent when the work is centered on notebooks and the agent needs notebook-aware context, cell execution, file edits, Jupyter UI tools, or Claude Code sessions opened from the current JupyterLab directory. It fits data-science, research, teaching, and exploratory coding workflows where notebook state matters.

The scope boundary is notebook-native agent assistance inside JupyterLab. It is not a generic Jupyter extension listing, not a model provider card, and not a broad framework. The approved workflow is bringing an existing agent/provider surface into notebook authoring, execution, MCP tooling, and review without leaving the notebook workspace.