marimo-reactive-review

Assess marimo notebooks for reactive model adherence and anti-patterns.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/t-uda/skills --skill marimo-reactive-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marimo-reactive-review
Source: https://github.com/t-uda/skills/tree/main/skills/marimo-reactive-review
Command: npx skills add https://github.com/t-uda/skills --skill marimo-reactive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps evaluate whether an existing marimo notebook adheres to marimo's reactive model, identifies anti-patterns, and proposes a concrete refactor plan without rewriting unless asked.

Core Features & Use Cases

  • Review notebooks for alignment with marimo's dependency model and reactive execution.
  • Identify non-reactive patterns, cross-cell mutations, and opportunities to separate setup, config, load, derive, compute, render, and export stages.
  • Provide actionable recommendations and a target architecture for future edits.

Quick Start

Provide the notebook you want reviewed to receive a structured, actionable marimo reactive assessment.

Frequently Asked Questions about marimo-reactive-review

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

FAQPage Schema
How do I review a marimo notebook for reactive execution anti-patterns?

A marimo reactive review evaluates your notebook's adherence to the reactive dependency model, identifying cross-cell mutations and non-reactive anti-patterns to produce a target architecture and prioritized refactor plan.

What is the best way to refactor a marimo notebook without rewriting code?

Refactoring a marimo notebook without rewriting code involves generating a prioritized refactor plan with clear guardrails, identifying anti-patterns, and proposing a target architecture while leaving the actual code untouched unless explicitly requested.

Can I use this reactive review to separate compute and render stages in a marimo notebook?

Yes, a marimo reactive review identifies opportunities to separate your notebook's setup, config, load, derive, compute, render, and export stages, ensuring proper alignment with marimo's reactive dependency model.

Why does my marimo notebook fail to execute cells reactively?

A marimo notebook fails to execute reactively due to cross-cell mutations and non-reactive anti-patterns, which a reactive review identifies by evaluating the notebook's setup, config, load, derive, compute, render, and export stages to propose a target architecture.

What are common marimo notebook anti-patterns to look for during a reactive review?

Common marimo notebook anti-patterns identified during a reactive review include cross-cell mutations, non-reactive execution patterns, and improper separation of setup, config, load, derive, compute, render, and export stages.