[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RQRP09R2BT6CBSK6MH7R1":3,"skill-same:01M77RQRP09R2BT6CBSK6MH7R1":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M77RQRP09R2BT6CBSK6MH7R1","jupyter-live-kernel",null,"Iterative Python via live Jupyter kernel (hamelnb).","vdcworkshop\u002FSkills-Catalog","vdcworkshop","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275270998?v=4","01M77R8FXSKYTB2X9SSVJN7ZRZ","αtef βouafif","01M77R8FYGECN2YWM6WVBVPMGS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F01 Tools\u002F06 CLI Tools\u002Fjupyter-live-kernel\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jupyter-live-kernel\ndescription: \"Iterative Python via live Jupyter kernel (hamelnb).\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [jupyter, notebook, repl, data-science, exploration, iterative]\n    category: data-science\n---\n\n# Jupyter Live Kernel (hamelnb)\n\nGives you a **stateful Python REPL** via a live Jupyter kernel. Variables persist\nacross executions. Use this instead of `execute_code` when you need to build up\nstate incrementally, explore APIs, inspect DataFrames, or iterate on complex code.\n\n## When to Use This vs Other Tools\n\n| Tool | Use When |\n|------|----------|\n| **This skill** | Iterative exploration, state across steps, data science, ML, \"let me try this and check\" |\n| `execute_code` | One-shot scripts needing hermes tool access (web_search, file ops). Stateless. |\n| `terminal` | Shell commands, builds, installs, git, process management |\n\n**Rule of thumb:** If you'd want a Jupyter notebook for the task, use this skill.\n\n## Prerequisites\n\n1. **uv** must be installed (check: `which uv`)\n2. **JupyterLab** must be installed: `uv tool install jupyterlab`\n3. A Jupyter server must be running (see Setup below)\n\n## Setup\n\nThe hamelnb script location:\n```\nSCRIPT=\"$HOME\u002F.agent-skills\u002Fhamelnb\u002Fskills\u002Fjupyter-live-kernel\u002Fscripts\u002Fjupyter_live_kernel.py\"\n```\n\nIf not cloned yet:\n```\ngit clone https:\u002F\u002Fgithub.com\u002Fhamelsmu\u002Fhamelnb.git ~\u002F.agent-skills\u002Fhamelnb\n```\n\n### Starting JupyterLab\n\nCheck if a server is already running:\n```\nuv run \"$SCRIPT\" servers\n```\n\nIf no servers found, start one:\n```\njupyter-lab --no-browser --port=8888 --notebook-dir=$HOME\u002Fnotebooks \\\n  --IdentityProvider.token='' --ServerApp.password='' > \u002Ftmp\u002Fjupyter.log 2>&1 &\nsleep 3\n```\n\nNote: Token\u002Fpassword disabled for local agent access. The server runs headless.\n\n### Creating a Notebook for REPL Use\n\nIf you just need a REPL (no existing notebook), create a minimal notebook file:\n```\nmkdir -p ~\u002Fnotebooks\n```\nWrite a minimal .ipynb JSON file with one empty code cell, then start a kernel\nsession via the Jupyter REST API:\n```\ncurl -s -X POST http:\u002F\u002F127.0.0.1:8888\u002Fapi\u002Fsessions \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"path\":\"scratch.ipynb\",\"type\":\"notebook\",\"name\":\"scratch.ipynb\",\"kernel\":{\"name\":\"python3\"}}'\n```\n\n## Core Workflow\n\nAll commands return structured JSON. Always use `--compact` to save tokens.\n\n### 1. Discover servers and notebooks\n\n```\nuv run \"$SCRIPT\" servers --compact\nuv run \"$SCRIPT\" notebooks --compact\n```\n\n### 2. Execute code (primary operation)\n\n```\nuv run \"$SCRIPT\" execute --path \u003Cnotebook.ipynb> --code '\u003Cpython code>' --compact\n```\n\nState persists across execute calls. Variables, imports, objects all survive.\n\nMulti-line code works with $'...' quoting:\n```\nuv run \"$SCRIPT\" execute --path scratch.ipynb --code $'import os\\nfiles = os.listdir(\".\")\\nprint(f\"Found {len(files)} files\")' --compact\n```\n\n### 3. Inspect live variables\n\n```\nuv run \"$SCRIPT\" variables --path \u003Cnotebook.ipynb> list --compact\nuv run \"$SCRIPT\" variables --path \u003Cnotebook.ipynb> preview --name \u003Cvarname> --compact\n```\n\n### 4. Edit notebook cells\n\n```\n# View current cells\nuv run \"$SCRIPT\" contents --path \u003Cnotebook.ipynb> --compact\n\n# Insert a new cell\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> insert \\\n  --at-index \u003CN> --cell-type code --source '\u003Ccode>' --compact\n\n# Replace cell source (use cell-id from contents output)\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> replace-source \\\n  --cell-id \u003Cid> --source '\u003Cnew code>' --compact\n\n# Delete a cell\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> delete --cell-id \u003Cid> --compact\n```\n\n### 5. Verification (restart + run all)\n\nOnly use when the user asks for a clean verification or you need to confirm\nthe notebook runs top-to-bottom:\n\n```\nuv run \"$SCRIPT\" restart-run-all --path \u003Cnotebook.ipynb> --save-outputs --compact\n```\n\n## Practical Tips from Experience\n\n1. **First execution after server start may timeout** — the kernel needs a moment\n   to initialize. If you get a timeout, just retry.\n\n2. **The kernel Python is JupyterLab's Python** — packages must be installed in\n   that environment. If you need additional packages, install them into the\n   JupyterLab tool environment first.\n\n3. **--compact flag saves significant tokens** — always use it. JSON output can\n   be very verbose without it.\n\n4. **For pure REPL use**, create a scratch.ipynb and don't bother with cell editing.\n   Just use `execute` repeatedly.\n\n5. **Argument order matters** — subcommand flags like `--path` go BEFORE the\n   sub-subcommand. E.g.: `variables --path nb.ipynb list` not `variables list --path nb.ipynb`.\n\n6. **If a session doesn't exist yet**, you need to start one via the REST API\n   (see Setup section). The tool can't execute without a live kernel session.\n\n7. **Errors are returned as JSON** with traceback — read the `ename` and `evalue`\n   fields to understand what went wrong.\n\n8. **Occasional websocket timeouts** — some operations may timeout on first try,\n   especially after a kernel restart. Retry once before escalating.\n\n## Timeout Defaults\n\nThe script has a 30-second default timeout per execution. For long-running\noperations, pass `--timeout 120`. Use generous timeouts (60+) for initial\nsetup or heavy computation.\n","# Jupyter Live Kernel (hamelnb)\n\nGives you a **stateful Python REPL** via a live Jupyter kernel. Variables persist\nacross executions. Use this instead of `execute_code` when you need to build up\nstate incrementally, explore APIs, inspect DataFrames, or iterate on complex code.\n\n## When to Use This vs Other Tools\n\n| Tool | Use When |\n|------|----------|\n| **This skill** | Iterative exploration, state across steps, data science, ML, \"let me try this and check\" |\n| `execute_code` | One-shot scripts needing hermes tool access (web_search, file ops). Stateless. |\n| `terminal` | Shell commands, builds, installs, git, process management |\n\n**Rule of thumb:** If you'd want a Jupyter notebook for the task, use this skill.\n\n## Prerequisites\n\n1. **uv** must be installed (check: `which uv`)\n2. **JupyterLab** must be installed: `uv tool install jupyterlab`\n3. A Jupyter server must be running (see Setup below)\n\n## Setup\n\nThe hamelnb script location:\n```\nSCRIPT=\"$HOME\u002F.agent-skills\u002Fhamelnb\u002Fskills\u002Fjupyter-live-kernel\u002Fscripts\u002Fjupyter_live_kernel.py\"\n```\n\nIf not cloned yet:\n```\ngit clone https:\u002F\u002Fgithub.com\u002Fhamelsmu\u002Fhamelnb.git ~\u002F.agent-skills\u002Fhamelnb\n```\n\n### Starting JupyterLab\n\nCheck if a server is already running:\n```\nuv run \"$SCRIPT\" servers\n```\n\nIf no servers found, start one:\n```\njupyter-lab --no-browser --port=8888 --notebook-dir=$HOME\u002Fnotebooks \\\n  --IdentityProvider.token='' --ServerApp.password='' > \u002Ftmp\u002Fjupyter.log 2>&1 &\nsleep 3\n```\n\nNote: Token\u002Fpassword disabled for local agent access. The server runs headless.\n\n### Creating a Notebook for REPL Use\n\nIf you just need a REPL (no existing notebook), create a minimal notebook file:\n```\nmkdir -p ~\u002Fnotebooks\n```\nWrite a minimal .ipynb JSON file with one empty code cell, then start a kernel\nsession via the Jupyter REST API:\n```\ncurl -s -X POST http:\u002F\u002F127.0.0.1:8888\u002Fapi\u002Fsessions \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"path\":\"scratch.ipynb\",\"type\":\"notebook\",\"name\":\"scratch.ipynb\",\"kernel\":{\"name\":\"python3\"}}'\n```\n\n## Core Workflow\n\nAll commands return structured JSON. Always use `--compact` to save tokens.\n\n### 1. Discover servers and notebooks\n\n```\nuv run \"$SCRIPT\" servers --compact\nuv run \"$SCRIPT\" notebooks --compact\n```\n\n### 2. Execute code (primary operation)\n\n```\nuv run \"$SCRIPT\" execute --path \u003Cnotebook.ipynb> --code '\u003Cpython code>' --compact\n```\n\nState persists across execute calls. Variables, imports, objects all survive.\n\nMulti-line code works with $'...' quoting:\n```\nuv run \"$SCRIPT\" execute --path scratch.ipynb --code $'import os\\nfiles = os.listdir(\".\")\\nprint(f\"Found {len(files)} files\")' --compact\n```\n\n### 3. Inspect live variables\n\n```\nuv run \"$SCRIPT\" variables --path \u003Cnotebook.ipynb> list --compact\nuv run \"$SCRIPT\" variables --path \u003Cnotebook.ipynb> preview --name \u003Cvarname> --compact\n```\n\n### 4. Edit notebook cells\n\n```\n# View current cells\nuv run \"$SCRIPT\" contents --path \u003Cnotebook.ipynb> --compact\n\n# Insert a new cell\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> insert \\\n  --at-index \u003CN> --cell-type code --source '\u003Ccode>' --compact\n\n# Replace cell source (use cell-id from contents output)\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> replace-source \\\n  --cell-id \u003Cid> --source '\u003Cnew code>' --compact\n\n# Delete a cell\nuv run \"$SCRIPT\" edit --path \u003Cnotebook.ipynb> delete --cell-id \u003Cid> --compact\n```\n\n### 5. Verification (restart + run all)\n\nOnly use when the user asks for a clean verification or you need to confirm\nthe notebook runs top-to-bottom:\n\n```\nuv run \"$SCRIPT\" restart-run-all --path \u003Cnotebook.ipynb> --save-outputs --compact\n```\n\n## Practical Tips from Experience\n\n1. **First execution after server start may timeout** — the kernel needs a moment\n   to initialize. If you get a timeout, just retry.\n\n2. **The kernel Python is JupyterLab's Python** — packages must be installed in\n   that environment. If you need additional packages, install them into the\n   JupyterLab tool environment first.\n\n3. **--compact flag saves significant tokens** — always use it. JSON output can\n   be very verbose without it.\n\n4. **For pure REPL use**, create a scratch.ipynb and don't bother with cell editing.\n   Just use `execute` repeatedly.\n\n5. **Argument order matters** — subcommand flags like `--path` go BEFORE the\n   sub-subcommand. E.g.: `variables --path nb.ipynb list` not `variables list --path nb.ipynb`.\n\n6. **If a session doesn't exist yet**, you need to start one via the REST API\n   (see Setup section). The tool can't execute without a live kernel session.\n\n7. **Errors are returned as JSON** with traceback — read the `ename` and `evalue`\n   fields to understand what went wrong.\n\n8. **Occasional websocket timeouts** — some operations may timeout on first try,\n   especially after a kernel restart. Retry once before escalating.\n\n## Timeout Defaults\n\nThe script has a 30-second default timeout per execution. For long-running\noperations, pass `--timeout 120`. Use generous timeouts (60+) for initial\nsetup or heavy computation.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":35,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"category":32},[29,30,31,32,33,34],"jupyter","notebook","repl","data-science","exploration","iterative",[36,37,38],"linux","macos","windows","main","cd5116e81009ad620d09c7bc8664ce8c37f88a99","01 Tools\u002F06 CLI Tools\u002Fjupyter-live-kernel",0,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvdcworkshop","https:\u002F\u002Fvdcworkshop.com","2026-06-28 03:22:57",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add vdcworkshop\u002FSkills-Catalog --skill jupyter-live-kernel",{"tool":53,"command":54},"bunx","bunx skills add vdcworkshop\u002FSkills-Catalog --skill jupyter-live-kernel",{"tool":56,"command":57},"pnpm","pnpm dlx skills add vdcworkshop\u002FSkills-Catalog --skill jupyter-live-kernel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F01 Tools\u002F06 CLI Tools\u002Fjupyter-live-kernel\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"README.md","REFERENCE","参考文档",996,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F01 Tools\u002F06 CLI Tools\u002Fjupyter-live-kernel\u002FREADME.md",[68,75,82,90,97,104],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XBV88FMNX83MKDZMXKQZ2","rhaios-staging","Interact with the Rhaios staging REST API for yield operations. Discover -> prepare -> setup-if-needed -> sign -> execute flow with pluggable signer backend. Triggers on requests involving DeFi yield, vault deposits, redeems, rebalancing, or Rhaios API.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F03 DeFi\u002Frhaios-staging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77X7AFQGDCFHC25GQ7V92GZ","git-commit-push","Commit and push repository changes safely. Use when user asks to commit, push, or verify and push current changes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fgit-commit-push\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M77X71FJ1KR7PTBPRC7S2241","exec-slurm-compile","Compile TensorRT-LLM on a SLURM cluster. Covers submitting a batch job with a container image, monitoring the job, and verifying the build. Use when the user wants to compile TRT-LLM remotely via SLURM rather than on a local compute node.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fexec-slurm-compile\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M77X4BQJ025SPPGRQ96X72QV","databases","Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F11 Databases\u002F03 NoSQL Databases\u002Fdatabases\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M77WZYZGCV9DK5HA0XCWSK97","toast","Toast — restaurant POS, orders, menus, employees, revenue centers, and reporting.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Ftoast\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M77WYYESVCXT81ERPHM77SA9","k-schoollunch-menu","Use when the user asks for Korean school meal menus (급식 식단) by natural-language education office and school name, via k-skill-proxy NEIS school-search and school-meal routes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Fk-schoollunch-menu\u002FSKILL.md",[],[]]