CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/nbval-tests

Validate Jupyter notebooks via the `pytest --nbval` plugin - re-execute cells and compare outputs to stored results. Cover the strict path (output match required), `--nbval-lax` (failure-only), `--sanitize-with` for dynamic outputs, and per-cell controls (`#NBVAL_SKIP`, `#NBVAL_IGNORE_OUTPUT`, `#NBVAL_RAISES_EXCEPTION`). Use when a repo ships `.ipynb` files as tutorials, docs, or analyses that must keep producing the same outputs after a dependency upgrade or source change.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

The content is concise, fully actionable, and clearly sequenced with validation inherent in the test run and recovery guidance in the anti-patterns. As a single-file skill it is well-structured with no nested references.

DimensionReasoningScore

Conciseness

The body is lean: numbered steps, command blocks, a marker table, and a sanitize.cfg snippet with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands and config - 'pip install nbval pytest', 'pytest --nbval ...', a concrete sanitize.cfg, and a GitHub Actions YAML - with no pseudocode.

3 / 3

Workflow Clarity

A clear Step 1-7 sequence with the pytest run itself acting as the explicit validation checkpoint; the Anti-patterns table supplies error-recovery fixes (e.g. swap strict for lax, targeted regexes).

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clear sections with the only reference being a one-level external link to the nbval docs, appropriately signaled in a References section.

3 / 3

Total

12

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, clearly stating both capabilities and use conditions in third person. It is among the strongest examples in the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 're-execute cells and compare outputs to stored results', 'strict path (output match required)', '--nbval-lax', '--sanitize-with', and per-cell controls - matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (validate notebooks by re-executing and comparing outputs) and when via an explicit 'Use when a repo ships .ipynb files...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say - 'Jupyter notebooks', '.ipynb files', 'tutorials, docs, or analyses', 'dependency upgrade or source change' - with good coverage of common phrasings; voice is third person ('Validate').

3 / 3

Distinctiveness Conflict Risk

Niche is narrow and distinct (nbval notebook regression testing) with triggers tied to .ipynb tutorials/docs/analyses post-upgrade, making conflict with other skills unlikely.

3 / 3

Total

12

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents