marimo-notebook

To define marimo notebooks as Python files, add a YAML frontmatter block with name and description, then use marimo's @app.cell decorators for reactive cell definitions. This structure enforces canonical notebook authoring and reproducible setups.

The best way to structure reproducible marimo notebooks is using a SKILL.md entry with required frontmatter, Python cell definitions, and optional directories like scripts/, references/, and assets/ to extend functionality and documentation across projects.

Yes, you can use YAML frontmatter to validate and discover marimo notebook skills. Placing the frontmatter at the SKILL.md entry requires a name and description, enabling frontmatter-driven validation for your Python notebook files.

You set up optional directories like scripts, references, and assets by including them alongside your Python file to extend notebook behavior. These directories integrate additional scripts, documentation, and assets into your structured marimo project.

Marimo notebook authoring requires using @app.cell decorators for cell definitions to establish reactive dependencies. This structured approach ensures reactive cells execute correctly and maintain cell dependencies within your Python file.

Your marimo notebook needs a SKILL.md frontmatter entry to standardize Python file authoring and prevent structural errors. It enforces required name and description fields, providing a canonical pattern for defining reproducible notebooks.