CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lab-result-interpretation

Transforms biochemical lab test results into clear, patient-friendly explanations. Covers blood routine, lipid panel, liver/kidney function, thyroid, electrolytes, and inflammation markers. Flags critical values, classifies severity, and generates structured interpretation rep...

Quality

69%

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-result-interpretation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 core instructional content (workflow, usage, formats) is concrete and well structured with appropriate offloading of data to reference files, but the document is heavily padded with generic administrative sections and contains dangling references to nonexistent files. Trimming the boilerplate and reconciling the file references would make it substantially leaner and more trustworthy.

Suggestions

Remove or collapse the generic administrative sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) that add no task-specific guidance, and deduplicate the 'Quick Check' / 'Audit-Ready Commands' py_compile command.

Fix the dangling bundle references: either add references/test_metadata.json or remove it from the Workflow and References sections; same for the missing requirements.txt in Prerequisites.

Add a brief validate-and-retry step for the parse phase (e.g., what to do when a test name or reference range fails to match) to close the workflow's only checkpoint gap.

DimensionReasoningScore

Conciseness

Roughly half the body is generic administrative boilerplate unrelated to executing the skill ('Risk Assessment' table, unchecked 'Security Checklist', 'Evaluation Criteria', 'Lifecycle Status', 'Output Requirements', 'Response Template'), and 'python -m py_compile scripts/main.py' is duplicated in both 'Quick Check' and 'Audit-Ready Commands' — matching 'noticeably verbose; several unnecessary explanations or padded sections'. Not 3 because the padding is extensive and includes a stale date ('Next Review Date: 2026-03-06') that penalizes per the guidelines, and not 1 because the core sections (Workflow, Usage, Parameters, Input/Output Format) are themselves efficient.

2 / 5

Actionability

Provides executable module import and CLI examples, a concrete parameters table, and explicit input/output format specs, matching 'mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because 'pip install -r requirements.txt' references a file that does not exist in the bundle, and the module example's output attribute (result.explanation) is unverified against the script.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with per-step inputs and outputs and an explicit critical-value checkpoint ('⛔ Checkpoint: Flag critical values to user with "Seek immediate medical attention" warning before continuing'), matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because there is no validate-and-retry feedback loop for parse failures (e.g., what to do when regex extraction misses a test), and not 3 because a checkpoint plus the Error Handling fallback guidance is present.

4 / 5

Progressive Disclosure

Sections are well organized and the bulk knowledge (reference ranges, explanation templates) is correctly split into one-level-deep references/ files, matching 'good structure; most content is appropriately placed; references mostly clear; minor organization gaps'. Not 5 because 'references/test_metadata.json' is cited in both the Workflow and References sections but is missing from the actual bundle.

4 / 5

Total

14

/

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.

The description communicates a clear, concrete capability set for lab result interpretation with good natural terminology, but it is truncated mid-sentence and lacks any 'use when' trigger guidance, capping its completeness. Fixing the truncation and adding trigger conditions would raise it substantially.

Suggestions

Restore the truncated ending so 'generates structured interpretation rep...' completes as '...interpretation reports' (or similar) and the final action is fully stated.

Add a trigger clause such as 'Use when the user shares lab test results, blood work, or a lab report and asks what the values mean.'

Include common synonyms like 'blood work', 'blood test', and 'lab report' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('biochemical lab test results') and several concrete actions ('Transforms... into clear, patient-friendly explanations', 'Flags critical values, classifies severity'), matching the 'several specific actions; minor gaps' anchor. Not 5 because the description is truncated mid-word ('generates structured interpretation rep...'), leaving the final action incomplete and coverage slightly short of comprehensive.

4 / 5

Completeness

The 'what' is clear and multi-action, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete rather than vague, and not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Contains good natural terms users would say ('lab test results', 'blood routine', 'lipid panel', 'liver/kidney function', 'thyroid', 'electrolytes', 'inflammation markers', 'critical values'), matching 'good keyword coverage; a few natural terms missing'. Not 5 because common variations like 'blood work', 'blood test', 'lab report', or 'blood panel' are absent.

4 / 5

Distinctiveness Conflict Risk

A distinct medical lab-interpretation niche with named test panels minimizes conflict with unrelated skills, matching 'mostly distinct; minor overlap risk'. Not 5 because it could still overlap with general health/medical-advice skills given no explicit trigger boundary.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/lab-result-interpretation/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.