CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hippocrates

Evidence-based medical knowledge and research mentor. Trigger this skill when users ask any question related to medicine, clinical science, pharmacology, pathology, epidemiology, or health sciences. Covers: disease mechanisms, drug actions and interactions, differential diagnosis reasoning, clinical guideline interpretation, medical literature appraisal (including GRADE assessment), treatment comparisons, lab and imaging interpretation, public health analysis, and medical terminology. Even if the user doesn't explicitly say "evidence-based" or "medical research," trigger this skill whenever the topic touches health, disease, drugs, or therapeutics. Part of the AIPOCH Medical Research Skill Hub.

Quality

82%

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

SKILL.md
Quality
Evals
Security

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.

A well-structured persona skill with genuinely actionable guidance: explicit classification cues, per-question-type response structures, a safety read-before-responding checkpoint, and an exemplary reference-file table whose paths all resolve. The main weaknesses are token padding — an abundance of voice exemplars, redundant evidence-tier instructions, and a speculative module tree — that could be tightened or offloaded to the reference files.

Suggestions

Trim the seven block-quote voice exemplars in 'The Mentor's Voice' to two or three, and move the extended register discussion (e.g., the historical-perspective pacing rules) into references/persona-guide.md, keeping only the core register definition in SKILL.md.

Consolidate the evidence-quality signaling: define the tier system once (either in Step 3 or in references/evidence-grading.md) and let the format rules reference it in one line instead of re-explaining how to express it in prose.

Remove the 'Module Expansion' tree lines for '(planned)' files (drug-interactions.md, specialties/) — advertising not-yet-existing bundle files adds tokens and misleads navigation — or move the tree to the hub-level documentation.

DimensionReasoningScore

Conciseness

The body is mostly efficient persona guidance, but there is tightening to do: seven extended block-quote voice exemplars where two or three would calibrate the register; a "Module Expansion" tree listing "(planned)" files that is speculative and not actionable; a "Source" GitHub link line; and redundancy between Step 3's 🟢🟡🔴⚪ tier definitions and the later "No emoji-based evidence grading in running text" rule, which re-explains the same system. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') — clearly more substantive than anchor 2's padded sections, but not anchor 4's lean fit.

3 / 5

Actionability

For an instruction-only skill, the guidance is largely concrete and executable: student-level classification with explicit lexical cues ("uses 'differential,' 'NNT,' 'GRADE', cites trials"), a per-question-type response structure block, named reference-file read triggers, a ❌/✅ paired metformin example showing the target register, a defined fallback ("default to intermediate and offer: 'Want me to go deeper into the mechanism...'"), and concrete evidence-tier definitions. It falls short of anchor 5 because some voice guidance is abstract and unverifiable ("let the prose breathe", "sentences can be longer, more contemplative") with no beginner-level worked example, matching anchor 4 ('mostly executable guidance... with minor gaps').

4 / 5

Workflow Clarity

The Response Workflow is a clear four-step sequence (classify → structure → evidence signaling → GRADE) with a decision table mapping student level and question type to behavior, and a genuine safety checkpoint ("For personal health context ('I have...', 'my child...') → Read references/safety-framework.md before responding"). Not a destructive/batch operation, so no validation cap applies. It misses anchor 5 because there is no error-recovery or verification loop (e.g., what to do when classification is ambiguous beyond the one fallback line), and Steps 3 and 4 partially overlap on evidence-quality handling — anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The opening Reference Files table with a "When to read" column per file is exemplary well-signaled navigation, and all three referenced paths (evidence-grading.md, persona-guide.md, safety-framework.md) exist as one-level-deep bundle files — verified on disk. Kept below anchor 5 by two organization gaps: the ~100-line persona voice section is substantial content that could largely live in persona-guide.md (the SKILL.md keeps only the core), and the module tree advertises not-yet-existing "(planned)" files. Anchor 4 ('good structure; most content appropriately placed; references mostly clear; minor organization gaps') is the best fit.

4 / 5

Total

15

/

20

Passed

Description

91%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 with excellent trigger-term coverage and an explicit, concrete 'when' clause that even handles the implicit-trigger case. The capability list is comprehensive but framed as topic areas rather than verb-driven actions, and the 'any question related to health' breadth slightly raises overlap risk with adjacent health skills.

DimensionReasoningScore

Specificity

"Evidence-based medical knowledge and research mentor. Covers: disease mechanisms, drug actions and interactions, differential diagnosis reasoning, clinical guideline interpretation, medical literature appraisal (including GRADE assessment), treatment comparisons, lab and imaging interpretation, public health analysis, and medical terminology" lists nine concrete capability areas with comprehensive domain coverage. It sits between anchors 4 and 5: the coverage is comprehensive, but the items are domain/topic noun phrases rather than explicit verb-driven actions (the only action verb is "mentor"), which keeps it below the multiple-concrete-actions bar of anchor 5 while clearly above anchor 4's 'minor gaps'.

4 / 5

Completeness

The 'what' is explicit ("Evidence-based medical knowledge and research mentor" plus a nine-item coverage list) and the 'when' is explicit with concrete trigger phrases: "Trigger this skill when users ask any question related to medicine..." and "Even if the user doesn't explicitly say 'evidence-based' or 'medical research,' trigger this skill whenever the topic touches health, disease, drugs, or therapeutics." This clearly matches anchor 5 (both what and when with concrete trigger phrases) and exceeds anchor 4's 'when could be more explicit' since it even covers the implicit-trigger case.

5 / 5

Trigger Term Quality

"medicine, clinical science, pharmacology, pathology, epidemiology, or health sciences" plus "health, disease, drugs, or therapeutics" provides comprehensive natural-term coverage including the everyday synonyms users actually say ("drugs" for medications, "health", "disease") alongside technical terms ("GRADE", "clinical guideline", "lab and imaging"). Matches anchor 5's standard of comprehensive natural terms including synonyms; anchor 4 would require noticeable missing variations, and none are evident.

5 / 5

Distinctiveness Conflict Risk

The medical-mentor niche is clearly distinct from document, code, or data skills and the triggers (pharmacology, GRADE, differential diagnosis) are domain-specific. However "any question related to... health sciences" and "whenever the topic touches health" are maximally broad, creating minor-to-moderate overlap risk with closely related health/wellness/patient-safety skills — fitting anchor 4 ('mostly distinct; minor overlap risk') rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

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

scientific-skills/Other/hippocrates/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.