CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-case-report-generator

Generates a patient-friendly medical case report tweet from case images and disease name. Use when the user provides a medical case image and wants a structured report or tweet.

Quality

75%

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/medical-case-report-generator/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 core six-step workflow is well designed — sequenced, concrete, and format-driven — but it is surrounded by large amounts of generic template boilerplate that inflates token cost without adding domain value, plus internally contradictory validation guidance and a broken cross-reference. Trimming the boilerplate and reconciling the validation sections would substantially improve the skill.

Suggestions

Remove the generic template sections (Key Features, Implementation Details, Output Contract, Deterministic Output Rules, etc.) that restate the description or state obvious process rules; this would cut the file roughly in half and let the actual Workflow lead the document.

Reconcile the contradictory validation guidance: either document the script's real interface (`python scripts/validate_skill.py --check`) in one place or delete both the "Validation Shortcut" and "Quick Validation" sections.

Fix navigation errors: "See `## Workflow` above for related details" should point below (or be deleted), and drop the pipeline-specific `cd "20260316/scientific-skills/..."` path from Example Usage.

DimensionReasoningScore

Conciseness

The ~290-line body wraps a ~165-line core workflow in heavy template boilerplate ("Key Features", "Implementation Details", "Output Contract", "Deterministic Output Rules", "Completion Checklist") that restates the description verbatim twice and adds filler like "Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable". This matches the anchor for several unnecessary padded sections; not 3 because the padding is close to half the file.

2 / 5

Actionability

The workflow gives concrete, executable guidance: exact output templates, per-section field lists, and hard rules ("Core symptoms (≤5)", "18-25 characters", "Start with prefix: 【Case Report】". Not 5 because the validation-script guidance is confusing — the body documents `--help` while the script's actual `--check` flag is never mentioned, and Example Usage includes a pipeline-specific `cd` path irrelevant to users.

4 / 5

Workflow Clarity

Six clearly sequenced steps each specify Input/Action/Output, backed by a completion checklist, failure handling, and input-validation rules. Not 5 because the validation guidance contradicts itself — "Validation Shortcut" says to run `python scripts/validate_skill.py --help` while "Quick Validation" says "No local script validation step is required for this skill" — and "See `## Workflow` above for related details" points to a section that appears below.

4 / 5

Progressive Disclosure

A single-file monolith with no reference files; the one referenced bundle path (`scripts/validate_skill.py`) is real, but the actual workflow is buried under ~50 lines of boilerplate and a broken internal pointer. Structure exists (clear section headers) but the skill is well over 50 lines and the treatment-option and disease-intro detail could live in reference files, matching the mid anchor.

3 / 5

Total

13

/

20

Passed

Description

83%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: it clearly and explicitly states what the skill does, its inputs, and when to use it, with natural trigger terms and a distinct medical niche. Only minor refinements — broader synonyms and niche-qualified triggers — would make it top-tier.

DimensionReasoningScore

Specificity

"Generates a patient-friendly medical case report tweet from case images and disease name" specifies the deliverable, both inputs, and the output style, going beyond naming 1-2 bare actions. Not 5 because it is one composite action and omits sub-capabilities like text extraction and anonymization.

4 / 5

Completeness

It explicitly answers both what ("Generates a patient-friendly medical case report tweet from case images and disease name") and when ("Use when the user provides a medical case image and wants a structured report or tweet") with concrete trigger phrases, matching the top anchor's structure.

5 / 5

Trigger Term Quality

"Use when the user provides a medical case image and wants a structured report or tweet" supplies natural trigger phrases like "medical case image", "structured report", and "tweet". A few natural variations (e.g., "case summary", "diagnosis report", "social media post") are missing, so it falls short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

The medical-case-report-from-images niche is mostly distinct with specific triggers, but "report" and "tweet" leave minor overlap risk with general medical summarization or tweet-writing skills. Not 5 because the trailing triggers are not fully niche-qualified.

4 / 5

Total

17

/

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/medical-case-report-generator/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.