healthcare-cdss-patterns

Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/healthcare-cdss-patterns/SKILL.md

The canonical home for this skill is tdg-personal/healthcare-cdss-patterns

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and safety-focused with clear workflows and validation, but it is held back by undefined helper functions and a monolithic single-file structure that would benefit from progressive disclosure into reference files.

Suggestions

Define or stub the referenced helpers (findInteraction, getDoseRules, getAgeAdjustedMax, getRenalAdjustedMax) so the code examples are executable rather than partially pseudocode.

Move large lookup data (interaction pairs, NEWS2 scoring tables, dose-rule schemas) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the inline function implementations to patterns/snippets that earn their tokens, keeping SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and avoids explaining basic concepts Claude already knows, but the ~237-line single document with full function implementations could be tightened; it sits at 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	Concrete TypeScript interfaces, functions, a severity table, and worked examples are provided, but core helpers (findInteraction, getDoseRules, getAgeAdjustedMax, getRenalAdjustedMax) are referenced without definition, leaving key details incomplete — matching the score-2 anchor of concrete but incomplete guidance.	2 / 3
Workflow Clarity	A clear architecture diagram sequences the EMR→CDSS→alert flow, modules are enumerated, and the testing section provides explicit validation checkpoints (100% pass criteria, reverse-direction interaction tests, missing-weight block test) with error feedback for a safety-critical system.	3 / 3
Progressive Disclosure	No bundle files exist and all content is inline in one ~237-line SKILL.md; scoring tables, interaction-pair data, and dose-rule definitions that could be split into reference files are instead inline, matching the score-2 anchor of content that should be separate being inline.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 is specific and distinctive with strong natural trigger terms, but it omits an explicit "Use when…" trigger clause, so it answers "what" well while leaving "when" only implied.

Suggestions

Add an explicit 'Use when…' clause naming common trigger phrases (e.g., 'Use when building clinical decision support, drug interaction checks, dose validation, or NEWS2/qSOFA scoring into an EMR').

Include a few more common user variations such as 'medication safety checks' or 'clinical alert rules' to broaden natural-language coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — "Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows" — matching the score-3 anchor of listing several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when…" clause or equivalent explicit trigger guidance for when Claude should invoke it, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural, varied terms a clinician or developer would say are present ("CDSS", "drug interaction checking", "dose validation", "NEWS2/qSOFA", "EMR workflows"), giving good coverage; it is not merely technical jargon, though it lacks some common variations.	3 / 3
Distinctiveness Conflict Risk	The healthcare/CDSS niche with distinctive triggers (NEWS2, qSOFA, EMR, dose validation) is clearly bounded and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/healthcare-cdss-patterns/SKILL.md
Commit: 754b8dd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.