Skills for Real Engineers. Straight from my .agents directory.
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
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 file1> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills)23# Lay Summary for Cross-Disciplinary Teams45Converts technical research into a structured summary that clinical, wet-lab,6bioinformatics, product, and management teams can rapidly read and act on.78## Position in the Research Pipeline910This skill sits **midstream**:1112- **Upstream** (should exist first): Clear research question, defined objectives,13 structured results, result narrative14- **This skill**: Translates that clarified content for non-specialist readers15- **Downstream** (natural next steps): Slide Deck for Lab Meeting, Graphical16 Abstract Generator, Reviewer Response Drafter1718If the user's research content is still vague or unstructured, prompt them to19clarify objectives and key findings first. A lay summary built on unclear input20will sound smooth but be factually imprecise — worse than no summary.2122---2324## Step 1 — Gather Input2526Ask the user to provide any of:27- Abstract, introduction, or results section28- Key findings in their own words29- A study summary or internal report3031Also ask: **Who is the primary audience?**32- `mixed` (default) — all teams listed33- `clinical` — clinicians, medical staff34- `wet-lab` — bench scientists, experimentalists35- `bioinformatics` — computational scientists, data analysts36- `product` — product managers, translational teams37- `management` — leadership, funders, executives38…
Excerpt shown under the repository's MIT license.
More skills in medical-research-skills
Similar skill repositories
An agentic skills framework & software development methodology that works.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Public repository for Agent Skills
Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
An AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
