lay-summary-for-cross-disciplinary-teams

lay-summary-for-cross-disciplinary-teams is a skill for Claude Code, Codex from aipoch/medical-research-skills. It costs 156 tokens per session (925 once invoked), scanned A, original, MIT.

A writing skill that turns technical research into a clear summary for people outside the writer’s specialty, such as clinicians, laboratory scientists, data specialists, and managers.

In plain words
What is it for?
Use it to rewrite abstracts, results, study summaries, or internal reports for a chosen cross-disciplinary audience.
Why use it?
It helps mixed teams understand research without needing to know its field-specific terms, while flagging when the source material is too unclear.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to rewrite abstracts, results, study summaries, or internal reports for a chosen cross-disciplinary audience.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams
About the project

Medical Research Agent Skills is a library of agent instructions for medical and biomedical research, covering evidence analysis, study protocol design, data analysis, and academic writing. Researchers use it to guide compatible coding agents through common scientific workflows. The catalogue contains many of the library's skills and commands.

aipoch/medical-research-skills · 1,860 stars · on GitHub · aipoch.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add aipoch/medical-research-skills --skill lay-summary-for-cross-disciplinary-teams
Clone the repo
git clone --depth 1 https://github.com/aipoch/medical-research-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for lay-summary-for-cross-disciplinary-teams

README.md
[![agentmods](https://agentmods.dev/badge/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams/github.svg)](https://agentmods.dev/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams)
Your own site
<a href="https://agentmods.dev/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams"><img src="https://agentmods.dev/badge/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for lay-summary-for-cross-disciplinary-teams

Your own site · 80×15
<a href="https://agentmods.dev/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams"><img src="https://agentmods.dev/badge/skills/aipoch/medical-research-skills/lay-summary-for-cross-disciplinary-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.00925
Opus 5 $0.00078 $0.00463
Sonnet 5 $0.00031 $0.00185
Haiku 4.5 $0.00016 $0.00093

Measured 13d ago against content hash 0f109e401f3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

lay-summary-for-cross-disciplinary-teams scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

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

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Source: https://github.com/aipoch/medical-research-skills

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 listed
  • clinical — clinicians, medical staff
  • wet-lab — bench scientists, experimentalists
  • bioinformatics — computational scientists, data analysts
  • product — product managers, translational teams
  • management — 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:

Element What to find
Study goal Why was this done? What problem does it address?
System / population What was studied? (patients, cells, datasets, samples…)
Main finding What did the data show? Be specific — avoid vague positives.
Evidence boundary What can this support? What remains uncertain or untested?
Next action What should each team know or do because of this?

Read the full file on GitHub · 110 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 110 lines · 156 tokens per session scan A 0f109e401f3f

Subscribe to this mod's changes

lay-summary-for-cross-disciplinary-teams is a skill published in the GitHub repository aipoch/medical-research-skills (1,860 stars, last pushed 1mo ago), licensed MIT. It adds 156 tokens to every session and 925 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.