iterate-from-skore

Converts skore audit digest findings into ML experiment backlog candidates.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/probabl-ai/ibm-workshop --skill iterate-from-skore-probabl-ai
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: iterate-from-skore
Source: https://github.com/probabl-ai/ibm-workshop/tree/main/.bob/skills/iterate-from-skore
Command: npx skills add https://github.com/probabl-ai/ibm-workshop --skill iterate-from-skore-probabl-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an ML experiment is audited, the diagnostic findings sit in a report without a clear path to action. This Skill reads the audit digest and turns each flagged check into a concrete, deduplicated backlog row so the next experiment idea comes from evidence rather than guesswork. ## Core Features & Use Cases - Digest-driven sourcing: Reads scratch/audit/<stem>/audit.md as text and converts every issue or tip row in the ## Checks summary into one backlog candidate, without re-opening the skore Project. - Documentation-grounded mitigations: Follows each check's documentation_url via WebFetch so the proposed experiment idea reflects the official skore remediation guidance rather than model memory. - Deduplication and safe fallbacks: Drops candidates whose audit:<stem>:checks.<code> citation already exists in JOURNAL.md, and returns an explicit empty result when the digest is clean or unreadable. - Use Case: After the 01_baseline classifier audit flags an SKD003 check, ask the agent to mine the report; it returns backlog rows citing the check plus a one-paragraph summary, and the parent skill writes them into the journal for you to promote via B<N>. ## Quick Start Ask the agent to mine the latest skore audit digest and fill the experiment backlog from its diagnostic findings.

Frequently Asked Questions about iterate-from-skore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn skore audit findings into next experiment ideas?ā–¼

Read the audit digest's Checks summary section and create one backlog row per check with severity issue or tip, deriving the experiment idea from the check's documentation_url. This Skill automates that loop and returns the rows to the parent iterate-ml-experiment skill.

How do I mine an ML experiment report for a backlog?ā–¼

Point the skill at the digest produced by audit-ml-pipeline at scratch/audit/<stem>/audit.md. It reads the file as text, fetches each flagged check's skore documentation page, and emits deduplicated backlog candidates with audit:<stem>:checks.<code> citations.

Does this skill re-run the skore report or open the Project?ā–¼

No. It only reads the pre-rendered audit digest as text and never calls project.get or report accessors. If the digest is missing, recovery is delegated to audit-ml-pipeline, which re-executes the audit runner.

What happens when the audit digest has no issues or tips?ā–¼

The skill returns zero candidate rows and a summary stating the report looks clean on the checks surface. The parent skill notes this in JOURNAL.md and the user picks a different sourcing strategy such as iterate-from-user.

How are duplicate backlog findings avoided?ā–¼

Each candidate carries a Source citation in the form audit:<stem>:checks.<code>. Before emitting rows, the skill reads the existing JOURNAL.md backlog and drops any candidate whose citation already appears, reporting the number of dropped duplicates.

When should I use iterate-from-user instead of mining the skore report?ā–¼

Use iterate-from-user when you already have a concrete modelling idea from an article, resource, or free text. Mining the skore digest fits when the previous experiment finished and you want its diagnostic checks converted into actionable backlog items.