CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reagent-expiry-alert

Scan reagent barcodes or IDs, log expiration dates, and generate multi-level alerts before reagent expiry to support laboratory inventory management.

Quality

75%

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/reagent-expiry-alert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured, highly actionable skill body with a real, executable bundled script and clean single-file organization. Its main weaknesses are duplicated boundary/error-handling prose across sections and a mismatch between the documented alert levels and the script's actual behavior.

Suggestions

Merge the Input Validation section's out-of-scope guidance with the When to Use bullet list (or vice versa) and delete the duplicated missing-input rule from either Workflow step 6 or Error Handling.

Unify Stress-Case Rules and Response Template into a single response structure, or state when each applies, to remove the overlap.

Reconcile the Alert Levels table with the script's actual buckets (expired/≤7 days vs. alert_days threshold) and document the script's --list flag, so the doc and implementation match.

DimensionReasoningScore

Conciseness

Mostly efficient — no padding explaining concepts Claude already knows — but there is real duplication that could be tightened: the scope boundary appears twice ("Do not use this skill to manage controlled substances, biological hazards..." in When to Use vs. the nearly identical Input Validation section), the missing-input rule is repeated verbatim (Workflow step 6 vs. Error Handling), and Stress-Case Rules and Response Template are two overlapping response structures. Not 4: the redundancy spans multiple sections, not just minor over-explanation; not 2: the body is not padded and the bulk of each section earns its tokens.

3 / 5

Actionability

Concrete, copy-paste-ready commands throughout: Quick Check ("python -m py_compile scripts/main.py", "python scripts/main.py --help"), full Usage invocations with realistic arguments, and a complete Parameters table; the referenced scripts/main.py exists and runs. Not 5: there are minor gaps — the documented Alert Levels (Critical ≤30 days, Warning ≤60 days) do not match the script's actual buckets (expired/≤7 days, then alert_days), and the script's --list flag is undocumented; not 3: guidance is fully executable, not pseudocode.

4 / 5

Workflow Clarity

The 6-step Workflow is clearly sequenced with an explicit date-validation checkpoint ("If --expiry is provided, validate that it is a valid YYYY-MM-DD date... emit a warning") and an Error Handling section covering script failure ("report the failure point, summarize what still can be completed safely, and provide a manual fallback"). Not 5: there is no explicit validate-fix-retry feedback loop, and the Quick Check is a one-time smoke test rather than a per-run checkpoint; not 3: validation is explicitly present, not implicit or missing.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clear section headers, and the only bundle file (scripts/main.py) is a real, correctly-pathed, one-level-deep reference that is clearly signaled in Quick Check, Workflow, and Usage. Content is appropriately placed — the Parameters table and Alert Levels are concise enough to live inline — and navigation is easy. Not 4: there is no content inlined that belongs in a separate file and no buried or nested references.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid, third-person description with concrete actions and a distinct laboratory niche, held back mainly by the absence of any explicit "Use when..." trigger clause. Adding one sentence of trigger guidance would raise completeness and trigger-term quality simultaneously.

Suggestions

Append an explicit trigger clause, e.g., "Use when tracking reagent expiry dates, scanning reagent barcodes, or checking laboratory inventory for expiring or expired reagents."

Add one or two natural user phrasings as synonyms (e.g., "expiring reagents", "out-of-date reagents") to broaden trigger coverage.

Optionally mention the alert-check and inventory-report outputs (e.g., "check for upcoming expirations and report reorder recommendations") to close the specificity gap.

DimensionReasoningScore

Specificity

Lists three concrete actions — "Scan reagent barcodes or IDs", "log expiration dates", "generate multi-level alerts before reagent expiry" — matching the anchor for several specific actions with minor gaps. Not 5: coverage is not comprehensive (inventory listing, reorder recommendations, and check-alert workflows are absent) and "multi-level alerts" is somewhat abstract; not 3: it goes beyond 1-2 actions with a clear, concrete capability set.

4 / 5

Completeness

The "what" is clear (scan, log, alert), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4: the "when" is not merely under-specified — it is entirely absent, not even weakly implied.

3 / 5

Trigger Term Quality

Good keyword coverage with natural domain terms — "reagent", "barcodes", "expiration dates", "expiry", "laboratory inventory" — and it uses both "expiration" and "expiry" as synonyms. Not 5: a few natural phrases users might say are missing (e.g., "expiring reagents", "out of date", "lab stock"); not 3: it is not limited to one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

"reagent barcodes", "expiration dates", and "reagent expiry" form a clear niche with distinct triggers and minimal conflict risk with other skills. Not 4: the trailing purpose clause "to support laboratory inventory management" describes intent rather than adding a competing trigger surface, so overlap risk with general inventory skills is minimal.

5 / 5

Total

16

/

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/reagent-expiry-alert/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.