CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-diagnostic-reasoning

Identify and counteract cognitive biases in medical decision-making through systematic error analysis and contextual algorithm application. For diagnostic reasoning, treatment decisions, and

Quality

60%

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/clinical-diagnostic-reasoning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 skill delivers concrete, well-sequenced decision flows and specific expert-vs-novice phrasings for clinical cognitive-bias correction, but nearly half the body is educational padding (bias-development timelines, metaphors, shibboleths) that costs tokens without adding instructions. Splitting the anti-pattern catalog into a reference file and cutting the padding would materially improve it.

Suggestions

Remove or drastically cut the 'Timeline:' paragraphs, 'Navigation Metaphor', 'Trap Metaphor', and 'Core Shibboleths' sections — they describe how human expertise develops, which does not guide execution.

Move the six detailed anti-pattern entries (novice/expert/timeline each) into a references/ file (e.g. ANTI-PATTERNS.md), keeping one-line summaries and the expert questions inline in SKILL.md.

Add a brief error-recovery loop to the diagnostic flow: what to do when the bias check flags a problem (e.g. regenerate the differential from scratch and re-examine disconfirming evidence before proceeding).

DimensionReasoningScore

Conciseness

Several padded sections explain material Claude either already knows or does not need to perform the skill: a 'Timeline:' paragraph for each of the six biases describing how expertise develops over years, a 'Navigation Metaphor', a 'Trap Metaphor', 'Core Shibboleths', and a References section restating the book's thesis. This matches 'noticeably verbose; several unnecessary explanations or padded sections' (2) rather than the mostly-efficient level of 3.

2 / 5

Actionability

The three ASCII decision flows are genuinely concrete — specific questions to ask ('What else could this be?', 'Does this explain ALL findings?', 'How is this patient NOT like that case?') and explicit branches — and the novice/expert contrasts give usable phrasings. However, roughly 40% of the body (timelines, metaphors, shibboleths, references) is descriptive rather than instructive, so guidance is incomplete in coverage, fitting score 3 rather than the 'mostly executable with minor gaps' of 4.

3 / 5

Workflow Clarity

The diagnostic flow is a clearly sequenced decision tree with a mandatory checkpoint ('[BIAS CHECK - Always perform]'), the error-analysis flow separates knowledge gaps from thinking errors before branching, and the communication flow ends with a comprehension-verification step ('What is your understanding of the risks/benefits?'). Checkpoints are present and explicit; it falls short of 5 only because there are no error-recovery/feedback loops (e.g. what to do when the bias check flags a problem mid-workup) beyond the branch instructions.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, but it is a single ~200-line monolith with no bundle files (no references/, scripts/, or assets/ exist) — the six detailed anti-pattern entries and mental-models material are inline content that would fit a one-level-deep references file. This matches 'some structure but could be better organized; content that should be separate is inline' (3); the under-50-line simple-skill exception does not apply.

3 / 5

Total

12

/

20

Passed

Description

53%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, distinctive purpose (cognitive-bias correction in clinical reasoning), but it is truncated mid-sentence, leaving the trigger/usage clause incomplete and the capability list cut short. Specific and distinctive, yet not fully usable as trigger guidance.

Suggestions

Complete the truncated description: the sentence ends at 'For diagnostic reasoning, treatment decisions, and' — finish the list and keep it under the description field's length limit.

Add an explicit 'Use when...' clause with natural trigger phrases users would say, e.g. 'Use when working through a differential diagnosis, treatment decisions, case review, or analyzing a diagnostic error'.

Include common synonyms such as 'clinical reasoning', 'differential diagnosis', 'anchoring bias', and 'diagnostic error' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description states the domain ('medical decision-making') and a couple of concrete actions ('Identify and counteract cognitive biases', 'systematic error analysis and contextual algorithm application'), but coverage is not comprehensive and 'contextual algorithm application' leans abstract. It names the domain plus 1-2 real actions without enumerating the skill's full scope, matching the score-3 anchor rather than 4, which would require several listed actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear (identify and counteract cognitive biases in medical decision-making), but the 'when' clause is literally cut off mid-sentence ('For diagnostic reasoning, treatment decisions, and'), leaving the usage guidance incomplete. Per the guideline that a missing or weak explicit 'when' clause caps completeness at 3, this sits at the score-3 anchor; it does not reach 4 because the when-guidance is not usable as written.

3 / 5

Trigger Term Quality

Relevant natural keywords are present ('cognitive biases', 'medical decision-making', 'diagnostic reasoning', 'treatment decisions') that a clinician would plausibly say, but the trigger clause is truncated mid-list ('...treatment decisions, and'), cutting off further terms and missing common synonyms such as 'clinical reasoning', 'differential diagnosis', or 'case review'. This fits 'some relevant keywords but missing common variations or synonyms' (3), not the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The clinical cognitive-bias niche ('cognitive biases in medical decision-making', 'diagnostic reasoning') is clearly distinguishable from generic document-, code-, or data-processing skills, with only minor overlap risk against other clinical/medical-education skills. It is not a 5 because the truncated trigger list prevents fully distinct, concrete triggers from being stated.

4 / 5

Total

13

/

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/clinical-diagnostic-reasoning/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.