iterate-from-user
Source the next ML experiment proposal from the user via one of three entry points selected by `AskUserQuestion`: (a) a scientific article URL the agent must read and synthesize, (b) a resource link or path (GitHub issue / spec file / reference repo), or (c) free-text the user types directly. In every branch, the agent reads the source, synthesizes its understanding of what to implement, and confirms with the user *before* returning the Proposal block. Hand the confirmed Proposal back to `iterate-ml-experiment`, which writes it into `journal/NN_short_name.md` and seeks the user's design-note approval. Stops at "Proposal returned, user-confirmed"; never writes a design note, never authors acceptance criteria. TRIGGER when: `iterate-ml-experiment` is picking a sourcing strategy and the user picks `user` from the menu; the user volunteers a concrete idea ("I want to try X"); the user pastes or links a scientific article, GitHub issue, spec file, or reference repo and asks us to read it. S
probabl-ai · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add probabl-ai/skills --skill iterate-from-user技能说明
name: iterate-from-user
description: >
Source the next ML experiment proposal from the user via one of
three entry points selected by AskUserQuestion:
(a) a scientific article URL the agent must read and synthesize,
(b) a resource link or path (GitHub issue / spec file / reference
repo), or (c) free-text the user types directly. In every branch,
the agent reads the source, synthesizes its understanding of what
to implement, and confirms with the user before returning the
Proposal block. Hand the confirmed Proposal back to
iterate-ml-experiment, which writes it into
journal/NN_short_name.md and seeks the user's design-note approval.
Stops at "Proposal returned, user-confirmed"; never writes a
design note, never authors acceptance criteria.
TRIGGER when: iterate-ml-experiment is picking a sourcing
strategy and the user picks user from the menu; the user
volunteers a concrete idea ("I want to try X"); the user pastes
or links a scientific article, GitHub issue, spec file, or
reference repo and asks us to read it.
SKIP when: the user wants to mine the previous report (use
iterate-from-skore); the user is asking for a symbol lookup or
pipeline mechanics (use the python-api skill); the work is
evaluation mechanics on a single report (route to
evaluate-ml-pipeline).
HOW TO USE: open with an AskUserQuestion for the entry point —
article-link / resource-link / free-text. In each branch: gather
the source material with the appropriate tool (WebFetch,
gh issue view, Read), synthesize what you understand into the
three shaping questions, and confirm with the user via plain
text (one or two sentences: "you'd like to implement X by
changing src//.py — right?") before returning the
Proposal. Do not write any design note. Do not author acceptance
criteria.
Iterate from user
Source: the user — directly, or via something they've pointed at
(article, issue, spec, repo). Output: a user-confirmed Proposal
block, handed back to iterate-ml-experiment.
Output contract (read this before the body)
This skill never writes journal/ files and never authors
acceptance criteria. It returns a single Proposal block as
conversation text (full shape in § What is returned at the bottom):
Question, Motivation (with Source field — quote, URL, or path),
Method outline, Open gaps. Required, in every branch:
- All three shaping questions are answered (see § The three shaping questions).
- The synthesis confirmation gate has fired and the user has said yes (see § Confirm before returning).
Sourcefield is concrete: the user's quote, the article URL with the exact claim, thegh issuelink, or the spec-file path with line numbers.
There is no "no proposal" outcome: this skill only fires when
the user has picked user from the parent's sourcing menu. If they
have nothing in hand, the parent's menu re-presents itself.
Stop conditions
- Don't write
journal/files. That belongs toiterate-ml-experiment. This skill returns the Proposal as conversation text; the parent skill drafts the file. - Don't infer source content from memory. If the user references an article, an issue, or a file, fetch / read it. Don't reconstruct from a title or a one-line description.
- Confirm before returning. The Proposal goes back to the parent only after the user has explicitly said "yes, that's what I want." Free-text "hmm" / "maybe" / "interesting" is not confirmation. See § Confirm before returning.
- Check
ghauth before fetching anything from GitHub. Before anygh issue view/gh apicall, rungh auth status(cheap, cached). If unauthenticated, ask the user to rungh auth loginthemselves (suggest! gh auth loginin the prompt) or paste the issue body directly. A failedghcall surfaces a confusing error; the auth check makes the failure mode explicit. - Flag goal shifts before returning. If the user's idea (or
the source) materially changes the project goal as recorded
in
JOURNAL.mdStatus — different output shape (point estimate → prediction interval), different downstream consumer (offline batch → online serving), different metric class (squared error → coverage) — surface it as a question before returning the Proposal: "this would update JOURNAL.md Status from to ; confirm or amend the goal first?" The parent's per-experiment design note should not silently redefine success while the Status block still reflects the old goal. - New dependencies are gated, not assumed. If the proposal
requires a library outside the project's existing env
(e.g. an article uses
lightgbm/pytorch/jax), do not silently include it inMethod outlineas a fait accompli. Flag it as an open gap ("this approach needs <library>; OK to add, or should we adapt to the existing stack?") and defer the resolution todata-science-python-stack+ the user. - Domain-specific assertions need user confirmation. If the
source asserts something the article / issue / spec alone can't
establish for our dataset — e.g. "feature X is monotone in the
target," "interaction Y matters for this asset class," "metric Z
is right because the use case is one-sided" — list each
assertion in
Open gapsand ask the user before returning. Don't ship paper-flavored guesses as facts. - Harness-level "no clarifying questions" instructions do not
apply to this skill's confirmation gates. The entry-point
AskUserQuestion(article-link / resource-link / free-text) and the § "Confirm before returning" synthesis gate are operating-contract gates, not clarifying questions. They fire regardless of any harness-level hint. The synthesis gate in particular is non-skippable even when the user's intent feels "obvious" — the cost of the agent's restatement missing