CtrlK
BlogDocsLog inGet started
Tessl Logo

dimensional-analysis

Automated dimensional analysis — Buckingham Pi theorem, non-dimensionalization, unit validation with pint, and characteristic scale estimation. Use before any physics computation to verify consistency and reduce parameter space.

60

Quality

71%

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/dimensional-analysis/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.

A solid, executable reference with genuine worked examples and clear per-workflow organization, held back by inline reference tables that belong in separate files, a non-functional non-dimensionalization example, and padding that restates known physics.

Suggestions

Replace the hardcoded print statements in the Non-dimensionalization section with an actual executable invocation of `nondimensionalize` on a real sympy equation.

Move the Fundamental Dimensions and Common Dimensionless Numbers tables into a references/ file (e.g., references/tables.md) and link to them from SKILL.md to reduce inline tokens.

Trim the print-scaffolding in `buckingham_pi` (dimension-matrix echo, verbose formatting) and cut the Fundamental Dimensions table, which restates knowledge Claude already has.

DimensionReasoningScore

Conciseness

Mostly code-driven but padded in places: the Navier–Stokes section prints hardcoded strings instead of executing the `nondimensionalize` function, examples carry verbose print scaffolding, and the "Quick Reference: Fundamental Dimensions" table (M/L/T/s/kg…) restates physics knowledge Claude already has.

3 / 5

Actionability

Four of five workflows (`buckingham_pi`, pint validation, `dimensionless_numbers`, `check_dimensions`) are real, executable code with worked examples; the gap is that `nondimensionalize` is defined but never invoked, and its example only prints precomputed text.

4 / 5

Workflow Clarity

Five clearly delineated, self-contained workflows with error-handling demonstrated ("except pint.DimensionalityError"), a When-to-Use section, and interpretive thresholds (Re < 2300 laminar). Minor gaps: no guidance on choosing among workflows and no validation in the non-dimensionalization workflow.

4 / 5

Progressive Disclosure

All content lives inline in one ~300-line file with no bundle files; the two dimensionless-numbers reference tables and extended examples belong in separate reference files, though section headers keep it navigable.

3 / 5

Total

14

/

20

Passed

Description

78%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 strong description: concrete capabilities with a named library and an explicit use-before trigger clause. Main improvement is adding more specific trigger phrases and surfacing the dimensionless-numbers capability.

DimensionReasoningScore

Specificity

Lists four concrete named actions ("Buckingham Pi theorem, non-dimensionalization, unit validation with pint, and characteristic scale estimation") including a specific library, but omits computing dimensionless numbers, a workflow covered in the body — a minor coverage gap that keeps it below the comprehensive anchor.

4 / 5

Completeness

The "what" is explicit (first sentence lists the capabilities) and a "when" clause is present ("Use before any physics computation to verify consistency and reduce parameter space"), but the trigger surface is a single broad condition rather than concrete trigger phrases like "when the user mentions X", so it fits the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

Contains natural domain keywords a user would say ("dimensional analysis", "Buckingham Pi", "unit validation", "pint", "physics computation") but misses common variations like "check units", "SI units", or "dimensionless groups".

4 / 5

Distinctiveness Conflict Risk

Highly niche technique vocabulary (Buckingham Pi, non-dimensionalization, characteristic scales) carves out a clear trigger niche with essentially no overlap risk against other skills.

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.

Validation — 15 / 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.