probabl-ai/skore-skills

shape-user-idea

Shape a user idea or a named artifact into one idea file and one Ideas row after they confirm.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/probabl-ai/skore-skills --skill shape-user-idea

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Shape User Idea

Comes after review, beside the backlog. The user already has an idea, a question, or an artifact. This skill writes journal/ideas/<slug>.md and one Ideas row only after they confirm. The backlog triages that file later.

Human-facing prose

Details: setup-workspace references/human_facing_prose.md. Questions and the confirmation paragraph describe this idea in data-science terms — not skill ids or the wrapper CLI.

Procedure

  1. Run python -m skore_skills status. Read journal/JOURNAL.md

Status and History, and data_analysis/data_analysis.md when it exists.

  1. If the entry is not already a concrete idea, question, or

artifact, AskUserQuestion: free-text or artifact. A URL, issue, path, or stated idea skips that menu.

  1. A question about this project is answered from those files.

Leave an unknown metric as n/a. Write no idea file and return to the caller.

  1. A topic with no artifact ("what do people do for …") loads

search-ml-literature only if status.skills.search-ml-literature is true. Otherwise one-line skip. Do not WebSearch for a paper from here.

  1. An artifact is read, not reconstructed. Paper or doc URL:

WebFetch the page. GitHub issue: gh auth status first; if unauthenticated, ask the user to run gh auth login or paste the body. Then gh issue view. Resolution: explicit URL, then org/repo#N, then bare #N only in the current gh repo — otherwise ask. Spec or notes file: read that file only.

  1. Walk three questions. Do not fabricate a missing answer.
  • What are we trying to learn?
  • Why now? Quote the user or the artifact.
  • What changes versus the last experiment, in prose?
  1. If the idea changes the project goal in journal/JOURNAL.md

Status, ask before writing the file. A library the source names and the user has not agreed to add stays in Open gaps. A domain claim this dataset does not establish stays in Open gaps.

  1. Restate the idea in one short paragraph, then one

single-choice AskUserQuestion: Yes / No. Do not also ask for a typed yes. Put that question in the message before any idea file. "Maybe" is not Yes. No or Stop writes nothing. A Yes from the tool, or an explicit yes the user already gave, authorizes the write only after that question is in the message.

  1. On Yes, write journal/ideas/<slug>.md and upsert its Ideas

row. Do not create a design note. Do not edit History, Backlog, or Status. Write journal/ideas/<slug>.md:

# <slug>
- Experiment: <last History stem, or n/a>
- Source: user
- Triage: open
- Question:
- Why now:
- What changes:
- Open gaps:

Why now carries the quote, URL, or path. No acceptance criteria. Then upsert one ## Ideas row: Question as plain text, Status open, Experiment <last History stem, or n/a>, Source user. If that table is missing, insert it between History and Backlog. Do not rewrite the other sections. Return the path to the caller (manage-ml-backlog or triage-ml-task).

Stop conditions

  • Do not write History, Backlog, Status, or a design note.

The Ideas table is the only JOURNAL.md edit.

  • Do not append a B<N> row. The backlog triages the file.
  • Do not invent source content from a title.
  • Do not WebSearch for a topic with no artifact.
  • The entry question and the Yes / No confirmation are

required gates.

  • If the user already asked to add a named library, put it in

What changes and load add-python-package when that skill is installed. Do not pixi add from here.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
probabl-ai
Comunidade

plot-ml-figure

Pick pandas, seaborn, plotly, or matplotlib before writing figure code. Trigger when explore-ml-data, evaluate-ml-pipeline, or audit-ml-pipeline is about to save or display a chart, or when the user asks for a plot. Not a session owner. Not for skore/sklearn Display plots that already exist on a report. HOW TO USE: first match on the tree (owned plot, interactive iframe HTML, seaborn statistical, pandas chart, else matplotlib). In a notebook: save PNG (or HTML) then leave the figure as the cell

Instalações / 1h
1
GitHub Stars
145
Atualizado
9 de nov.
probabl-ai
Comunidade

setup-git

Initialize safe version control, including an optional commit of the tree before setup changes it. Trigger when the user asks to initialize version control, add ignore rules, or make the first commit. This action owns first-time git setup only. Before the first commit, ask once which unknown hidden files and review paths to keep tracked. When loaded for the pre-change snapshot, commit the current tree before other setup writes, then return.

Instalações / 1h
1
GitHub Stars
145
Atualizado
9 de nov.
probabl-ai
Comunidade

audit-ml-pipeline

Audit a persisted skore report read-only and produce a reusable digest. Do not execute it. Run materialize.py once. Never call skore.evaluate or project.put. TRIGGER when a completed run needs an audit, the user asks to audit, show, or re-audit an experiment, a re-run overwrote the same put() key, or they want a narrative of a past experiment without journal/ideas/ files. STOP when status.setup.pending is non-empty (load setup-ml-project), or when there is no approved design, no report, or no ag

Instalações / 1h
1
GitHub Stars
142
Atualizado
20 de out.
probabl-ai
Comunidade

choose-python-library

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.

Instalações / 1h
1
GitHub Stars
142
Atualizado
20 de out.