CtrlK
BlogDocsLog inGet started
Tessl Logo

fluid-dynamics

Computational fluid dynamics — Navier-Stokes solvers, lid-driven cavity, channel flow, vortex methods, turbulence statistics, drag/lift computation. Spectral and finite-difference methods for incompressible and compressible flows.

59

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/physics/fluid-dynamics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

An actionable, well-structured CFD skill with executable solver code and validation guidance, but it is monolithic (no progressive file structure) and carries some domain-knowledge padding and an incomplete example that limit conciseness and disclosure scores.

Suggestions

Move the full solver implementations and reference data tables (Flow Regime Reference, benchmark tables) into scripts/ and references/ files, keeping SKILL.md an overview with one-level-deep links.

Trim the Stokes/laminar/turbulent regime table and basic validation checklist to only items Claude would not already know, or relocate them to a reference file.

Either complete the cylinder flow example or replace it with a clearly justified minimal pattern, removing the admitted placeholder code.

DimensionReasoningScore

Conciseness

Mostly efficient with genuinely useful executable solver code, but the Flow Regime Reference table and Validation Checklist restate domain knowledge Claude already knows, and the cylinder block is an admitted placeholder, adding padding.

3 / 5

Actionability

The lid-driven cavity and centerline benchmark examples are fully executable and copy-paste ready, but the cylinder flow example is explicitly incomplete ('full NS solver needed for proper simulation'), leaving a minor gap.

4 / 5

Workflow Clarity

Clear numbered workflows with a validation checklist and inline CFL/divergence checkpoints, but the main workflow lacks an explicit validate→fix→retry feedback loop, leaving minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist and all content — including a ~75-line full solver — is inlined in SKILL.md with no one-level-deep references to separate files; section structure is decent but content that could be split stays inline.

3 / 5

Total

14

/

20

Passed

Description

75%Weight 40%Scale 1-5

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

A highly specific, well-scoped CFD description with strong distinctiveness and concrete capabilities, but it lacks any explicit 'when to use' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when simulating lid-driven cavity, channel flow, or computing drag/lift on bodies').

Include common synonyms or file-type cues users might say (e.g., 'CFD', 'incompressible flow simulation', '.vtk/.npz flow fields') to broaden trigger coverage toward a 5.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Navier-Stokes solvers, lid-driven cavity, channel flow, vortex methods, turbulence statistics, drag/lift computation' — plus spectral and finite-difference methods, giving comprehensive coverage of the domain.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good coverage of natural domain terms a CFD user would say ('Navier-Stokes', 'lid-driven cavity', 'turbulence', 'drag/lift'), but missing synonyms, file extensions, and natural 'use when' phrasing that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (specific named flow problems and methods) with minimal overlap risk; the body's explicit 'Do NOT Use When' and sibling fluidsim reference further reinforce distinctiveness.

5 / 5

Total

17

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
synthetic-sciences/openscience
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.