probabl-aiprobabl-ai/skore-skills/skills/export-ml-project/SKILL.md

export-ml-project

Skill144 starsChanged 17 days agoBSD-3-ClauseView on GitHub

Coordinate executed notebooks and an offline MkDocs documentation site. Trigger on a generic "export" request, or to flip the notebooks/site gates after setup.

1 other project uses a version of this.

Adopted by

Most recently taken up by

probabl-ai/skillsword for word, first seen Oct 27, 2026

Other versions1 project uses a version of this.
Word for word · 1
probabl-ai/skills★ 144100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-python-packageSkill
- audit-ml-pipelineSkill
- build-ml-pipelineSkill
- choose-python-librarySkill
- evaluate-ml-pipelineSkill
- explore-ml-dataSkill
- export-ml-notebookSkill
- export-ml-siteSkill
- frame-ml-problemSkill
- manage-ml-backlogSkill
- model-ml-pipelineSkill
- persist-ml-gitSkill
- plot-ml-figureSkill
- research-ml-practiceSkill
- review-ml-choicesSkill
- review-ml-experimentSkill
- search-ml-literatureSkill
- setup-gitSkill
- setup-ml-projectSkill
- setup-python-envSkill
- setup-workspaceSkill
- shape-user-ideaSkill
- smoke-test-ml-pipelineSkill
- sync-ml-reportsSkill
- triage-ml-taskSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
After the answer, and not in the question, persist each box this turn: selected → python -m skore_skills policy set notebooks true (or …
line 38
Distinctive:
Do not git end-turn or git commit.
line 58
Very specific:
Do not invent convert or mkdocs steps when the child skill is missing.
line 59
Very specific:
Do not pixi add / uv add from this coordinator.
line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Export ML Project

Ordering only. Children own convert and site commands.

Human-facing prose

Details: setup-workspace references/human_facing_prose.md. The multi-select uses Executed notebooks and Documentation site. Do not put skill ids, convert flags, or the wrapper CLI in the question.

Sequence

python -m skore_skills status. Read policy.notebooks, policy.site, and skills.
AskUserQuestion with allow_multiple. Say first, in 2–4 lines, what each box authorizes (toolchain installs, convert re-execution, a built site), the recorded flags (policy.notebooks and policy.site: true, false, or not recorded), and that both answers persist as policy. A file link is an addition, never the context. The question's last line is exactly: Select each one you want. Write nothing after that line.
- Executed notebooks
- Documentation site
After the answer, and not in the question, persist each box this turn: selected → python -m skore_skills policy set notebooks true (or site); a box the user does not select → false. Do not leave them null. Do not write notebooks or site into JOURNAL; policy is the record.
Load each selected child only if status.skills.<id> is true; else one-line skip. Do not invent that skill's steps:
- notebooks → export-ml-notebook (installs toolchain if this is the first yes, then convert; --html only if the user wants the notebook viewer on the site)
- site → export-ml-site (installs mkdocs-material if first yes, init if needed, then build; never convert)
Load triage-ml-task only if status.skills.triage-ml-task is true; else stop.

Stop conditions

Do not git end-turn or git commit.
Do not invent convert or mkdocs steps when the child skill is missing.
Do not pixi add / uv add from this coordinator.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free