CtrlK
BlogDocsLog inGet started
Tessl Logo

lab-inventory-predictor

Predict depletion time of critical lab reagents based on historical usage frequency, and automatically generate purchase alerts when stock falls below safety thresholds.

64

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 ./scientific-skills/Other/lab-inventory-predictor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill body is highly actionable with clear, validated workflows and a real referenced script, scoring well on actionability and workflow clarity. Its main weakness is mild verbosity in the validation messaging and prerequisites, and some long inline reference material.

Suggestions

Tighten the out-of-scope reply into one short sentence and move the full fallback wording into the Fallback Behavior section to cut repetition.

Remove the 'pip install -r requirements.txt' block under the 'No external dependencies' bullet, or drop the dependency bullet entirely, since it contradicts the 'no external dependencies' claim.

Consider moving the full parameter tables and Python API examples into a references file (e.g. REFERENCE.md) and linking from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tables and code blocks, but includes padded sections — the long quoted out-of-scope reply, a verbose 'strictly required' prerequisites explanation with inline version-guard code, and a 'pip install -r requirements.txt' line directly under 'No external dependencies' — that could be tightened.

3 / 5

Actionability

It provides fully executable, copy-paste-ready CLI commands and a Python API example covering common cases, plus concrete parameter tables and explicit algorithm formulas, matching the anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

The workflow is clearly sequenced with explicit validation checkpoints (input validation as step 1, a Quick Check block) and feedback loops for error recovery (Fallback Behavior and Error Handling with validate→report→manual-retry), matching the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

Content is well-organized under clear section headers with the single bundle file (scripts/main.py) referenced and present, but the inline Parameters/Python API sections are fairly long and could partly live in a reference file, leaving it just short of a clean one-level-deep split.

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 specific and clearly distinct within its lab-inventory niche, but lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrases would lift the completeness and trigger-term dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when managing lab reagent inventory, predicting when reagents will run out, or deciding when to reorder supplies.'

Broaden trigger terms with natural synonyms a researcher might say (e.g. 'reorder', 'running low', 'restock', 'supply shortage').

Keep the third-person voice but tighten to a single sentence so the 'what' and 'when' read together.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Predict depletion time', 'based on historical usage frequency', 'generate purchase alerts', 'stock falls below safety thresholds' — giving comprehensive coverage of the skill's capabilities, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It clearly answers 'what' (predict depletion, generate purchase alerts) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3 with the 'when' only weakly implied.

3 / 5

Trigger Term Quality

It surfaces natural domain terms users would say ('lab reagents', 'depletion', 'purchase alerts', 'safety thresholds', 'stock'), but leans slightly technical and omits common synonyms a lay user might phrase, placing it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The lab-reagent depletion/alerting niche is clearly bounded with distinct triggers and minimal overlap with other skills, matching the anchor for a clear niche with minimal conflict risk.

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.