Lay Summary For Cross Disciplinary Teams
Rewrites technical research content into a structured lay summary that...
Install
npx skills add aipoch/medical-research-skills --skill lay-summary-for-cross-disciplinary-teams -g -a claude-code -y- Repository
- aipoch/medical-research-skills2k
- Category
- Documents
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Lightabout 817 tokens
- Runs scripts
- No, instructions only
What it does
Rewrites technical research content into a structured lay summary that cross-disciplinary teams can quickly understand and act on. Use when the user wants to explain research to colleagues outside their specialty, clinicians, wet-lab scientists, bioinformaticians, product managers, or leadership. Trigger on: "lay summary", "explain my research to the team", "non-technical summary", "cross-disciplinary summary", "translate my findings", "align our team on the study", or any request to communicate research goals, findings, or next steps to a mixed or non-specialist audience. Part of the AIPOCH Academic Writing skill hub. Sits midstream: after research content is clarified, before downstream deliverables like slide decks or graphical abstracts.
Lay Summary for Cross-Disciplinary Teams
Converts technical research into a structured summary that clinical, wet-lab, bioinformatics, product, and management teams can rapidly read and act on.
Position in the Research Pipeline
This skill sits midstream:
- Upstream (should exist first): Clear research question, defined objectives, structured results, result narrative
- This skill: Translates that clarified content for non-specialist readers
- Downstream (natural next steps): Slide Deck for Lab Meeting, Graphical Abstract Generator, Reviewer Response Drafter
If the user's research content is still vague or unstructured, prompt them to clarify objectives and key findings first. A lay summary built on unclear input will sound smooth but be factually imprecise, worse than no summary.
Step 1, Gather Input
Ask the user to provide any of:
- Abstract, introduction, or results section
- Key findings in their own words
- A study summary or internal report
Also ask: Who is the primary audience?
mixed(default), all teams listedclinical, clinicians, medical staffwet-lab, bench scientists, experimentalistsbioinformatics, computational scientists, data analystsproduct, product managers, translational teamsmanagement, leadership, funders, executives
If unspecified, use mixed and include all relevant audience bullets.
Step 2, Extract Core Structure
Before writing, internally map the input to these five elements:
