research.notebook.viz

Builds experiment logs and lab notebooks into MkDocs Material HTML sites with Chart.js time-series charts.

Updated May 9, 2026
One-click install
npx skills add https://github.com/0h-n0/auto-research --skill research-notebook-viz-0h-n0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research.notebook.viz
Source: https://github.com/0h-n0/auto-research/tree/main/skills/research.notebook.viz
Command: npx skills add https://github.com/0h-n0/auto-research --skill research-notebook-viz-0h-n0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mkdocs-material, chart.js, uv, jq, and includes references (resource) components.

What problem does it solve? Research projects accumulate dozens of markdown artifacts—experiment logs, lab notebooks, postmortems, paper drafts—that are hard to navigate as plain text: loss curves stay invisible in JSONL files, 100+ notebook entries cannot be reverse-looked-up by tag, and phase progress is not visible at a glance. This Skill converts those artifacts into a browsable static HTML site while keeping the original markdown files untouched as the source of truth. ## Core Features & Use Cases - MkDocs Material site generation: Auto-generates mkdocs.yml, copies and transforms source MD files into viz-src/docs/, and builds a static site with search, dark mode, and tag-based reverse lookup via uvx (no fixed installation). - Chart.js time-series visualization: Parses events.jsonl to render loss curves and metric charts on per-run pages, plus a Phase 1-8 progress bar injected from STATE.json into every page header. - Sortable tables and tag inversion: Converts run indexes, survey matrices, and results tables into sortable HTML tables, and transforms lab notebook Tags into mkdocs frontmatter for automatic tag index pages. - Use Case: After completing several experiment runs in an LLM research project, invoke the skill to produce .research/<slug>/viz/index.html, open it in a browser, and navigate brief, survey, ideas, runs, postmortems, results, and paper draft sections with full-text search. ## Quick Start Run /auto-research:notebook-viz <slug> to build the HTML research notebook for your project, optionally adding --serve to preview it at localhost:8000.

Frequently Asked Questions about research.notebook.viz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize machine learning experiment logs as HTML?▼

Run the notebook-viz command with your project slug to build a static MkDocs Material site from your experiment logs. It parses events.jsonl into Chart.js loss and metric curves, renders run tables, and outputs everything to .research/<slug>/viz/index.html.

How to render JSONL training metrics as time-series charts?▼

The build pipeline extracts step, loss, and eval.metric events from events.jsonl using jq, embeds them as JSON in canvas data attributes, and renders them with Chart.js line charts on each per-run page. Both loss curves and multi-metric charts are generated automatically.

Does MkDocs Material require permanent installation for site builds?▼

No, this skill uses uvx to run mkdocs-material on demand without a fixed installation. The first build takes about 30 seconds to install into the uv cache, and subsequent builds reuse the cache in roughly 3 seconds.

Can I view the generated research notebook offline?▼

The built site opens via file:// and works offline for navigation and search, but Chart.js is loaded from a CDN so charts require network access. A vendored offline mode for Chart.js is planned for a later version.

Why does the notebook visualization build fail with a STATE.json error?▼

The build requires STATE.json to render the phase progress bar, so it fails if the research project was never initialized. Run the research-start command first to create the project structure under .research/<slug>/ before building the visualization.

Does building the HTML site modify my original markdown files?▼

No, source markdown files are strictly read-only. All transformations happen on copies inside viz-src/docs/, and the final viz/ directory is a regenerable artifact that can be safely deleted or rebuilt at any time.