overthinkos/notebook-templates
jupyter/skills/notebook-templates/SKILL.md
Starter notebook templates provisioned into the workspace volume at deploy time. First data-only candy in the project — no packages, no services, no dependencies. Use when working with notebook-templates, data candies, or jupyter initial content.
testing
Updated Jun 14, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins notebook-templatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 14, 2026, 5:59 AM141.7s1 file scanned
SKILL.md
- name:
- notebook-templates
- description:
- |
notebook-templates -- Starter notebook data candy
Candy Properties
| Property | Value |
|----------|-------|
| Dependencies | (none) |
| Packages | (none) |
| Services | (none) |
| Volumes | workspace -> /workspace |
| Data | data/notebooks -> workspace volume |
| Install files | (none) |
How It Works
This is a data candy — the first of its kind in the project. It uses the data: field in charly.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 box.
At deploy time, when the volume is configured as a bind mount (charly config --bind workspace), charly config copies the staged data from the box into the host-backed volume directory. This seeds the volume with starter content (e.g., getting-started.ipynb).
Included Data
| File | Purpose |
|------|---------|
| getting-started.ipynb | Starter notebook for new jupyter deployments |
Usage
# charly.yml
jupyter:
candy:
- notebook-templates
# ... other candies
# Deploy with bind-backed workspace volume
charly config jupyter --bind workspace
# Data is copied from image to host volume on first config
charly start jupyter
Used In Boxes
/charly-jupyter:jupyter/charly-jupyter:jupyter-ml/charly-jupyter:jupyter-ml-notebook
Related Skills
/charly-image:layer-- data field documentation and candy authoring rules/charly-core:charly-config-- data provisioning duringcharly configsetup/charly-core:deploy-- volume backing configuration (bind, named, encrypted)/charly-jupyter:jupyter-- the JupyterLab candy that consumes the workspace volume/charly-jupyter:jupyter-- the box that includes this candy
When to Use This Skill
Use when the user asks about:
- The notebook-templates candy or its contents
- Data candies and the
data:field incharly.yml - How starter content gets provisioned into volumes
- The
getting-started.ipynbnotebook - How
charly configseeds bind-backed volumes with box data
Related
/charly-check:check— declarative testing (check:block,charly check box,charly check live)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).
SKILL.mdUpdated Jun 14, 2026