CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medical-case-interpreter

Generates compliant medical case report articles for WeChat.

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/medical-case-interpreter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 generation rules (privacy anonymization, article structure, word limits, drug naming) are specific and genuinely actionable. However, the file is roughly doubled in size by generic template boilerplate and contains internal contradictions about whether a validation script is part of the workflow, which undermine both conciseness and workflow clarity.

Suggestions

Delete the generic template sections (Key Features, Dependencies, Implementation Details, Required Inputs, Deterministic Output Rules, Completion Checklist) that duplicate the generation rules — keep only skill-specific content.

Resolve the validation contradiction: pick either the scripts/validate_skill.py path (and document its actual --check flag) or the 'no script required' statement, not both.

Fix the hardcoded example path ("20260316/scientific-skills/Others/medical-case-interpreter") to reference the actual skill directory, and add one short worked example of the expected article output.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template padding ("Key Features", "Dependencies", "Implementation Details", "Required Inputs", "Completion Checklist") that restates the same scope/safety boilerplate in multiple sections, e.g., "Scope-focused workflow aligned to: Generates compliant medical case report articles for WeChat" and "Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable." This matches 'noticeably verbose; several padded sections' — it does not extensively explain concepts Claude already knows (not score 1), but it goes well beyond the 'some unnecessary explanation' of score 3.

2 / 5

Actionability

The Generation Rules give concrete, executable guidance: "Convert all patient names to 'Patient (Gender, Age)'", "Strictly under 200 words", exact headers ("## Case Report", "### Patient Information", "### Treatment Process"), and the drug-mapping rule. Not score 5 because there is no worked example of the output article and the script commands reference a path that does not match the bundle; clearly above score 3 since the guidance is directly executable rather than pseudocode.

4 / 5

Workflow Clarity

A sequence exists (Step 1: Privacy & Data Cleaning → Step 2: Content Generation → output contract), but the validation story is contradictory: "Validation Shortcut" instructs "Run python scripts/validate_skill.py --help" while "Quick Validation" states "No local script validation step is required for this skill", and the body's own description says it works "without requiring external scripts." Checkpoints are therefore present but incoherent, matching 'sequence present but checkpoints missing or implicit'; not 4 because the contradiction is more than a minor gap.

3 / 5

Progressive Disclosure

The body is well-sectioned with headers and its one bundle reference (scripts/validate_skill.py) is a real file, but everything lives inline in a 166-line SKILL.md — the boilerplate half should be trimmed or split, and "Example Usage" hardcodes an unrelated path ("20260316/scientific-skills/Others/medical-case-interpreter"). This fits 'some structure but could be better organized'; not 4 because substantial content is inlined that does not belong in the overview file.

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 is concise, specific, and third-person, with a clear single-action 'what' and a well-defined niche. Its main weaknesses are the complete absence of any 'Use when' trigger guidance and limited keyword variation, leaving a user or Claude little to distinguish when to invoke it versus a sibling medical-writing skill.

Suggestions

Add a 'Use when...' clause, e.g., "Use when the user provides clinical case data and asks for a WeChat/公众号 case report article or 病例报道."

Surface 1-2 more concrete capabilities from the body, such as anonymizing patient identifiers and enforcing the fixed article structure (Foreword, Case Report, Treatment).

Include natural synonyms a user would say — "case study", "medical writing", "公众号 article" — to improve trigger matching.

DimensionReasoningScore

Specificity

"Generates compliant medical case report articles for WeChat" names the domain (medical case reports, WeChat) and one concrete action (generates articles), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not 2 because the action and deliverable are specific rather than generic, and not 4/5 because only a single action is listed — anonymization, formatting, and structuring capabilities from the body are absent.

3 / 5

Completeness

The description has a clear 'what' ("Generates compliant medical case report articles for WeChat") with no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is clear and specific rather than vague; not 4 because 'when' is entirely absent rather than merely implicit or weak.

3 / 5

Trigger Term Quality

Keywords like "medical case report", "articles", and "WeChat" are relevant natural terms, but common variations are missing (e.g., "case study", "病例报告", "公众号/official account", "medical writing"). This matches the anchor for some relevant keywords missing synonyms; it is above 'one or two generic keywords' (score 2) but lacks the broad coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

The niche — compliant medical case report articles for the WeChat platform — is specific and mostly distinct. Minor overlap risk remains with closely related medical-writing/WeChat-article skills (the skill comes from a medical-research-skills collection where siblings plausibly cover similar article types), so it is not 5; it is clearly more distinct than the broad overlap examples at score 3.

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