CtrlK
BlogDocsLog inGet started
Tessl Logo

statistical-mechanics

Monte Carlo simulation for statistical mechanics — Ising model, Metropolis-Hastings, Wolff cluster algorithm, observables (magnetization, susceptibility, specific heat), finite-size scaling, and critical phenomena analysis.

65

Quality

78%

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/statistical-mechanics/SKILL.md
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 strong, executable skill body with well-structured workflows and concrete code throughout. The main gap is the absence of explicit validation/feedback-loop checkpoints for batch simulation runs, and inline reference material that could be split into separate files.

Suggestions

Add explicit validation checkpoints to batch workflows (e.g. 'verify <|M|> is in [0,1] and C >= 0 before recording; if not, extend equilibration'), with a fix-and-retry loop.

Move the critical-exponents table and extended algorithm notes into a references/ file, signaled from SKILL.md, to improve progressive disclosure.

Tighten a few inline comments that restate what the code already shows.

DimensionReasoningScore

Conciseness

Mostly lean and code-forward with minimal padding; only minor over-explanation remains (e.g. restating 'Wolff cluster flip (much faster near T_c)' and a few inline comments that assume little), so it sits above the midpoint but not fully lean.

4 / 5

Actionability

Fully executable, copy-paste-ready Python covering the common cases (Metropolis/Wolff sweeps, temperature sweep, finite-size scaling, autocorrelation), with concrete observables and plotting code.

5 / 5

Workflow Clarity

Four clearly sequenced workflows with implicit validation (equilibration vs measurement separation, autocorrelation/error estimation, T_c cross-check against Onsager), but no explicit validation checkpoints or fix-retry feedback loops for the batch operations.

4 / 5

Progressive Disclosure

Well-organized sections (Overview, When to Use, Core Workflows, exponents, troubleshooting) with no nested references and a single self-contained body; minor gap only because bulk reference material (exponent tables, API details) is inline rather than split out.

4 / 5

Total

17

/

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.

The description is highly specific and distinctive, naming concrete algorithms and observables, but it lacks any explicit 'Use when...' trigger guidance, which the rubric caps at completeness 3. Adding a concrete trigger clause would raise the overall score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when simulating spin systems, locating critical temperatures, or doing finite-size scaling of phase transitions.'

Add a couple of natural synonym phrases users might say (e.g. 'phase transition', 'critical exponents', 'Monte Carlo spin simulations') to broaden trigger coverage.

Keep the third-person voice (currently correct) while adding the 'Use when' guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and algorithms (Ising model, Metropolis-Hastings, Wolff cluster, finite-size scaling, critical phenomena analysis) with named observables, matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no explicit 'when'/'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural domain terms (Monte Carlo, Ising model, phase transition, critical phenomena) but lacks common synonym variations or file/format markers that users might say; a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (statistical-mechanics Monte Carlo) with distinct, specialized triggers (Ising, Metropolis-Hastings, Wolff, finite-size scaling) that are unlikely to fire for unrelated 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.

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.