Export Ml Site

Organization

probabl-ai

export-ml-site

Package workspace markdown and existing notebook HTML into an offline MkDocs site. Embeds existing notebook HTML companions in their associated reports. Never executes Python. Trigger when the user asks for a website, mkdocs, or documentation site.

Overview

Publisher	probabl-ai
Repository	`skore-skills`
Skill name	`export-ml-site`
Stars	144
Forks	9
Bundled files	1
License	BSD-3-Clause
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by probabl-ai on GitHub. Read the source before you install it.

Installation

Install the Export Ml Site AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/probabl-ai/skore-skills/tree/main/skills/export-ml-site
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/probabl-ai/skore-skills.git /tmp/skore-skills
mkdir -p .claude/skills
cp -r /tmp/skore-skills/skills/export-ml-site .claude/skills/export-ml-site

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Export Ml Site in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Export Ml Site on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Export Ml Site is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Export ML Site

Human-facing prose

Details: setup-workspace references/human_facing_prose.md. Tell the user the website has been updated and paste the file:// line from that output verbatim, so a click opens the browser. Do not describe the line. Do not link a workspace-relative path. Do not say double-click or "no server". Do not name the markdown file that was edited. Do not quote site init / site build as something they should run.

The site is a derived index of files other skills already write. The staged docs mirror the workspace folders (journal/, data_analysis/, experiments/, audit/, scratch/results/), so a relative link written between two source files also works on the site. MkDocs warns about a link it cannot resolve and site build prints that warning: fix the link, do not hide the warning. Markdown is the report: its figures are shown inline and an HTML file it refers to by name is pasted into the page when it is a fragment (TableReport html_snippet()). A whole HTML document (Plotly) sits in a fixed-height iframe with an open-separately link. Existing converted notebooks (<stem>.nb.html, written only by export-ml-notebook with notebook convert --html) are links that open a page of their own. Each experiment design note has one ## Notebooks section: evaluation first, then audit. The audit notebook is audit/<stem>.nb.html from notebook convert --html. A missing file is omitted. Do not use . Derived HTML and PNG files under scratch/results/<stem>/ (checks, metrics, plus extra Display slugs) may be copied into the staged docs. Core Results headings are Report overview / Checks / Metrics. ### Report overview is prose only: the skore report (report.html) is not published. checks.html and metrics.html are pasted into the page under their headings; the scores are that table, not a second markdown table. Extra slugs use  under ## Results or ## Method. pipeline is the graph image pipeline.svg shown on the page plus a link to the DataOp report pipeline/index.html. Only Markdown and already-generated notebook/HTML files are exported. The gitignored serialized Skore reports/ directory is private runtime state and is never copied into the site. On desktop, site pages are in the top bar (experiments in a scrollable dropdown) and the page contents are in a collapsible left rail beside a 1200px report column. Mobile uses a drawer.

Workflow stages publish at completed checkpoints, after their Python execution and final durable Markdown batch and before the next user decision. They call site build --if-stale: unchanged inputs skip MkDocs. This is coalescing, not a file-save hook; do not build between related Markdown edits. Only policy.site true enables these automatic builds. null and false do not change policy. A direct user request to rebuild uses site build without --if-stale.

Lookup

Run status and read policy.site. Take the first row that matches. site build writes the site. Do not stop after reading the table.

`policy.site`	Turn	Then
`null`	direct request	step 2: persist `true`, install `mkdocs-material`, `site init`, then build
`false`	direct request	step 3. Do not init or build until it is `true`.
`true`	direct request, and `site build` reports `mkdocs-material is required`	load `add-python-package` for `mkdocs-material`, then build once more. Do not `site init` again.
`true`	direct request, first site turn	step 4 `site init`, then step 5 `site build`
`true`	direct request, later turn (`site init` already ran)	step 5 `site build` only. Do not `site init`.
`true`	workflow checkpoint, not a direct request to build	`site build --if-stale` (preview section, including its one retry). Unchanged inputs skip MkDocs.

Sequence

python -m skore_skills status. Read policy.site.
If policy.site is null: persist python -m skore_skills policy set site true. Do not AskUserQuestion. Then load add-python-package for mkdocs-material (agent) then python -m skore_skills site init. Continue to build.
If policy.site is false: say the documentation site is off; offer to turn it on. Do not init or build until it is true.
If this is the first site turn, run site init (gitignore only). Later turns only site build.
python -m skore_skills site build. Do not run notebook convert. If site build errors with mkdocs-material is required, load add-python-package for mkdocs-material (agent) and build once more. Do not pixi add / uv add. If that skill is missing, or the retry still fails, name the error in one line. Name a build error; the markdown sources remain the record. Do not claim the website was updated. When the build succeeds, tell the user the website has been updated and paste the file:// line from that output verbatim. Do not say double-click or "no server". Do not name the markdown file or a stage page (html/data_analysis/data_analysis.html, html/journal/<stem>.html). Stage owners that just ran site build say that same line in the User-facing close.

Preview before markdown-review gates

Stage owners that just wrote durable markdown and will ask the user to approve or continue must rebuild the site before that AskUserQuestion / consent stop — not only at End of turn.

If policy.site is true and this skill is installed, run python -m skore_skills site build --if-stale. Skip in one line otherwise. If site build errors with mkdocs-material is required, load add-python-package for mkdocs-material (agent) and build once more. Do not pixi add / uv add. If that skill is missing, or the retry still fails, name the error in one line. Name a build error; do not fail the gate.
In the same message as the gate, when the build ran or reported the site current: the website has been updated, and paste the file:// line from that output verbatim. Do not name the .md path or the stage page. A file link is an addition, never the context. If the build failed, name the error in one line and do not claim the website was updated.
Do not notebook convert, git end-turn, or git commit on this preview rebuild. Do not re-run site init.
Close-time conversion and build remain a freshness safety gate. Current notebooks and site inputs skip execution/build; changed or missing outputs are refreshed.

Stop conditions

Do not assemble the site by hand. site build writes the site.
Do not git commit or git end-turn.
Do not pixi add / uv add; load add-python-package.
Do not convert or execute # %% scripts.
Do not copy or link serialized files from gitignored reports/.
Skip in one line if this skill is not installed.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

evals/evals.json10 KB

Frequently asked questions

What does the Export Ml Site AI skill do?

Why use Export Ml Site on TypingMind?

Because you install it once and use it with any model. Export Ml Site is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Export Ml Site in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/probabl-ai/skore-skills/tree/main/skills/export-ml-site. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Export Ml Site?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Export Ml Site?

As many as you like. As long as a model supports skills, you can use Export Ml Site with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Export Ml Site AI skill free?

Yes. It is published on GitHub by probabl-ai under the BSD-3-Clause license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mono Color

NousResearch

OrganizationPopular

Generate one- or two-ink editorial print poster images.

Pretext

Build creative browser demos with DOM-free text layout.

Sketch

Throwaway HTML mockups: 2-3 design variants to compare.

Tldraw Offline

Drive and script tldraw offline canvases with an agent.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Export ML Site

Human-facing prose

Lookup

Sequence

Preview before markdown-review gates

Stop conditions

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now