Tooluck logoTooluck
SKILL.md

lay-summary-for-cross-disciplinary-teams

Agent skill fromaipoch/medical-research-skills

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.

How to install lay-summary-for-cross-disciplinary-teams

install lay-summary-for-cross-disciplinary-teams
# install the medical-research-skills pack with the skills CLI
npx skills add aipoch/medical-research-skills

# or add only this skill to Claude Code: copy the folder

awesome-med-research-skills/Academic Writing/lay-summary-for-cross-disciplinary-teams/

# into

~/.claude/skills/lay-summary-for-cross-disciplinary-teams/ (all projects)

.claude/skills/lay-summary-for-cross-disciplinary-teams/ (one project)

awesome-med-research-skills/Academic Writing/lay-summary-for-cross-disciplinary-teams/SKILL.md

MITFull file
1> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)
2
3# Lay Summary for Cross-Disciplinary Teams
4
5Converts technical research into a structured summary that clinical, wet-lab,
6bioinformatics, product, and management teams can rapidly read and act on.
7
8## Position in the Research Pipeline
9
10This skill sits **midstream**:
11
12- **Upstream** (should exist first): Clear research question, defined objectives,
13 structured results, result narrative
14- **This skill**: Translates that clarified content for non-specialist readers
15- **Downstream** (natural next steps): Slide Deck for Lab Meeting, Graphical
16 Abstract Generator, Reviewer Response Drafter
17
18If the user's research content is still vague or unstructured, prompt them to
19clarify objectives and key findings first. A lay summary built on unclear input
20will sound smooth but be factually imprecise — worse than no summary.
21
22---
23
24## Step 1 — Gather Input
25
26Ask the user to provide any of:
27- Abstract, introduction, or results section
28- Key findings in their own words
29- A study summary or internal report
30
31Also ask: **Who is the primary audience?**
32- `mixed` (default) — all teams listed
33- `clinical` — clinicians, medical staff
34- `wet-lab` — bench scientists, experimentalists
35- `bioinformatics` — computational scientists, data analysts
36- `product` — product managers, translational teams
37- `management` — leadership, funders, executives
38…

Excerpt shown under the repository's MIT license.

More skills in medical-research-skills

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates