agentleFS
qinyan-aiqinyan-ai/qinyan-academic-skills/skills/02-科学写作与学术交流/medical-imaging-review/SKILL.md

medical-imaging-review

Skill80 starsChanged 8 months agoMITView on GitHub

Write comprehensive literature reviews for medical imaging AI research. Use when writing survey papers, systematic reviews, or literature analyses on topics like segmentation, detection, classification in CT, MRI, X-ray, ultrasound, or pathology imaging. Triggers on requests for "review paper", "survey", "literature review", "综述", "systematic review", or mentions of writing academic reviews on deep learning for medical imaging.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write comprehensive literature reviews following a systematic 7-phase workflow.

    line 33
  2. Distinctive:

    Avoid absolutes: Never say "X is the best method"

    line 52
  3. Distinctive:

    Citation support: Every claim needs reference

    line 53
  4. Distinctive:

    Use multi-source strategy for comprehensive coverage:

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Medical Imaging AI Literature Review Skill

Write comprehensive literature reviews following a systematic 7-phase workflow.

Quick Start

  1. Initialize project with three core files:
    • CLAUDE.md - Writing guidelines and terminology
    • IMPLEMENTATION_PLAN.md - Staged execution plan
    • manuscript_draft.md - Main manuscript
  2. Follow the 7-phase workflow (see references/WORKFLOW.md)
  3. Use domain-specific templates (see references/DOMAINS.md)

Core Principles

Writing Style

  • Hedging language: "may", "suggests", "appears to", "has shown promising results"
  • Avoid absolutes: Never say "X is the best method"
  • Citation support: Every claim needs reference
  • Limitations: Each method section needs a Limitations paragraph

Required Elements

  • Key Points box (3-5 bullets) after title
  • Comparison table for each major section
  • Performance metrics: Dice (0.XXX), HD95 (X.XX mm)
  • Figure placeholders with detailed captions
  • References: 80-120 typical, organized by topic

Paragraph Structure

Topic sentence (main claim)
  → Supporting evidence (citations + data)
  → Analysis (critical evaluation)
  → Transition to next paragraph

Literature Sources

Use multi-source strategy for comprehensive coverage:

SourceBest ForTools
ArXivLatest DL methods, preprintssearch_papers, read_paper
PubMedClinical validation, peer-reviewedpubmed_search_articles
ZoteroExisting library, organized refszotero_search_items

For MCP configuration details, see references/MCP_SETUP.md.


Standard Review Structure

# [Title]: State of the Art and Future Directions

## Key Points
- [3-5 bullets summarizing main findings]

## Abstract

## 1. Introduction
### 1.1 Clinical Background
### 1.2 Technical Challenges
### 1.3 Scope and Contributions

## 2. Datasets and Evaluation Metrics
### 2.1 Public Datasets (Table 1)
### 2.2 Evaluation Metrics

## 3. Deep Learning Methods
### 3.1 [Category 1]
### 3.2 [Category 2]
(Table 2: Method Comparison)

## 4. Downstream Applications

## 5. Commercial Products & Clinical Translation (Table 3)

## 6. Discussion
### 6.1 Current Limitations
### 6.2 Future Directions

## 7. Conclusion

## References

Method Description Template

### 3.X [Method Category]

[1-2 paragraph introduction with motivation]

**[Method Name]:** [Author] et al. [ref] proposed [method], which [innovation]:
- [Key component 1]
- [Key component 2]
Achieves Dice of X.XX on [dataset].

**Limitations:** Despite advantages, [category] methods face:
(1) [limit 1]; (2) [limit 2].

Citation Patterns

# Data citation
"...achieved Dice of 0.89 [23]"

# Method citation
"Gu et al. [45] proposed..."

# Multi-citation
"Several studies demonstrated... [12, 15, 23]"

# Comparative
"While [12] focused on..., [15] addressed..."

Reference Files

FilePurpose
references/WORKFLOW.mdDetailed 7-phase workflow
references/TEMPLATES.mdCLAUDE.md and IMPLEMENTATION_PLAN.md templates
references/DOMAINS.mdDomain-specific method categories
references/MCP_SETUP.mdMCP server configuration
references/QUALITY_CHECKLIST.mdPre-submission quality checklist

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.