search-ml-literature
Skill145 starsChanged 7 days agoBSD-3-ClauseView on GitHub
Search scientific and technical sources and write one idea file and one Ideas row for the direction the user confirms. Comes after review, beside the backlog. Do not call research-ml-practice. Do not write History, Backlog, or a design note. Do not pick a winner.
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-choicesSkill
- review-ml-experimentSkill
- 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
11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Run python -m skore_skills status.
- Distinctive: line 35
Search scientific and technical sources.
- Very specific: line 39
Write scratch/research/direction-<slug>.md when that write can run.
- Distinctive: line 46
If this turn is not already an explicit yes, restate the picked direction in one short paragraph, then one single-choice AskUserQuestion: …
- Very specific: line 55
Do not edit History, Backlog, or Status.
- Very specific: line 80
Do not load research-ml-practice.
- Very specific: line 81
Do not write History, Backlog, Status, or a design note.
- Very specific: line 83
Do not append a B<N> row.
- Distinctive: line 84
Do not search a dataset proper name, a loader, or a Kaggle slug.
- Very specific: line 85
Do not add a package or run env add / pixi add.
- Distinctive: line 86
Do not treat one blog as ground truth.
≈ “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
Search ML Literature
Comes after review, beside the backlog. Source is a query, not an
artifact the user already named. Show a few directions, then write
one journal/ideas/<slug>.md and one Ideas row for the direction
they confirm. manage-ml-backlog triages that file later.
Human-facing prose
Details: setup-workspace references/human_facing_prose.md.
Directions and the pick question are scientific options for this
project — not skill ids or the wrapper CLI.
Procedure
- Run
python -m skore_skills status. Readjournal/JOURNAL.mdStatus, the last History headline, and the EDA summary whendata_analysis/data_analysis.mdexists. If the query is too vague to search, ask once. - Rewrite the query as a problem class before any search. Drop
dataset names, loader names (
sklearn.datasets,fetch_*), and Kaggle slugs. JOURNAL and EDA are context for that rewrite, not search strings. - Search scientific and technical sources. Fetch the primary pages. When sources disagree, say so. Do not fill a gap from memory after a search has run. If search cannot run, say so and stop. Do not invent papers, URLs, or claims.
- Write
scratch/research/direction-<slug>.mdwhen that write can run. Do not paste it into chat. - Show two to four directions. Each one: a one-line idea, why it might transfer here, what it would change, and the URL plus the claim. Do not rank a winner.
- AskUserQuestion: pick one, narrow the query, or stop. Narrow restarts at step 2. Stop writes no idea file.
- If this turn is not already an explicit yes, restate the picked direction in one short paragraph, then one single-choice AskUserQuestion: Yes / No. Do not also ask for a typed yes. Until Yes, that paragraph and the question are the whole message. "Maybe" is not Yes. No or Stop writes nothing.
- On Yes — the tool answer, or an explicit yes already given
on this or a later turn — write
journal/ideas/<slug>.mdand upsert its Ideas row. Do not create a design note. Do not edit History, Backlog, or Status. Writejournal/ideas/<slug>.md:
# <slug>
- Experiment: <last History stem, or n/a>
- Source: literature: <url>
- Triage: open
- Question:
- Why now:
- What changes:
- Open gaps:Open gaps hold transfer risks, disagreements, and domain
claims this dataset does not establish. A library named only
by a source stays in Open gaps until the user asks to add it.
Then upsert one ## Ideas row: Question as plain text, Status
open, Experiment <last History stem, or n/a>, Source
literature: <url>. If that table is missing, insert it
between History and Backlog. Do not rewrite the other
sections. Return the path to the caller.
Stop conditions
- Do not load
research-ml-practice. - Do not write History, Backlog, Status, or a design note.
The Ideas table is the only
JOURNAL.mdedit. - Do not append a
B<N>row. - Do not search a dataset proper name, a loader, or a Kaggle slug.
- Do not add a package or run
env add/pixi add. - Do not treat one blog as ground truth.
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.

