ov-layers/skills/notebook-templates/SKILL.md
Starter notebook templates provisioned into the workspace volume at deploy time. First data-only layer in the project — no packages, no services, no dependencies. Use when working with notebook-templates, data layers, or jupyter initial content.
npx skillsauth add overthinkos/overthink-plugins notebook-templatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | (none) |
| Packages | (none) |
| Services | (none) |
| Volumes | workspace -> ~/workspace |
| Data | data/notebooks -> workspace volume |
| Install files | (none) |
This is a data layer — the first of its kind in the project. It uses the data: field in layer.yml to map a directory of files to a named volume:
info: "Starter notebook templates for jupyter"
data:
- src: data/notebooks
volume: workspace
At build time, the contents of data/notebooks/ are staged into /data/workspace/ inside the image.
At deploy time, when the volume is configured as a bind mount (ov config --bind workspace), ov config copies the staged data from the image into the host-backed volume directory. This seeds the volume with starter content (e.g., getting-started.ipynb).
| File | Purpose |
|------|---------|
| getting-started.ipynb | Starter notebook for new jupyter deployments |
# image.yml
jupyter:
layers:
- notebook-templates
# ... other layers
# Deploy with bind-backed workspace volume
ov config jupyter --bind workspace
# Data is copied from image to host volume on first config
ov start jupyter
/ov-images:jupyter/ov-images:jupyter-ml/ov-images:jupyter-ml-notebook/ov:layer -- data field documentation and layer authoring rules/ov:config -- data provisioning during ov config setup/ov:deploy -- volume backing configuration (bind, named, encrypted)/ov-layers:jupyter -- the JupyterLab layer that consumes the workspace volume/ov-images:jupyter -- the image that includes this layerUse when the user asks about:
data: field in layer.ymlgetting-started.ipynb notebookov config seeds bind-backed volumes with image data/ov:test — declarative testing (tests: block, ov image test, ov test)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.