agent-toolkit-cli 1.11.0__py3-none-win_amd64.whl

agent_toolkit/data/skills/tooling/herdr/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: herdr
+description: Manage Herdr workspaces, tabs, and panes for Agent Toolkit swarms with eager windows, shell-aware
+  execution, and reuse.
+origin:
+  type: first-party
+metadata:
+  author: ulises-jeremias
+  version: '1.0'
+  tags:
+  - herdr
+  - swarm
+  - workspace
+  - tmux
+  - orchestration
+---
+# Herdr
+
+Operate Herdr as the primary UI for `agent-toolkit swarm` — eager tabs, shell-consistent execution (`zsh`/`bash` via `_user_shell()`), and clean reuse of windows. This skill is the Herdr complement to `swarm` and `swarm-observer`.
+
+## When to use
+
+- Swarm was started with `--ui herdr` (default) and you need to inspect or recover Herdr state.
+- `herdr workspace list/create/tab create/pane run` behavior is unexpected (extra workspaces `w7-wA` for `headless`, wrong `--cwd`, or missing eager windows).
+- User prefers Herdr over tmux for its excellent interactive UX and wants to reuse tabs for sequential requests.
+
+## Prerequisites
+
+- `herdr` CLI installed and daemon running (`herdr --version`, `herdr workspace list --json` works; `--json` may be unsupported on older binaries — fallback to text).
+- Swarm run exists: `.agent-toolkit/swarm/runs/<run-id>/state.json` with `ui: herdr`.
+- Repo is a Git directory (worktrees are created under `.agent-toolkit/swarm/runs/<run-id>/worktrees/`).
+
+## Workflow
+
+### 1. Verify backend and shell
+
+```bash
+agent-toolkit swarm doctor --json | jq '.backends'
+herdr --version
+echo $SHELL; getent passwd $USER | cut -d: -f7  # should be /usr/bin/zsh on this host
+# swarm's _user_shell() picks: $SHELL -> pwd.getpwuid -> /usr/bin/zsh -> /bin/bash
+```
+
+### 2. Inspect Herdr state for a run
+
+```bash
+herdr workspace list --json 2>&1 | jq '.[] | {id,name,path,status}' | head -n 40
+# Expected: one workspace per run: swarm-20260807T...-<short>
+# Orphan check: workspaces w7-wA with headless run-id -> delete after fixing backend
+
+agent-toolkit swarm status --run-id <run-id> --json | jq '{ui,recipe,runner,model_profile,worktrees,handoffs}'
+agent-toolkit swarm handoffs --run-id <run-id> --json | jq
+herdr workspace list | grep swarm-<run-id>
+```
+
+### 3. Eager windows (automatic on swarm start)
+
+On `swarm start --ui herdr`, swarm creates **one tab per role** immediately:
+
+- `tab create --workspace swarm-<run-id> --name <role>` for each role (`implementer`, `reviewer`, `integrator`, ... plus `1` for coordinator).
+- Each non-implementer tab runs: `echo "Waiting for handoff: <pred> -> <role> | role: <role> | run: <run-id>"` via `<shell> -lc` (quoted to avoid `| pipe` issues) and records `agent_waiting` trace.
+- `select-window` / `workspace focus` focuses `implementer`; implementer pane runs `export AGENT_TOOLKIT_SWARM_RUN_ID=... RUN_DIR=... REPO=... SWARMFORGE_ROLE=implementer && cd <worktree> && exec <runner> "$(cat prompt)"`.
+
+If a tab is missing:
+
+```bash
+herdr tab create --workspace swarm-<run-id> --name reviewer --json 2>&1 | jq
+herdr pane run --workspace swarm-<run-id> --tab reviewer --command "/usr/bin/zsh -lc 'echo \"Waiting for handoff: implementer -> reviewer | role: reviewer | run: <run-id>\"'" --json 2>&1 | jq
+```
+
+### 4. Recover from known pitfalls
+
+| Symptom | Fix |
+|---------|-----|
+| Extra workspaces for `headless` runs | `get_backend("headless")` fallback created spurious Herdr workspaces. Patch `swarm/backends/__init__.py` to return headless/noop backend; then `herdr workspace delete <id>` for orphans. |
+| `--cwd` wrong (repo not found) | Ensure `herdr workspace create --cwd <repo-root>` uses `find_repo_root` result, not `cwd` when run from worktree. |
+| `pane run` fails with `pipe` | Swarm fixed by quoting waiting message: `echo "Waiting..."` not `echo Waiting ... |` |
+| Shell mismatch (`bash` vs `zsh`) | Swarm now uses `_user_shell()`; verify Herdr panes inherit `$SHELL`. `herdr pane run --command "/usr/bin/zsh -lc 'echo \$SHELL'"` |
+
+### 5. Reuse tabs for new requests
+
+Do not delete the workspace between tasks. Reuse the same `run-id`:
+
+```bash
+agent-toolkit swarm handoff create --type artifact --from implementer --to reviewer --artifact artifacts/next-task.md --run-id <run-id>
+# Herdr tabs stay; only the handoff chain retriggers. New run only for isolated branch.
+```
+
+Attach when needed:
+
+```bash
+agent-toolkit swarm attach --run-id <run-id>
+herdr workspace focus --workspace swarm-<run-id>
+```
+
+## Boundaries
+
+- Never write Herdr's workspace DB directly; use `herdr workspace/tab/pane` CLI via swarm's `HerdrBackend`.
+- Never mix Herdr and tmux sockets — swarm uses `herdr` OR isolated `tmux -L agent-toolkit-swarm-<run-id>`, never both for one run.
+- Do not run `herdr workspace open` (removed); use `workspace focus` / `workspace list`.
+
+## Delegates to
+
+| Need | Skill |
+|------|-------|
+| Launch or reuse a swarm | `swarm` |
+| Diagnose stuck handoffs/logs | `swarm-observer` |
+| Create file handoffs | `swarm-handoff` |
+| Isolated fallback when Herdr unavailable | `tmux` (via `swarm --ui tmux`) |

agent_toolkit/data/skills/tooling/inventory/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: inventory
+description: Discover installed skills, agents, loops, and platform capabilities via agent-toolkit inventory,
+  matrix, and skills list.
+origin:
+  type: first-party
+metadata:
+  author: ulises-jeremias
+  version: '1.0'
+  tags:
+  - inventory
+  - matrix
+  - catalog
+  - discovery
+---
+# Inventory
+
+Discover what the toolkit can do before you build — **skills, agents, loops, MCP, and platform support** — via `agent-toolkit inventory`, `matrix`, `build --check`, and `skills list`.
+
+## When to use
+
+- User asks "what can agent-toolkit do?", "what skills are available?", or "is there a skill for X".
+- Before starting delivery: check which workflow (`delivery/*`), forge (`github-cli-workflow`), or ops (`swarm`) skills apply.
+- After `agent-toolkit install` — verify what was deployed and what needs `mcp setup`.
+- Before running `build` or `plugin` — understand target support via `matrix`.
+
+## Workflow
+
+### 1. List everything
+
+```bash
+agent-toolkit inventory              # skills (61), agents (16), loops (10), products
+agent-toolkit matrix                 # platform capability matrix (claude-code, cursor, opencode, etc.)
+agent-toolkit skills list            # grouped by domain (core, ops, forge, etc.)
+agent-toolkit skills list --domain ops  # filter
+agent-toolkit loops --help 2>&1 | head
+```
+
+`inventory` now shows 61 skills across 9 domains including the new swarm family:
+- `ops/swarm`, `ops/swarm-observer`, `ops/swarm-handoff`, `tooling/herdr`, `forge/worktree`, `core/workspace`, `core/project`, `integrations/mcp`, `tooling/inventory`.
+
+### 2. Inspect a skill or agent
+
+```bash
+agent-toolkit skills validate        # all 61 should be ✓
+muse skills validate ~/.ai-workspace/.agents/skills/swarm --json | jq .valid
+cat skills/ops/swarm/SKILL.md | head -n 20
+cat agents/code-reviewer/AGENT.md | head -n 20
+ls plugins/  # agent-toolkit-core, agent-toolkit-forge, etc. — each maps skills+agents to targets
+```
+
+### 3. Check readiness before delivery
+
+```bash
+agent-toolkit doctor
+agent-toolkit mcp doctor
+agent-toolkit swarm doctor           # herdr/tmux + runner model profiles
+agent-toolkit build --check          # validate compilation without writing plugins/
+```
+
+### 4. After adding skills
+
+```bash
+# After creating skills/<domain>/<id>/SKILL.md and data/skills/<domain>/<id>/SKILL.md:
+python3 scripts/generate-catalogs.py          # regenerate skill-catalog.yaml
+bash scripts/prepare-package-data.sh         # sync skills/catalogs to data/
+# Then update installed data if testing locally:
+cp catalogs/skills-layout.json packages/pypi/agent-toolkit-cli/src/agent_toolkit/data/catalogs/
+cp -r skills/ops/swarm packages/pypi/agent-toolkit-cli/src/agent_toolkit/data/skills/ops/
+agent-toolkit skills validate                # should show 61
+agent-toolkit skills list --domain ops       # should include new skill
+agent-toolkit install --dry-run | grep "Would deploy"
+```
+
+## Delegates to
+
+| Need | Skill |
+|------|-------|
+| Use a discovered skill | `assistant` (discovery), `swarm` (orchestration), `workspace` (context) |
+| Install or sync to a tool | `mcp` (providers), `herdr` (UI) |
+| Build error after inventory | `build-error-resolver` agent |

agent_toolkit/data/skills/tooling/jupyter-notebook/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

agent_toolkit/data/skills/tooling/jupyter-notebook/NOTICE.txt

@@ -0,0 +1,27 @@
+jupyter-notebook (agent-toolkit distribution)
+=======================================
+
+This skill is derived from the OpenAI "skills" repository, originally licensed
+under the Apache License 2.0:
+
+  https://github.com/openai/skills (skills/.curated/jupyter-notebook)
+
+Modifications by agent-toolkit S.A. for distribution via agent-toolkit:
+
+- Replaced `CODEX_HOME` / `~/.codex/skills/jupyter-notebook/...` paths with the
+  chezmoi-managed install location
+  (`~/.local/share/agent-toolkit/skills/jupyter-notebook/`).
+- Added the `agent-toolkit` (via jupyter-notebook skill) wrapper script at `~/.local/bin/dots-newnotebook`
+  that delegates to the bundled `scripts/new_notebook.py`.
+- Removed the `agents/openai.yaml` manifest in favor of the agent-toolkit
+  `skill.json` schema.
+- Dropped vendor logo assets (`assets/jupyter*`); kept the two notebook
+  templates (`experiment-template.ipynb`, `tutorial-template.ipynb`).
+- Updated `references/notebook-structure.md` to reference the agent-toolkit install
+  path instead of `$CODEX_HOME`.
+
+`scripts/new_notebook.py` and the four reference markdown files are preserved.
+The helper script is self-contained — it discovers its skill directory via
+`Path(__file__).resolve().parents[1]` and uses only the Python standard library.
+
+Original LICENSE.txt is preserved in this directory.

agent_toolkit/data/skills/tooling/jupyter-notebook/SKILL.md

@@ -0,0 +1,145 @@
+---
+name: jupyter-notebook
+description: Create, scaffold, or refactor Jupyter notebooks (.ipynb) for experiments and tutorials. Prefer
+  the bundled templates and the helper script (`new_notebook.py`, also exposed as `newnotebook`) to generate
+  a clean starting notebook instead of authoring raw notebook JSON.
+origin:
+  type: first-party
+---
+# Jupyter Notebook
+
+Create clean, reproducible Jupyter notebooks for two primary modes:
+
+- **Experiments** — exploratory analysis, ablations, hypothesis testing.
+- **Tutorials** — instructional walkthroughs, teaching-oriented notebooks.
+
+Prefer the bundled templates and the helper script for consistent structure and
+fewer JSON mistakes.
+
+## When to use
+
+- Create a new `.ipynb` notebook from scratch.
+- Convert rough notes or scripts into a structured notebook.
+- Refactor an existing notebook to be more reproducible and skimmable.
+- Build experiments or tutorials that will be read or re-run by other people.
+
+## Decision tree
+
+- Exploratory / analytical / hypothesis-driven → `experiment`.
+- Instructional / step-by-step / audience-specific → `tutorial`.
+- Editing an existing notebook → treat as a refactor: preserve intent and
+  improve structure.
+
+## Prerequisites
+
+- `python3` (provided by `bootstrap`).
+- Optional: `uv` for local notebook execution and dependency isolation
+  (also from `bootstrap`).
+
+`skills check jupyter-notebook` validates `python3` is present.
+
+## Helper script
+
+The bundled scaffolder (`scripts/new_notebook.py`, stdlib only) loads a
+template, updates the title cell, and writes a notebook to `--out`. Two ways
+to invoke it:
+
+### Option A — `newnotebook` wrapper (recommended)
+
+`bootstrap` installs a tiny wrapper at `~/.local/bin/newnotebook` so
+the script is available without remembering its full path:
+
+```bash
+newnotebook --kind experiment \
+  --title "Compare prompt variants" \
+  --out output/jupyter-notebook/compare-prompt-variants.ipynb
+
+newnotebook --kind tutorial \
+  --title "Intro to embeddings" \
+  --out output/jupyter-notebook/intro-to-embeddings.ipynb
+```
+
+### Option B — call the script directly
+
+```bash
+python3 ~/.local/share/agent-toolkit/skills/jupyter-notebook/scripts/new_notebook.py \
+  --kind experiment \
+  --title "Compare prompt variants" \
+  --out output/jupyter-notebook/compare-prompt-variants.ipynb
+```
+
+If you prefer `uv` for a pinned interpreter:
+
+```bash
+uv run --python 3.12 python ~/.local/share/agent-toolkit/skills/jupyter-notebook/scripts/new_notebook.py \
+  --kind tutorial \
+  --title "Intro to embeddings"
+```
+
+The script uses **only the Python standard library** — no extra deps required.
+
+## Workflow
+
+1. **Lock the intent.** Pick `experiment` or `tutorial`. Capture the objective,
+   audience, and what "done" looks like.
+2. **Scaffold from the template** (use `newnotebook` or option B above).
+3. **Fill the notebook with small, runnable steps.** Keep each code cell
+   focused on one step. Add short markdown cells that explain purpose and
+   expected result. Avoid large, noisy outputs when a short summary works.
+4. **Apply the right pattern.** For experiments, follow
+   [`references/experiment-patterns.md`](references/experiment-patterns.md).
+   For tutorials,
+   [`references/tutorial-patterns.md`](references/tutorial-patterns.md).
+5. **Edit safely when working with existing notebooks.** Preserve structure;
+   avoid reordering cells unless it improves the top-to-bottom story. Prefer
+   targeted edits over full rewrites. If you must edit raw JSON, review
+   [`references/notebook-structure.md`](references/notebook-structure.md) first.
+6. **Validate the result.** Run the notebook top-to-bottom when the environment
+   allows. If execution is not possible, say so explicitly and call out how to
+   validate locally. Use the final pass checklist in
+   [`references/quality-checklist.md`](references/quality-checklist.md).
+
+## Templates and helper script
+
+- Templates live in `assets/experiment-template.ipynb` and
+  `assets/tutorial-template.ipynb` (chezmoi-managed, read-only — do not edit
+  in place; copy and modify).
+- The helper script loads a template, updates the title cell, and writes a
+  notebook.
+
+## Temp and output conventions
+
+- Use `tmp/jupyter-notebook/` for intermediate files; delete when done.
+- Write final artifacts under `output/jupyter-notebook/` when working in a
+  repository.
+- Use stable, descriptive filenames (e.g. `ablation-temperature.ipynb`).
+
+## Dependencies (install only when needed)
+
+Prefer `uv` for dependency management.
+
+Optional Python packages for local notebook execution:
+
+```bash
+uv pip install jupyterlab ipykernel
+```
+
+The bundled scaffold script needs no extra dependencies.
+
+## Boundaries
+
+- This skill **scaffolds and refactors** notebooks. It does not run them — for
+  execution, use Jupyter / VS Code / the user's preferred runtime.
+- Do not commit notebook outputs that contain secrets or large binary blobs;
+  clear outputs before staging when in doubt.
+
+## Reference map
+
+- [`references/experiment-patterns.md`](references/experiment-patterns.md) —
+  experiment structure and heuristics.
+- [`references/tutorial-patterns.md`](references/tutorial-patterns.md) —
+  tutorial structure and teaching flow.
+- [`references/notebook-structure.md`](references/notebook-structure.md) —
+  notebook JSON shape and safe editing rules.
+- [`references/quality-checklist.md`](references/quality-checklist.md) —
+  final validation checklist.

agent_toolkit/data/skills/tooling/jupyter-notebook/assets/experiment-template.ipynb

@@ -0,0 +1,117 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "id": "7fb27b941602401d91542211134fc71a",
+   "metadata": {},
+   "source": [
+    "# Experiment: TITLE\n",
+    "\n",
+    "Objective:\n",
+    "- State the question you want to answer.\n",
+    "- Define the success criteria.\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "acae54e37e7d407bbb7b55eff062a284",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# Setup: imports and reproducibility\n",
+    "from __future__ import annotations\n",
+    "\n",
+    "import random\n",
+    "import statistics\n",
+    "\n",
+    "SEED = 7\n",
+    "random.seed(SEED)\n",
+    "SEED"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "9a63283cbaf04dbcab1f6479b197f3a8",
+   "metadata": {},
+   "source": [
+    "## Plan\n",
+    "\n",
+    "- Hypothesis:\n",
+    "- Variables to sweep:\n",
+    "- Metrics to record:\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "8dd0d8092fe74a7c96281538738b07e2",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# Define parameters and lightweight helpers\n",
+    "sample_size = 20\n",
+    "values = [random.random() for _ in range(sample_size)]\n",
+    "summary = {\n",
+    "    \"count\": len(values),\n",
+    "    \"mean\": statistics.fmean(values),\n",
+    "    \"min\": min(values),\n",
+    "    \"max\": max(values),\n",
+    "}\n",
+    "summary"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "72eea5119410473aa328ad9291626812",
+   "metadata": {},
+   "source": [
+    "## Results\n",
+    "\n",
+    "- Key observations:\n",
+    "- Surprises or failure modes:\n",
+    "- Decision: continue, pivot, or stop:\n"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "8edb47106e1a46a883d545849b8ab81b",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "# Record findings in a minimal, copy-pasteable structure\n",
+    "result = {\n",
+    "    \"seed\": SEED,\n",
+    "    \"mean\": summary[\"mean\"],\n",
+    "    \"range\": summary[\"max\"] - summary[\"min\"],\n",
+    "}\n",
+    "result"
+   ]
+  },
+  {
+   "cell_type": "markdown",
+   "id": "10185d26023b46108eb7d9f57d49d2b3",
+   "metadata": {},
+   "source": [
+    "## Next steps\n",
+    "\n",
+    "- What to try next:\n",
+    "- What to document elsewhere (PRD, notes, issue):\n"
+   ]
+  }
+ ],
+ "metadata": {
+  "kernelspec": {
+   "display_name": "Python 3",
+   "language": "python",
+   "name": "python3"
+  },
+  "language_info": {
+   "name": "python",
+   "version": "3.12"
+  }
+ },
+ "nbformat": 4,
+ "nbformat_minor": 5
+}