CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

loading-openmed-models

Load OpenMed clinical/biomedical NER models from the Hugging Face Hub or a local path and reuse them efficiently across calls. Use when the user wants to load an OpenMed model, control the model cache, run fully offline after a one-time download, reuse a ModelLoader to avoid reloading, set a cache_dir or device, or pick between a registry key, a full Hugging Face id, and a local directory. Pairs with choosing-openmed-models (pick the model) and extracting-clinical-entities (run it).

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-crafted, highly actionable body: copy-paste-ready code in every section, a clear three-form model-naming model, and an unusually strong edge-cases section. Minor room remains in tightening restated Hugging Face knowledge, adding an explicit verify-offline checkpoint, and splitting reference-grade detail into a separate file.

DimensionReasoningScore

Conciseness

The body is efficient and library-specific ("the second call is instant"; "Without loader=... you pay to re-instantiate the pipeline"), but a few sentences restate standard Hugging Face behavior (offline env vars, hub caching) that could be trimmed, matching the 4 anchor of minor over-explanation.

4 / 5

Actionability

Every section ships fully executable, copy-paste-ready code covering the common cases — pip install with the [hf] extra, the ModelLoader reuse loop, OpenMedConfig fields, offline env vars, get_model_max_length, and unload/loaded_models — with no gaps.

5 / 5

Workflow Clarity

The offline flow is clearly sequenced ("1. First run (online)... 2. Every run after...") with pre-warm guidance and error-recovery in the gotchas (force_reload, ImportError install hint, local-path collision rule), but there is no explicit verification checkpoint such as confirming cached state via loaded_models() before going offline, matching the 4 anchor of minor validation gaps.

4 / 5

Progressive Disclosure

A well-organized single-file skill with clear section headers, a naming-forms table, and clearly signaled hand-offs to sibling skills, with no nested references; at ~205 lines it exceeds the small-skill threshold and material like the full config-field listing could move to a reference file, placing it at good structure with minor organization gaps (4) rather than fully optimal splitting (5).

4 / 5

Total

17

/

20

Passed

Description

92%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 description: concrete, comprehensive, in third person, with an explicit Use-when clause full of natural triggers and clear delineation from adjacent skills. The only shortfall is slightly technical trigger phrasing where a few everyday synonyms are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Load OpenMed clinical/biomedical NER models from the Hugging Face Hub or a local path", "reuse them efficiently across calls", "control the model cache", "run fully offline after a one-time download", "set a cache_dir or device", "pick between a registry key, a full Hugging Face id, and a local directory" — giving comprehensive coverage with no gaps, matching the 5 anchor.

5 / 5

Completeness

It explicitly answers both what (sentence 1: load models and reuse them) and when ("Use when the user wants to load an OpenMed model, control the model cache, run fully offline..."), with concrete trigger phrases in third-person voice — the exact 5-anchor shape.

5 / 5

Trigger Term Quality

Good natural trigger coverage ("load an OpenMed model", "control the model cache", "run fully offline", "cache_dir or device") but terms like "ModelLoader", "registry key", and "full Hugging Face id" lean technical and common synonyms such as "download" or "GPU" are missing, placing it just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to OpenMed model loading and it explicitly delineates sibling skills ("Pairs with choosing-openmed-models (pick the model) and extracting-clinical-entities (run it)"), so the risk of triggering the wrong skill is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

maziyarpanahi/openmed

Path

skills/loading-openmed-models/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.