Individual skill

medical-review-writer-architect

A multi-stage workflow for writing long-form medical reviews; used when the user needs to build an outline based on PubMed literature, write chapter by chapter, perform supplementary searches, and format citations; input is the review topic and project directory, output is a c...

scientific-skills/Academic Writing/medical-review-writer-architect/SKILL.md

Read pinned source

Source commit 686e09dfdb45d9fa1a08664f06bb93769b3c9d91

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,042
Repository last updated
Sep 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)


# Medical Review Writer (Architect)

## When to Use

- The user explicitly wants to write a medical review, narrative review, or long-form review based on PubMed evidence.
- The user accepts a multi-stage process of outline, search, chapter-by-chapter writing, verification, and formatting.
- The user needs real intermediate files, rather than generating the final long document in one shot within the conversation.

## When Not to Use

- When the user only needs a summary, single paragraph review, or brief background introduction, do not launch the full workflow.
- When the user has no topic, target audience, language requirements, or project directory, do not start writing directly — first collect the minimum inputs.
Back to top