CtrlK
BlogDocsLog inGet started
Tessl Logo

lay-summary-for-cross-disciplinary-teams

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and actionable with a clear validated workflow and proper progressive disclosure; its only modest weakness is minor over-explanation and delegation of executable detail to external files.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, using short directives, a table, and checklists, though a few explanatory lines (e.g. the "worse than no summary" rationale) could be trimmed.

4 / 5

Actionability

It provides concrete, specific guidance — an audience enum with defaults, a 5-element extraction table, explicit writing principles with quantification examples ("3-fold higher", "in 4 of 6 subtypes"), and pointers to real template/reference files — but delegates the executable specifics to external files rather than inlining them.

4 / 5

Workflow Clarity

A clear four-step sequence (Gather → Extract → Write → Quality Check) is paired with an explicit validation checklist and a feedback loop ("If a check fails, revise before presenting") plus upstream input validation, matching the top anchor.

5 / 5

Progressive Disclosure

The body is a well-organized overview that clearly signals two one-level-deep, real bundle files (assets/output-template.md and references/audience-guide.md) and summarizes them in a References section, giving easy navigation.

5 / 5

Total

18

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong, with an explicit trigger list and a clear what/when structure; its only weakness is specificity, since it describes a single transformation rather than multiple concrete actions.

DimensionReasoningScore

Specificity

It names the domain and one concrete action — "Rewrites technical research content into a structured lay summary that cross-disciplinary teams can quickly understand and act on" — but does not enumerate multiple distinct actions, so it stops at domain + 1-2 concrete actions rather than comprehensive coverage.

3 / 5

Completeness

It clearly states what the skill does (rewrites into a structured lay summary) and gives an explicit "Use when..." clause plus concrete trigger phrases, satisfying both halves with concrete triggers.

5 / 5

Trigger Term Quality

An explicit "Trigger on:" clause lists seven natural phrases ("lay summary", "explain my research to the team", "non-technical summary", "translate my findings", "align our team on the study") covering synonyms and paraphrases a user would plausibly say.

5 / 5

Distinctiveness Conflict Risk

The cross-disciplinary/lay-summary framing and specific audience list define a clear niche with distinct triggers, but there is minor overlap risk with general research-summarization or writing skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.