CtrlK
BlogDocsLog inGet started
Tessl Logo

chemical-storage-sorter

Sort laboratory chemicals into safe storage groups by hazard classification (acids, bases, oxidizers, flammables, toxics). Identifies incompatible pairs, generates storage plans with warnings, and supports OSHA/NFPA compliance for lab safety.

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 ./scientific-skills/Other/chemical-storage-sorter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 highly actionable skill body with executable, verified code examples and a clear CLI surface. It is held back by verbosity/redundancy (triple-stated capabilities, duplicate storage tables) and a missing explicit output-validation checkpoint for what is a batch, safety-relevant operation.

Suggestions

Remove the redundant 'Key Capabilities' bullet list and one of the two storage-requirement tables; keep a single consolidated table to cut tokens.

Tighten 'Common Pitfalls' to terse, skill-specific rules rather than general lab-safety education Claude already knows.

Add an explicit output-validation step to the Workflow (e.g. 'Review the generated plan: confirm every incompatible pair flagged a warning and multi-hazard chemicals landed in the most restrictive group') to lift workflow clarity above the batch-operation cap.

DimensionReasoningScore

Conciseness

Mostly efficient and task-relevant, but it restates the description in the intro, repeats it again as a 'Key Capabilities' bullet list, and includes two overlapping storage-requirement tables (Core Capabilities and 'Storage Requirements by Group'). The 'Common Pitfalls' section also explains safety concepts Claude already knows. It is not a 4 because the redundancy and preachy pitfalls could be trimmed without losing clarity.

3 / 5

Actionability

Code examples are fully executable and copy-paste ready — `from scripts.main import ChemicalStorageSorter`, `sorter.classify_chemical(...)`, `sorter.check_compatibility(...)` — and the methods match the bundled `scripts/main.py`. Concrete CLI commands and a parameters table cover the common cases (sort, compatibility check, list groups).

5 / 5

Workflow Clarity

A clear 5-step Workflow with a Quick Check (`py_compile`, `--help`), an input-validation step, and an Error Handling fallback is present, but this is a batch operation and there is no explicit checkpoint validating the generated storage plan for safety/correctness. Per the rubric's batch-operation cap, implicit-only validation holds this at 3 rather than 4.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a real one-level-deep reference to `scripts/main.py` (verified present) plus external reference URLs. Not a 5 because content that could be consolidated — the duplicated storage-requirement tables and the somewhat tangential 'Common Pitfalls' — is inlined, leaving minor organization gaps.

4 / 5

Total

15

/

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 specific, well-scoped description with concrete actions and a distinct niche, written in correct third-person voice. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. 'Use when sorting or segregating laboratory chemicals for safe storage, or when checking whether two chemicals are compatible to store together.'

Add a couple of plainer synonyms ('chemical storage', 'segregate chemicals') alongside the regulatory terms to broaden natural keyword coverage.

Optionally mention accepted input forms (chemical names or CAS numbers) in the description so users know what to provide.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Sort laboratory chemicals into safe storage groups', 'Identifies incompatible pairs', 'generates storage plans with warnings', 'supports OSHA/NFPA compliance' — with the hazard groups enumerated, giving comprehensive coverage. Third-person voice ('Sort', 'Identifies', 'generates') is used throughout with no first/second person.

5 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3. The 'when' is only weakly implied by the task framing.

3 / 5

Trigger Term Quality

Natural terms a lab user would say are present ('laboratory chemicals', 'safe storage groups', 'incompatible pairs', 'storage plans', 'lab safety'), but it leans slightly technical ('hazard classification', 'OSHA/NFPA compliance') and omits a few plainer synonyms. Not a 5 because common informal phrasings like 'chemical storage' or 'segregate chemicals' are not explicitly surfaced.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — sorting laboratory chemicals into safe storage groups by hazard classification — with distinct triggers and minimal overlap risk against other skills. The specificity of 'laboratory chemicals' and 'storage groups' makes misfiring unlikely.

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
aipoch/medical-research-skills
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.