CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-research-algorithm-matcher

Matches a user’s biomedical research direction, disease problem, study aim, data modality, and resource constraints to the most relevant recent algorithms and method papers. Always search real recent algorithm literature first, prioritize the last 12 months, expand to 1–3 years only when needed, and add canonical baselines only when necessary. Every formal algorithm recommendation must include the verified primary method paper, plus published downstream papers that actually cite/use the algorithm when such papers are found, with DOI when available. Never fabricate papers, algorithm names, authors, journals, years, DOI, PMID, links, or benchmark claims. If no directly verified algorithm paper is found, say so explicitly.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./awesome-med-research-skills/Protocol Design/medical-research-algorithm-matcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 instruction-only skill with an unusually strong verification-driven workflow: explicit gates, fallbacks, and an honest-output checklist. Its weaknesses are token-level redundancy (rules repeated across sections and duplicated between body and references) and the lack of concrete search-query examples for the retrieval step itself.

Suggestions

State the search-priority and two-layer evidence rules once (in their reference modules) and reference them from the body instead of repeating them in Mandatory Behavioral Rules, Step 4, and Sections D/F.

Trim the inlined "Mandatory Output Structure" section headings to a one-line summary pointing at references/output-section-guidance.md, which already enumerates sections A–J and Section F's requirements.

Add one or two concrete literature-search query templates (e.g., example search strings for PubMed or a web search) to make Step 4's retrieval fully executable.

DimensionReasoningScore

Conciseness

The body states the ≤12-month / 1–3-year / baseline search priority three times (Mandatory Behavioral Rules 1–3, Step 4A, output Section D), repeats the two-layer evidence fields in both Step 4C and Section F, and inlines the full A–J output structure that output-section-guidance.md already carries. It never explains concepts Claude already knows, but the repetition could be consolidated.

3 / 5

Actionability

Concrete, executable guidance throughout: exact search windows ("≤12 months", "1–3 years"), an explicit acceptable-source list (DOI landing page, PubMed, PMC, arXiv/bioRxiv/medRxiv), exact required fields per paper, and an exact fallback sentence for unverified names. The minor gap is the absence of concrete search-command or query templates for the retrieval step.

4 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with explicit validation gates ("A formal algorithm can only be recommended if at least one real paper is verified", named-algorithm handling, the Step 5 fit/rejection rule), error-recovery fallbacks ("If critical detail is missing, do not fail immediately. Infer a provisional target and state assumptions"; state nearest validated alternatives when literature is weak), and a checklist-style mandatory output structure with a final risk and honesty review.

5 / 5

Progressive Disclosure

All seven referenced modules exist as real one-level-deep files, each clearly signaled and mapped to its execution step. However, the body inlines the complete output structure and evidence-field lists that the reference modules already carry, so the split is not as clean as it could be.

4 / 5

Total

16

/

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 highly specific, third-person description with strong domain vocabulary and honest anti-fabrication constraints. Its main weakness is the absence of any "Use when..." trigger clause, leaving the "when to use" half of completeness only implicit. It is clearly distinguishable from other skills but could include the natural phrasings users would actually say.

Suggestions

Add an explicit trigger clause such as "Use when the user asks for recent or latest algorithms for a disease/topic-specific research direction, wants to match a study plan to recent methods, or asks to verify a named algorithm."

Include the natural user phrasings the body already quotes (e.g., "what are the latest methods I should consider") as trigger terms in the description.

Mention the baseline-vs-recent-vs-frontier recommendation stack, a core capability currently absent from the description.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Matches a user's biomedical research direction... to the most relevant recent algorithms and method papers", "prioritize the last 12 months, expand to 1–3 years only when needed", "must include the verified primary method paper, plus published downstream papers... with DOI" — but omits capabilities the skill actually has (baseline/recent/frontier layering, named-algorithm verification), leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is explicit and detailed (matching, 12-month-first search, verified evidence package), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "recent algorithms", "method papers", "biomedical", "disease", "data modality" would plausibly appear in a user's request, but common phrasings such as "latest methods" or "which algorithms should I use for my project" are missing.

4 / 5

Distinctiveness Conflict Risk

Terms like "biomedical research direction", "DOI, PMID", and "published downstream papers that actually cite/use the algorithm" pin a clear niche, with only minor overlap risk against generic literature-search or fact-checking skills.

4 / 5

Total

15

/

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

awesome-med-research-skills/Protocol Design/medical-research-algorithm-matcher/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.