review-ml-choices
Skill145 starsChanged 7 days agoBSD-3-ClauseView on GitHub
Show stored project choices and re-enter the skill that can change one. Trigger when the user asks what we decided, what the current settings are, or to change a stored project choice.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- probabl-ai/skillsword for word, first seen Nov 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- probabl-ai/skills★ 145100% 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-projectSkill
- export-ml-siteSkill
- frame-ml-problemSkill
- manage-ml-backlogSkill
- model-ml-pipelineSkill
- persist-ml-gitSkill
- plot-ml-figureSkill
- research-ml-practiceSkill
- 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
7 rules. About 0 are common, 1 is distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Run python -m skore_skills review choices.
- Very specific: line 53
Do not policy set. Do not run the child's commands from memory.
- Very specific: line 72
Do not policy set any key.
- Very specific: line 73
Do not edit JOURNAL, including a Data understanding skipped row.
- Very specific: line 75
Do not load sync-ml-reports when policy.skore_mode is unset.
- Very specific: line 77
Do not env add-skore, git commit, or scaffold src/.
- Distinctive: line 78
If the owning skill is not installed, show the value and skip the change in one line.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Review ML Choices
Show stored choices. A change loads the skill that already owns
that decision. Do not write .skore or the journal from here.
Human-facing prose
Details: setup-workspace references/human_facing_prose.md.
The board uses data-science labels: where reports go, executed
notebooks, documentation site, git commits, who manages the
environment, data analysis, and each filled framing cell
(prediction goal, deployment, metric, fold count, and the
others below). Do not put skill
ids, G-* names, or the wrapper CLI in the question.
Sequence
- Run
python -m skore_skills review choices. The JSON is the board. Do not rebuild which rows are offered. Do not runframe showorframe clearhere. AskUserQuestion, one pick. Say first, in 2–4 lines, what a change authorizes — re-entering that setup, not a silent flag flip — and echo the current values from the JSON. A file link is an addition, never the context.
Options are Keep these plus one option per
changeablerow and one option perframingrow.read_onlyandnot_offeredare context, not options. Use each row'svalue. Fornot_offered, say that row'sreason. Whenframing_reasonis set, say it and do not offer framing rows. "Who manages the environment" is whether this project manages it (policy.env.managed). An installed skill is not that value. Do not write a skill id on the board.- Keep these → stop. Do not load a skill.
One
changeablerow → load that row'sskilland stop. The close names the decision being re-opened, not the skill id. Do notpolicy set. Do not run the child's commands from memory.skore_mode→ the user asked to change where reports go.notebooks_site→ notebooks and the documentation site.git_autocommit→ the user asked to change that choice.env_managed→ do not runenv add-skorehere. If the recorded destination ishubormlflow, do not use--mode local.data_analysiswhenactionisrerun→ do not write a JOURNALskippedrow. The written analysis stays; the change is to run it again.
- One
framingrow → loadframe-ml-problemnaming that row'sid. Do not blank the cell here. - A request to change a
read_onlyrow: say that row'sreasonand stop. Do not loadsetup-workspaceto rename. Do notpolicy set.
Stop conditions
- Do not
policy setany key. - Do not edit JOURNAL, including a Data understanding
skippedrow. - Do not load
sync-ml-reportswhenpolicy.skore_modeis unset. - Do not
env add-skore,git commit, or scaffoldsrc/. - If the owning skill is not installed, show the value and skip the change in one line. Do not invent that skill's steps.
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
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.

