agentleFS
probabl-aiprobabl-ai/skore-skills/skills/choose-python-library/SKILL.md

choose-python-library

Skill144 starsChanged 17 days agoBSD-3-ClauseView on GitHub

Resolve a library choice and add the selected dependency. Trigger for competing-library questions or an optional package not already fixed by the project stack — at first use (tabular exploration, pipeline, or eval extras), never during workspace setup.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Do not name skill ids or the wrapper CLI in the question.

    line 19
  2. Very specific:

    Run python -m skore_skills env stack.

    line 22
  3. Very specific:

    After the user chooses, load add-python-package when status.skills reports it installed.

    line 29
  4. Distinctive:

    Do not install every candidate.

    line 43
  5. Distinctive:

    Do not use popularity alone as a technical decision.

    line 44
  6. Distinctive:

    Do not run pip directly in a managed project.

    line 45
  7. Distinctive:

    Do not substitute black/isort for Ruff or sklearn Pipeline for skrub DataOps.

    line 46
  8. Very specific:

    Do not present matplotlib vs seaborn vs plotly.

    line 48

≈ “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

Choose Python Library

Human-facing prose

Details: setup-workspace references/human_facing_prose.md. Present library options as a data-science choice for this job. Do not name skill ids or the wrapper CLI in the question.

  1. State the job and constraints.
  2. Run python -m skore_skills env stack. A job listed under competing is a genuine choice; anything the policy already fixes (mandatory, stage, export) is settled — use it rather than reopening the choice. Do not read the packaged JSON file directly; it lives inside the installed package.
  3. For a genuine choice, present the smallest useful option set and ask the user. Do not pick silently.
  4. After the user chooses, load add-python-package when status.skills reports it installed. If it is not installed, name the package and stop. Do not call env add from this skill. Typical callers: explore-ml-data (pandas vs polars), later extras (tuning). Not setup-workspace. Plotting jobs: load plot-ml-figure if installed; do not present matplotlib vs seaborn vs plotly.
  5. Confirm symbols with python -m skore_skills api get <dotted>... before writing calls. Several symbols go in one call. Scope for one package is python -m skore_skills env route <pkg>, not a guess.

Stop conditions

  • Do not install every candidate.
  • Do not use popularity alone as a technical decision.
  • Do not run pip directly in a managed project.
  • Do not substitute black/isort for Ruff or sklearn Pipeline for skrub DataOps; those choices are already fixed.
  • Do not present matplotlib vs seaborn vs plotly; that job is plot-ml-figure.

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.