CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lab-prep-calculations

Perform pre-experiment calculations and generate step-by-step preparation protocols for dilutions, solution preparation, dissolution, and % concentrations when planning formulations and lab prep workflows.

Quality

74%

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 ./scientific-skills/Other/Lab-Prep-Calculations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The domain-specific core (When to Use, Key Features, the worked NaCl example, and Implementation Details) is genuinely strong — concrete, correct, and well-validated. However, the file is padded with ~10 generic boilerplate sections that restate default assistant behavior, roughly doubling token cost without adding skill-specific value, which is the primary quality problem.

Suggestions

Delete or collapse the generic filler sections ("When Not to Use", "Required Inputs", "Recommended Workflow", "Deterministic Output Rules", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Completion Checklist", "Quick Validation", "Scope Reminder") into a few lines, keeping only the lab-specific validation rules (V1 ≤ V2, purity correction, equipment-range checks) that are already in Implementation Details.

Add a short worked serial-dilution example (e.g., factoring a 1:1000 dilution into three 1:10 steps with aliquot and solvent volumes) to match the concreteness of the dilution example.

Surface the bundle references in a dedicated short section (e.g., "## References") with link syntax so navigation to guide.md and the output template is immediate.

DimensionReasoningScore

Conciseness

Roughly the bottom half of the body ("When Not to Use", "Required Inputs", "Recommended Workflow", "Deterministic Output Rules", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Completion Checklist", "Quick Validation", "Scope Reminder") is generic template boilerplate that restates behavior Claude already applies by default and adds no lab-prep-specific value; the "Quick Validation" code block literally just says "No local script validation step is required for this skill." This matches the level-2 anchor of several padded, unnecessary sections, and is below level 3 because the padding is not incidental but constitutes the majority of the file's line count.

2 / 5

Actionability

The body gives an excellent fully worked, copy-paste-style example (unit conversion to 1000 mM, V1 = 0.5 mL, solvent 49.5 mL, 5-step executable protocol with equipment list) plus explicit formulas (C1V1 = C2V2, m = C × V × MW, m_adj = m / purity) and concrete validation rules (V1 ≤ V2, step volumes within equipment ranges). It falls short of level 5 because serial dilution and percentage-concentration paths get method descriptions but no worked example or concrete numbers.

4 / 5

Workflow Clarity

There is a clear domain sequence — requirement confirmation (concentration, volume, MW, purity, constraints) → calculation path selection (dilution / serial / solid / percentage) → verification with explicit sanity checks — plus failure handling and a completion checklist, satisfying most checkpoints. It is not level 5 because the "Recommended Workflow" section is abstract filler ("Select the documented execution path and prefer the simplest supported command") rather than a concrete ordering tied to the actual calculation flow, and the serial-dilution path lacks a worked feedback example.

4 / 5

Progressive Disclosure

The body correctly pushes detail one level deep to real, existing files — "see `references/guide.md`" for the verification checklist and "`assets/lab_prep_calc_template.md`" for the reusable output template, both of which exist and are single-level references — while keeping formulas and the worked example inline. It stops short of level 5 because the references are only signaled deep inside "Implementation Details" rather than in a clear navigation section, and the inline boilerplate sections dilute what should be a lean overview.

4 / 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 that explicitly states both capabilities and a use-when trigger in third person, with concrete domain-specific actions. Its main weakness is trigger breadth: common user phrasings like "prepare a stock solution" or "calculate molarity" are not covered.

Suggestions

Add the most common user phrasings to the when-clause, e.g. "Use when preparing working solutions from stocks, planning serial dilutions, or calculating molarity/mass from molecular weight and purity".

Mention serial dilution and purity/molecular-weight corrections in the description since these are core documented features users would search for.

DimensionReasoningScore

Specificity

The description names several concrete actions — "Perform pre-experiment calculations and generate step-by-step preparation protocols" — across specific domains ("dilutions, solution preparation, dissolution, and % concentrations"), but omits capabilities documented in the body such as serial dilutions, purity correction, and unit normalization, leaving minor coverage gaps.

4 / 5

Completeness

Both "what" (perform pre-experiment calculations, generate step-by-step preparation protocols) and "when" ("when planning formulations and lab prep workflows") are explicitly answered, matching the level-4 anchor; the when-clause is a single condition and would be stronger if it also covered users asking to prepare or dilute a solution without mentioning "formulations".

4 / 5

Trigger Term Quality

Natural keywords like "dilutions", "solution preparation", "% concentrations", "formulations", and "lab prep" are present and would be said by users, but common variations such as "stock solution", "molarity", "serial dilution", "buffer prep", or "w/v" are missing.

4 / 5

Distinctiveness Conflict Risk

The lab-prep calculation niche (dilutions, dissolution, % concentrations for formulation planning) is clearly distinct from generic document, code, or data skills, and its triggers are unlikely to fire for the wrong skill.

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

aipoch/medical-research-skills

Path

scientific-skills/Other/Lab-Prep-Calculations/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.