CtrlK
BlogDocsLog inGet started
Tessl Logo

working-with-marimo

Interactive development in marimo notebooks with validation loops. Use for creating/editing marimo notebooks and verifying execution.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, actionable, and structured around a clear Plan-Execute-Verify loop with explicit validation. Its only meaningful weakness is a broken reference to best_practices.md, which is not present in the bundle.

Suggestions

Add the missing reference/best_practices.md file (and a references/ directory) so the two inline links resolve, or remove the references if the guidance fits inline.

Consider a one-line example of the write/search_replace edit step so the Execute phase is as concrete as the Plan and Verify phases.

DimensionReasoningScore

Conciseness

The body is a lean list of concrete tool calls and brief rules with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Provides specific executable MCP tool names (e.g., mcp_marimo_lint_notebook) and concrete rules (mo.sql, plt.gca(), "No plt.show()"), giving copy-paste-ready guidance.

3 / 3

Workflow Clarity

The Plan-Execute-Verify loop is numbered and sequenced, with Verify marked "(CRITICAL)" and broken into lint, runtime, and output checks forming an explicit validation feedback loop.

3 / 3

Progressive Disclosure

The body is a clear overview signaling a one-level-deep reference (reference/best_practices.md), but that file does not exist in the bundle (no references/ directory), so navigation is broken and cannot reach a 3.

2 / 3

Total

11

/

12

Passed

Description

75%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and clearly answers both what the skill does and when to use it, with an explicit trigger clause and a distinctive niche. It is slightly held back by abstract phrasing and limited trigger-term variation.

DimensionReasoningScore

Specificity

Names the marimo domain and a few actions ("creating/editing marimo notebooks and verifying execution"), but "interactive development" and "validation loops" are abstract rather than a list of concrete actions, matching the score-2 anchor.

2 / 3

Completeness

States what it does ("Interactive development in marimo notebooks with validation loops") and explicitly when to use it ("Use for creating/editing marimo notebooks and verifying execution"), satisfying both what and when.

3 / 3

Trigger Term Quality

"marimo notebooks" is a natural user term, but "verifying execution" is technical phrasing and common variations are absent, fitting the score-2 anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

"marimo notebooks" is a narrow, distinctive niche with triggers unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
pymc-labs/CausalPy
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.