CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-decision-support

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). ...

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/Academic Writing/clinical-decision-support/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 body is well-organized by topic and contains genuinely useful concrete artifacts (LaTeX first-page example, schematic command, document structure specs), but it is heavily padded with repeated mandates and duplicated scope sections, lacks a sequenced end-to-end workflow with validation checkpoints, and advertises 14+ bundle files that are missing from the bundle entirely. The dominant failure is verbosity plus broken file references rather than missing domain knowledge.

Suggestions

Actually ship the referenced files (references/, scripts/, assets/) or delete the "See the references/scripts/assets directory" sections — 14 named, non-existent files make the progressive-disclosure structure a dead end.

Merge the three separate statements of the page-1 executive-summary mandate (Document Structure, Output Format, Best Practices) into one section, and collapse "When to Use"/"Integration"/"Key Differentiators" into a single boundary section — this alone would cut hundreds of tokens.

Add an explicit sequenced workflow (gather inputs → run analysis scripts → assemble from template → run validate_cds_document.py → fix and re-validate) with the validation script embedded as a checkpoint.

DimensionReasoningScore

Conciseness

The ~530-line body is noticeably verbose with several padded, redundant sections: the page-1 executive summary mandate is stated three times ("CRITICAL REQUIREMENT: All clinical decision support documents MUST begin with a complete executive summary on page 1" in Document Structure, "MANDATORY FIRST PAGE REQUIREMENT" in Output Format, and "First Page Executive Summary (MANDATORY)" in Best Practices); the treatment-plans boundary is repeated across "When to Use" ("Do NOT use this skill for: Individual patient treatment plans"), "Integration", and "Key Differentiators from Treatment-Plans Skill"; and the marketing-style use-case catalogs (Drug Development, Medical Affairs, Clinical Guidelines, Real-World Evidence) restate capabilities already listed. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections'). Not 1 because it does not explain concepts Claude already knows (no basic PDF/LaTeX tutorials), and not 3 because the duplication is substantial, not just occasional over-explanation.

2 / 5

Actionability

Concrete elements exist: a copy-paste-ready LaTeX first-page example with tcolorbox code, the command "python scripts/generate_schematic.py \"your diagram description\" -o figures/output.png", and named templates. However, the bulk of the body is descriptive capability enumeration ("Evidence-based treatment guidelines for specific disease states", "Subgroup Analyses: Forest plots showing treatment effects") rather than executable instruction, and the referenced scripts and templates (e.g., generate_survival_analysis.py, cohort_analysis_template.tex) do not exist in the bundle, so a user following them hits dead ends. This lands between anchor 2 and anchor 4, fitting anchor 3 ('some concrete guidance but incomplete; missing key details').

3 / 5

Workflow Clarity

Sub-workflows are sequenced (the schematic steps "1. Generate at minimum ONE schematic... 2. For cohort analyses: include patient flow diagram" and the page-1 → TOC → detailed-sections layout), but there is no overall end-to-end sequence for producing a document (inputs → analysis → assembly → verification). Validation is named as a tool ("validate_cds_document.py - Quality and compliance checks") but never embedded as an explicit checkpoint in a workflow with a fix-and-retry loop, matching anchor 3 ('steps listed but validation gaps; checkpoints missing or implicit'). Not 4 because no coherent document-generation sequence with verification steps exists; not 2 because the sub-processes that are present are clearly defined.

3 / 5

Progressive Disclosure

The body points to "references/", "assets/" (cohort_analysis_template.tex, treatment_recommendation_template.tex, etc.) and "scripts/" (generate_survival_analysis.py, create_waterfall_plot.py, etc.), but none of these files or directories exist in the actual bundle — every reference dangles. Meanwhile all detail (capability catalogs, best practices, five usage examples, GRADE tables) is inlined in a single ~530-line SKILL.md that clearly belongs in separate files. Per the guideline to score against the actual bundle structure, this matches anchor 2 ('content that clearly belongs in separate files is inlined'). Not 1 because section headers provide real navigation and references are one level (not nested); not 3 because the referenced files are absent, so the split promised by the pointers does not actually exist.

2 / 5

Total

10

/

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.

The description states a clear 'what' with two well-specified document types and good domain keywords, but entirely lacks 'when to use' trigger guidance, which caps completeness. Third-person voice is used correctly and no vague filler appears. The truncated '...' ending suggests the description was cut off mid-sentence.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks for patient cohort analyses, biomarker-stratified subgroup comparisons, or evidence-based treatment recommendation reports' — this would raise completeness from 3 to 5.

Remove the trailing '...' truncation artifact so the description reads as a complete sentence.

Include a boundary phrase like 'not for individual patient treatment plans' to reduce overlap with treatment-plans-style skills directly in the description.

DimensionReasoningScore

Specificity

Quotes: "Generate professional clinical decision support (CDS) documents", "patient cohort analyses (biomarker-stratified with outcomes)", "treatment recommendation reports (evidence-based guidelines with decision algorithms)". Several concrete deliverables with meaningful parenthetical detail (biomarker stratification, decision algorithms), matching anchor 4 ('several specific actions; minor gaps'). Not 5 because coverage is incomplete (no mention of statistical analysis, evidence grading, or survival analysis), and not 3 because it goes beyond naming just 1-2 generic actions.

4 / 5

Completeness

Quotes: "Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including..." — the 'what' is clearly stated (two document types with specifics), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guideline, a missing 'Use when' clause caps completeness at 3, which matches anchor 3 ('clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Quotes: "clinical decision support (CDS)", "patient cohort analyses", "treatment recommendation reports", "evidence-based guidelines", "pharmaceutical". These are natural phrases a researcher would say, matching anchor 4 ('good keyword coverage; a few natural terms missing'). Not 5 because common variations like "clinical trial analysis", "subgroup analysis", "evidence grading", or "survival analysis" are absent; not 3 since multiple relevant natural keywords are present rather than only 'some'.

4 / 5

Distinctiveness Conflict Risk

Quotes: "clinical decision support (CDS) documents", "patient cohort analyses (biomarker-stratified with outcomes)", "treatment recommendation reports". The specialized document types create a clear niche with distinct triggers, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills'). Not 5 because the description itself does not differentiate from adjacent medical-documentation skills (e.g., treatment-plans, clinical-reports); not 3 because the specific deliverables are more distinct than 'somewhat specific'.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (529 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/clinical-decision-support/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.