Medical Case Interpreter

Source: https://github.com/aipoch/medical-research-skills

When to Use

• Use this skill when the request matches its documented task boundary.
• Use it when the user can provide the required inputs and expects a structured deliverable.
• Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming.

Key Features

• Scope-focused workflow aligned to: Generates compliant medical case report articles for WeChat.
• Packaged executable path(s): scripts/validate_skill.py.
• Structured execution path designed to keep outputs consistent and reviewable.

Dependencies

• Python: 3.10+. Repository baseline for current packaged skills.
• Third-party packages: not explicitly version-pinned in this skill package. Add pinned versions if this skill needs stricter environment control.

Example Usage

cd "20260316/scientific-skills/Others/medical-case-interpreter"
python -m py_compile scripts/validate_skill.py
python scripts/validate_skill.py --help

Example run plan:

1. Confirm the user input, output path, and any required config values.
2. Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
3. Run python scripts/validate_skill.py with the validated inputs.
4. Review the generated output and return the final artifact with any assumptions called out.

Implementation Details

• Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
• Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
• Primary implementation surface: scripts/validate_skill.py.
• Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
• Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.

Validation Shortcut

Run this minimal command first to verify the supported execution path:

python scripts/validate_skill.py --help

Medical Case Interpreter

Description

This skill acts as a Senior Medical Expert to transform raw clinical data into a professional WeChat case report article. It enforces strict privacy, formatting, and style rules without requiring external scripts.

Inputs

• Case Data: Raw text or files containing patient history, exams, and treatment.
• Product Name: The target drug/product to highlight.
• Doctor Info: Name and affiliation of the expert.
• Drug Mapping: (Optional) Specific Chinese translations for English drug names.

Generation Rules

When executing this skill, the Agent must follow these steps and constraints:

Step 1: Privacy & Data Cleaning (Mental Check)

• Strictly Anonymize: Convert all patient names to "Patient (Gender, Age)".
• Remove Dates: Convert specific admission dates to relative time (e.g., "Day 1", "Month 3").
• Hospital Info: Do not mention specific hospital ID numbers.

Step 2: Content Generation

Generate the article in a single pass using the following structure:

1. Title

• Create an engaging, professional title suitable for a medical audience.

2. Foreword

• Constraint: Strictly under 200 words.
• Format: Single paragraph.
• Content: Summarize the case significance and hook the reader. Do not reveal the full outcome yet.

3. Case Report Body

• Header: Start with ## Case Report.
• Structure:
  • ### Patient Information: History, Symptoms (Anonymized).
  • ### Auxiliary Examination: Key lab results and imaging.
  • ### Diagnosis: Clear clinical diagnosis.
  • ### Treatment Process: Detail the regimen. Highlight the [Product Name] usage here.
  • ### Summary: Clinical takeaways.
• Drug Names: If [Drug Mapping] is provided, ALWAYS use the specified Chinese names.

Example Prompt for User

"Please generate a case report for [Product Name] based on the attached file. The doctor is [Doctor Name]."

When Not to Use

• Do not use this skill when the required source data, identifiers, files, or credentials are missing.
• Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
• Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.