medical-unit-converter

Convert medical laboratory values between units (mg/dL to mmol/L, etc.) with formula transparency and clinical reference ranges. Supports glucose, cholesterol, creatinine, and hemoglobin conversions.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/medical-unit-converter/SKILL.md

Quality

Content

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

An actionable, well-structured skill body with executable examples, validation, and a fallback loop, weakened slightly by generic Workflow prose and an unreferenced guidelines.md. Tightening the workflow language and linking the reference file would raise it.

Suggestions

Replace the generic Workflow steps with concrete conversion-specific steps (parse --value/--from-unit/--to-unit, call scripts/main.py, emit the JSON Output Format), keeping the validation/fallback steps.

Link references/guidelines.md from the body (e.g. under a References section) so the bundled reference file is signaled and not orphaned.

Align the Implementation Notes convert() return-dict description with main.py's actual fields (input_value/input_unit/output_value/output_unit) to remove the minor actionability gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tables and examples, but the Workflow section is generic consulting prose ('Confirm the user objective, required inputs, and non-negotiable constraints') unrelated to unit conversion, adding noticeable padding.	3 / 5
Actionability	Provides copy-paste executable commands in Quick Check, a concrete Input Parameters table, an Output Format JSON example, and a bundled script; minor gaps only (documented convert() return fields differ slightly from main.py).	4 / 5
Workflow Clarity	Clear sequence with validation checkpoints present (py_compile quick check, Error Handling rules, Fallback Template feedback loop); the generic Workflow steps hold it back from 5 but the simple, well-guarded operation is otherwise unambiguous.	4 / 5
Progressive Disclosure	Well-organized single overview with a bundled script referenced from the body; minor gap: references/guidelines.md exists but is never linked or signaled from the body.	4 / 5
	Total	15 / 20 Passed

Description

66%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-keyworded description with a clear niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3. Adding a concrete trigger phrase would lift it to the top band.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when converting lab values like glucose or creatinine between mg/dL and mmol/L, or when clinical reference ranges are needed alongside a conversion.'

Broaden trigger terms with common synonyms (e.g. 'lab results', 'blood work units', 'unit conversion') to push trigger-term quality toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("Convert...between units", "formula transparency", "clinical reference ranges") plus four analytes; not fully comprehensive but lists multiple specific actions.	4 / 5
Completeness	Has a clear "what" (convert lab values between units with formula/range context) but no explicit "Use when..." trigger clause, so per the missing-trigger guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage (mg/dL, mmol/L, glucose, cholesterol, creatinine, hemoglobin, lab values, reference ranges) that users would actually say; a few synonyms/variations are missing, stopping short of 5.	4 / 5
Distinctiveness Conflict Risk	The medical lab-unit-conversion niche with specific analyte/unit triggers is mostly distinct; only minor overlap risk with general unit-conversion skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/medical-unit-converter/SKILL.md
Commit: f5ef65b

Reviewed: ~18 hours ago

Table of Contents

Discovery Implementation Validation

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.