CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clinical-reports

Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory complianc...

Quality

67%

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-reports/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 body is authoritative and well-bundled — every referenced reference, template, and script path resolves to a real file (except the schematic generator), and workflows carry regulatory timelines. Its central weakness is that SKILL.md is the whole textbook rather than an overview: roughly 80% of the content restates material already in references/ and assets/, at severe token cost, and the mandatory-figure section depends on a missing script and an external skill.

Suggestions

Cut SKILL.md to an overview + TL;DR + workflow + resource index, moving the inlined CARE checklist, HIPAA identifier list, and per-report-type section anatomy into the existing reference/template files they duplicate.

Remove or soften the "MANDATORY scientific-schematics" section: scripts/generate_schematic.py is absent from the bundle and it hard-depends on an external skill not shipped here.

Add one executable usage example per validation script (e.g. "python scripts/validate_case_report.py draft.md") and insert an explicit run-validation checkpoint into each report workflow.

DimensionReasoningScore

Conciseness

The ~1,150-line body is a textbook inlined into SKILL.md: full CARE checklists, the 18 HIPAA identifiers, SOAP/H&P/discharge section anatomy, ICH-E3 section lists, and standard nomenclature (SNOMED/LOINC/ICD-10) — all concepts Claude already knows and all duplicated in the bundled reference files. Genuinely skill-specific nuggets (7/15-day SAE timelines, Joint Commission do-not-use abbreviations, turnaround benchmarks) are diluted by heavy padding, fitting 'noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Guidance is concrete: exact template paths ("assets/soap_note_template.md", "assets/clinical_trial_csr_template.md"), validation scripts named per task ("scripts/validate_case_report.py", "scripts/check_deidentification.py"), worked report excerpts, and regulatory timelines. Not a 5 because the only literal command shown, "python scripts/generate_schematic.py", targets a script that does not exist in the bundle, and no usage examples (arguments, expected output) are given for any of the eight real scripts.

4 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced with realistic timeframes (case report Phases 1–6 by week, SAE "24 hours to 15 days", CSR "6–12 months") and include review checkpoints (Phase 4 internal review, CSR QC review) plus a Final Checklist. Not a 5 because validation is generic — "Validation scripts are available in the scripts/ directory" — rather than wired in as an explicit validate-then-fix step at a defined point in each workflow.

4 / 5

Progressive Disclosure

The bundle structure itself is excellent — all 8 references, 12 assets, and 8 scripts referenced in the body exist on disk, are one level deep, and are catalogued with descriptions in the Resources section. But the split is undermined by massive inlining: the ~900 lines of CARE/radiology/pathology/ICH-E3/SOAP textbook in SKILL.md duplicate the dedicated reference files, matching 'content that should be separate is inline'.

3 / 5

Total

13

/

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 domain-rich description that names all four report categories with their regulatory standards and mostly natural trigger terms. Its main defects are the absence of any 'Use when...' trigger clause and a second sentence that is vague and truncated mid-word ("regulatory complianc..."), suggesting it was cut off at a length limit.

Suggestions

Replace the truncated "Full support with templates, regulatory complianc..." sentence with concrete actions, e.g. "Validates CARE/ICH-E3 structure and scans for the 18 HIPAA identifiers using bundled scripts and templates".

Add an explicit trigger clause, e.g. "Use when writing case reports, radiology/pathology/laboratory reports, SAE or CSR regulatory documents, or SOAP/H&P/discharge notes".

Add natural synonyms such as "progress notes", "clinical notes", and "adverse event reports" to widen trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables with standards — "case reports (CARE guidelines)", "diagnostic reports (radiology/pathology/lab)", "clinical trial reports (ICH-E3, SAE, CSR)", "patient documentation (SOAP, H&P, discharge summaries)" — matching the 'lists several specific actions; minor gaps' anchor. It is not a 5 because the second sentence, "Full support with templates, regulatory complianc...", is vague filler and is literally truncated mid-word, and the sole action verb is the generic "Write".

4 / 5

Completeness

The 'what' is clearly answered (write four categories of clinical reports with named templates/standards), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The 'when' is only weakly implied by the enumeration of report types.

3 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: "case reports", "radiology", "pathology", "lab", "clinical trial reports", "SOAP", "H&P", "discharge summaries". Not a 5 because common synonyms and variations are missing — "progress notes", "clinical notes", "medical documentation", "patient records" — and abbreviations like SAE/CSR are never expanded into searchable phrases.

4 / 5

Distinctiveness Conflict Risk

Terms like "CARE guidelines", "ICH-E3", "SOAP", and "discharge summaries" carve out a clear clinical-documentation niche with distinct triggers. Not a 5 because case-report writing overlaps with general scientific/medical writing skills, and the description (unlike the body's "When NOT to Use" section) draws no boundary against research manuscripts.

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 (1157 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/Other/clinical-reports/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.