CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

co-tank-monitor

IoT monitoring simulation to predict CO2 tank depletion and prevent weekend gas outages in cell culture facilities. Monitors cylinder pressure, calculates consumption rates, provides early warnings, and supports automated scheduling via cron.

Quality

79%

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/co2-tank-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-built, executable, bundle-accurate skill document: all code references resolve to real functions and CLI flags, the workflow has validation and fallback steps, and the domain data (pressures, conversions, cylinder specs) is genuinely non-obvious. Weaknesses are minor: an ambiguous overlapping unit-detection rule, an internally inconsistent cron path, and some duplication between the capability summary and core sections.

Suggestions

Fix the overlapping unit-detection ranges in Workflow step 2 (values 15–150 match both the PSI and Bar rules) with non-overlapping thresholds and an explicit precedence or disambiguation step.

Correct the cron examples' path (e.g. `cd /lab/scripts && python main.py` or drop the cd) so they are copy-paste runnable.

Trim the "Key Capabilities" bullet list, which restates the "Core Capabilities" sections, or merge the unit-conversion rule with the Pressure Conversion Reference table to remove redundancy.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables, executable snippets, and domain data Claude genuinely lacks (typical cylinder pressures, conversion factors, cylinder durations) rather than explanations of known concepts. Minor trimming is possible: the opening "Key Capabilities" bullet list duplicates the "Core Capabilities" sections, and the Pressure Conversion Reference table partially repeats the unit-detection rule in the Workflow. A 5 would require every section to be non-duplicative; a 3 would need noticeably padded passages.

4 / 5

Actionability

Guidance is mostly copy-paste ready: the Quick Check commands, the Python import examples (all referenced functions verified to exist in scripts/main.py), CLI examples, and the full Parameters table matching the actual argparse flags. The gap is the cron examples — `cd /lab/scripts && python scripts/main.py` is internally inconsistent (after cd, scripts/main.py is not at that relative path) — so it fits the 4 anchor of concrete, executable guidance with minor gaps rather than the fully executable 5.

4 / 5

Workflow Clarity

The 6-step Workflow has a clear sequence with real checkpoints: input range validation (step 3), an explicit fallback path (step 6), an Error Handling section with manual-calculation fallback, and a Quick Check verification. It misses a 5 because the unit-detection rule in step 2 is ambiguous — "If pressure > 15 and < 220, assume PSI" and "If pressure > 15 and < 150, assume Bar" overlap for values 15–150, leaving the reader without a disambiguation step; a 3 would lack the validation checkpoints that are present.

4 / 5

Progressive Disclosure

Scored against the actual bundle: scripts/main.py exists and every path and function the body references (scripts/main.py, calculate_remaining_days, calculate_depletion_time, is_weekend, will_deplete_on_weekend, all CLI flags) is real — no dangling references, no nesting. Structure is well-sectioned with a single ~180-line overview. It falls short of 5 only because content that could live in a reference file (cron recipes, conversion/spec tables, pitfalls) is all inlined in SKILL.md, fitting the 4 anchor of good structure with minor organization gaps.

4 / 5

Total

16

/

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 strong, specific, third-person description with a well-defined niche and concrete action list. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3 and leaves a few natural trigger terms (incubator, CO2 cylinder, gas run-out) unsaid.

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when checking CO2 cylinder pressure, predicting tank or gas depletion, or planning pre-weekend replacement in cell culture incubator labs."

Include natural synonyms users would say: "CO2 cylinder", "incubator", "gas run-out", and "cylinder replacement" alongside the existing "CO2 tank" and "gas outages".

Mention the simulation/training capability explicitly in the description so users asking for drills or staff training scenarios trigger the skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete, third-person actions — "Monitors cylinder pressure, calculates consumption rates, provides early warnings, and supports automated scheduling via cron" plus "predict CO2 tank depletion and prevent weekend gas outages" — covering the skill's full capability set. This matches the anchor for multiple specific concrete actions with comprehensive coverage; a 4 would require noticeable gaps in the action list, which are absent.

5 / 5

Completeness

The "what" is clear (predict CO2 tank depletion, monitor pressure, early warnings, cron scheduling), but there is no "Use when..." clause or equivalent explicit trigger guidance — "to prevent weekend gas outages in cell culture facilities" states a purpose, not when to invoke the skill. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3; a 4 would require an explicit (if imperfect) when-clause.

3 / 5

Trigger Term Quality

Good natural-term coverage: "CO2 tank", "tank depletion", "gas outages", "cylinder pressure", "cell culture", "cron". It falls short of the 5 anchor because common user phrasings are missing — "CO2 cylinder" (only implied), "incubator", "gas run-out / replace cylinder" — whereas a 3 would miss multiple common variations or synonyms.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and well-defined — CO2 cylinder depletion prediction for cell culture facilities with weekend risk and cron scheduling — with essentially no overlap with other skill domains. This is a clear niche with distinct triggers and minimal conflict risk; a 4 would require some overlap with closely related skills, which is not the case.

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/co2-tank-monitor/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.