CtrlK
BlogDocsLog inGet started
Tessl Logo

choosing-openmed-models

Discover and pick the right OpenMed model for a clinical or biomedical task, domain, or language. Use when the user asks which OpenMed model to use, wants to list model categories, find a Disease vs Oncology vs Privacy/PII model, get a PII model for a specific language, search models by size or task, or inspect a model's labels and metadata before loading. Covers list_model_categories, get_models_by_category, get_pii_models_by_language, get_default_pii_model, search_models(ModelQuery(...)), get_model_info, and the openmed models CLI. Pairs with loading-openmed-models.

76

Quality

95%

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

90%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 highly actionable, well-sectioned skill body built almost entirely from executable examples and domain-specific reference material, with a clear selection workflow and a useful gotchas section. The only gaps are an explicit validation/feedback loop in the main flow and the absence of any progressive-disclosure reference files.

Suggestions

Add an explicit validate-then-proceed checkpoint in the Quick start flow (e.g. 'Confirm entity_types matches your schema before handing off to loading-openmed-models') to lift workflow_clarity to 5.

Consider extracting the ModelInfo attribute table and ModelQuery filter list into a reference file referenced one level deep, to push progressive_disclosure toward 5.

Make the Disease vs Oncology vs Privacy decision a short numbered checklist rather than three parallel code blocks, so the selection workflow reads as a single sequenced process.

DimensionReasoningScore

Conciseness

Lean and efficient: nearly every section is executable code or tightly-scoped domain-specific reference (e.g. the ModelInfo attribute table) that Claude would not already know, with minimal connective prose and no padding about general concepts.

5 / 5

Actionability

Fully executable, copy-paste-ready examples throughout — list_model_categories, get_models_by_category, search_models(ModelQuery(...)), get_pii_models_by_language, the CLI — each with realistic inputs and expected outputs covering the common cases.

5 / 5

Workflow Clarity

A clear browse→inspect→hand-off sequence is present (numbered Quick start, explicit 'Hand-off to / from OpenMed' section) and the 'Edge cases & gotchas' list supplies checks ('Match labels before committing', 'get_default_pii_model can return None'), but there is no explicit validate→fix→retry loop within the main workflow.

4 / 5

Progressive Disclosure

Well-organized into clearly-labeled sections (When to use, Quick start, ModelInfo, Disease vs Oncology, PII by language, search, CLI, hand-off, edge cases, references) with an external pointer to the HF org; no bundle files exist, and most content is appropriately inline, though some API reference material (ModelInfo attributes, ModelQuery filters) could conceivably live in a separate file.

4 / 5

Total

18

/

20

Passed

Description

100%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, third-person description that concretely enumerates the API surface, provides an explicit 'Use when' trigger with natural phrasing, and draws a clear boundary against its paired loading skill. No verbosity or fluff to penalize.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full API surface — 'list_model_categories, get_models_by_category, get_pii_models_by_language, get_default_pii_model, search_models(ModelQuery(...)), get_model_info' — giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers both 'what' ('Discover and pick the right OpenMed model...') and 'when' ('Use when the user asks which OpenMed model to use, wants to list model categories...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when...' clause is packed with natural phrases a user would actually say ('which OpenMed model to use', 'find a Disease vs Oncology vs Privacy/PII model', 'get a PII model for a specific language', 'search models by size or task') alongside their API-name synonyms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OpenMed model selection) with distinct triggers and an explicit hand-off boundary ('Pairs with loading-openmed-models'), minimizing overlap with adjacent skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
maziyarpanahi/openmed
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.