CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

physics-fitting

Nonlinear curve fitting for physics data with proper error propagation, chi-squared analysis, residual diagnostics, confidence intervals, and model comparison (AIC/BIC). Use for any parameter extraction from experimental or simulation data.

69

Quality

87%

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

82%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 high-quality, code-first skill body: fully executable workflows covering the core physics-fitting tasks, effective pitfall/interpretation tables, and clear scoping via a 'Do NOT Use When' section. The main gaps are a missing explicit validation feedback loop in the fitting workflow, some trimmable plotting boilerplate, and no use of reference files despite a length that would benefit from them.

Suggestions

Embed an explicit validation gate in the fit workflow, e.g. 'if chi2_red is far from 1, try multiple initial guesses (p0) or lmfit bounds before reporting parameters'.

Trim the plotting boilerplate (full figure/residual-plot setup, unused t_dist import) or move it to a references/plotting.md to keep the core workflows lean.

Consider splitting the model-comparison and error-propagation utilities into a references/ file so SKILL.md stays a lean overview with well-signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The body is mostly lean: terse comments, no re-teaching of concepts Claude already knows, and code that earns its tokens. Minor trimmable material exists — the full plotting boilerplate (subplots, labels, gridspec) and an unused 'from scipy.stats import t as t_dist' import — placing it between 'mostly efficient' (3) and 'lean and efficient, every token earns its place' (5), noticeably above the midpoint.

4 / 5

Actionability

All four workflows (scipy curve_fit, lmfit with bounds and confidence intervals, AIC/BIC model comparison, Jacobian-based error propagation) are complete, executable, copy-paste-ready Python with realistic sample data. The code covers the common cases end-to-end, matching the top anchor.

5 / 5

Workflow Clarity

The workflows are clearly sequenced (fit, extract parameters with uncertainties, compute chi-squared/ndof, compare models) and the Goodness-of-Fit table and Common Pitfalls table supply interpretation and error-recovery guidance. However, no explicit validate-then-proceed gate or retry loop is woven into the steps (e.g. 'if chi2_red is far from 1, re-fit with different p0'), so it falls short of the anchor requiring explicit validation steps and feedback loops.

4 / 5

Progressive Disclosure

The single file is well-organized into clear sections (When to Use, Do NOT Use When, four workflows, reference tables) with no nested or buried references, and cross-references to sibling skills are clearly signposted. But at ~230 lines with no bundle files, content like the full plotting/confidence-band block would fit naturally in a references/ file, so structure is good with minor organization gaps rather than an ideal split.

4 / 5

Total

17

/

20

Passed

Description

88%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: specific, multi-action capability list with an explicit use-when clause. Main weaknesses are a slightly over-broad trigger phrase ('any parameter extraction') that could conflict with adjacent statistics/ML skills, and missing common synonyms like 'least squares' or 'regression' that users would naturally say.

Suggestions

Add natural trigger synonyms users would actually say, e.g. 'least squares', 'regression', 'fit a model/curve to data', 'error bars'.

Narrow the 'when' clause from 'any parameter extraction' to something like 'when fitting models to experimental or simulation data with uncertainties', reducing overlap with generic regression or ML hyperparameter-tuning skills.

Consider naming the primary tools (scipy/lmfit) or a typical phrasing like 'extract physical constants' to sharpen distinctiveness.

DimensionReasoningScore

Specificity

The description lists six concrete, specific actions ('nonlinear curve fitting', 'error propagation, chi-squared analysis, residual diagnostics, confidence intervals, and model comparison (AIC/BIC)') with comprehensive coverage of the skill's capabilities. This matches the anchor for multiple specific concrete actions; there are no coverage gaps that would justify a 4.

5 / 5

Completeness

It clearly answers 'what' (the enumerated action list) and explicitly answers 'when' with 'Use for any parameter extraction from experimental or simulation data.' Both are explicit, matching the top anchor; a 4 would require the 'when' to be only weakly specified, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('curve fitting', 'chi-squared', 'error propagation', 'AIC/BIC', 'parameter extraction', 'experimental or simulation data') but common user phrasings like 'least squares', 'regression', 'fit a model to data', and 'error bars' are missing. This sits between 'some relevant keywords' (3) and 'comprehensive coverage of natural terms including synonyms' (5), noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

'Nonlinear curve fitting for physics data' carves a clear niche, but the trigger 'any parameter extraction' is broad and risks overlap with generic regression, statistics, or ML skills. Mostly distinct with minor overlap risk against closely related skills — anchor 4 rather than 5 because of the over-broad trigger.

4 / 5

Total

18

/

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

Path

backend/cli/skills/physics/physics-fitting/SKILL.md

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.