notebook-to-agilab-project

Convert local notebooks into an AGILAB project with lab_stages.toml.

19|2|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/ThalesGroup/agilab --skill notebook-to-agilab-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notebook-to-agilab-project
Source: https://github.com/ThalesGroup/agilab/tree/main/.claude/skills/notebook-to-agilab-project
Command: npx skills add https://github.com/ThalesGroup/agilab --skill notebook-to-agilab-project

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps researchers and engineers convert local notebooks into a reproducible AGILAB project, ensuring that exploratory work can be handed off as portable, artifact-backed workflows.

Core Features & Use Cases

  • Migrates a small set of notebooks (2-6) into an AGILAB project, exposing ANALYSIS notebooks and enabling WORKFLOW imports.
  • Generates lab_stages.toml and an artifact contract to capture run evidence and reproducible results.
  • Produces a conceptual workflow view to communicate the project trajectory and analytics.

Quick Start

Import your local notebooks and run the migration to generate a reproducible AGILAB project with an artifact contract and a lab_stages.toml.

Frequently Asked Questions about notebook-to-agilab-project

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

FAQPage Schema
How do I convert local notebooks into a reproducible analytics workflow?

To convert local notebooks into a reproducible analytics workflow, migrate 2-6 notebooks into an AGILAB project. This process exposes ANALYSIS notebooks and generates a lab_stages.toml file to capture stable run evidence.

What is an artifact contract in notebook migration?

An artifact contract in notebook migration is a generated configuration that satisfies workflow import and export requirements. It captures run evidence to ensure your analytics results remain reproducible across different AGILAB environments.

Can I migrate more than six notebooks into an AGILAB project?

Migrating more than six notebooks into an AGILAB project is not the intended use case. This notebook migration skill specifically applies to small sets of 2-6 local notebooks to ensure proper artifact contract generation and workflow exposure.

How does lab_stages.toml work for notebook reproducibility?

The lab_stages.toml file works for notebook reproducibility by defining the conceptual workflow view of your project trajectory. It structures the migrated analytics stages so imported workflows produce stable run evidence.

What is the best way to hand off exploratory notebook analytics?

The best way to hand off exploratory notebook analytics is converting them into a portable AGILAB project. This replaces scattered local notebooks with artifact-backed workflows, ensuring reproducible results for downstream engineers.