CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lay-summary-gen

Converts complex medical abstracts into plain language summaries for.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/lay-summary-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 body has a real structure and a genuine packaged script, but it is padded with templated boilerplate, broken 'see above' cross-references, and a hardcoded dated path, and its documented run commands do not match the script's actual CLI. The core executable guidance exists but is inaccurate where it matters most — invoking the tool and reading its output.

Suggestions

Replace the non-existent `--help` and `demo` commands with the real invocation, e.g. `python scripts/main.py "<medical abstract text>"`, and align the documented Output Format with the script's actual output keys (original_word_count, summary_word_count, target_audience, key_takeaways, jargon_replaced).

Delete the broken filler lines ('See `## Features` above', 'See `## Prerequisites` above', 'See `## Workflow` above') and the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add no actionable guidance, roughly halving the file.

Signal the bundle concretely: name `references/guidelines.md` and state that it lists the EU CTR / NIH / PLAIN plain-language standards the summaries must follow, instead of the generic 'references/ contains supporting rules' line.

DimensionReasoningScore

Conciseness

The ~200-line body is noticeably verbose: boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements) pad the file, three sections contain broken filler cross-references ('See `## Features` above', 'See `## Prerequisites` above', 'See `## Workflow` above' — all pointing to sections that appear below, not above), and the description is repeated grammatically broken ('Use this skill when the task needs Converts complex medical abstracts...'). It avoids explaining concepts Claude already knows, so it is not severely verbose (1), but several sections could simply be deleted.

2 / 5

Actionability

There is concrete guidance (an Input Parameters table, an Output Format JSON schema, a working `python -m py_compile scripts/main.py` check), but key details are wrong or missing: the 'Audit-Ready Commands' `python scripts/main.py --help` and `python scripts/main.py demo` do not exist as such — the script treats argv[1] as the abstract text, so both commands would summarize the literal strings '--help' and 'demo'. No correct invocation example (`python scripts/main.py "<abstract>"`) is ever shown, and the documented Output Format does not match the script's actual output keys (`original_word_count`/`summary_word_count`/`target_audience` vs the documented `word_count`). This fits 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable anchor at 4.

3 / 5

Workflow Clarity

The Workflow section lists a coherent 5-step sequence with stop-early validation (step 2) and a fallback path (step 5), and Error Handling covers missing inputs and script failure. However, the checkpoints are abstract ('validate that the request matches the documented scope') rather than executable, the run step never shows a working command, and there is no output-verification step that can actually be executed. This sits between the 'steps listed but validation gaps' anchor (3) and the 'clear sequence with most checkpoints present' anchor (4); the broken run commands and generic checkpoints keep it at 3.

3 / 5

Progressive Disclosure

The bundle is real and one level deep (references/guidelines.md with plain-language standards, scripts/main.py), and the body mentions both paths. But references are only signaled generically ('Reference material available in `references/`', 'references/ contains supporting rules, prompts, or checklists') without naming guidelines.md or describing what it holds, and the main SKILL.md inlines large amounts of boilerplate that adds no navigational value. This matches 'some structure; references present but not clearly signaled' rather than the well-signaled anchor at 4.

3 / 5

Total

11

/

20

Passed

Description

53%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 states a clear, third-person capability in a distinct domain, but it is truncated mid-sentence ('...summaries for.'), omits the target audience it clearly intended to name, and contains no 'Use when...' trigger guidance, which caps completeness at 3. Keywords are relevant but miss natural synonyms like 'lay summary'.

Suggestions

Complete the truncated sentence and name the audience, e.g.: 'Converts complex medical abstracts into plain language lay summaries for patients and the public.'

Add an explicit trigger clause: 'Use when the user asks for a lay summary, plain-language version, or patient-friendly explanation of a medical abstract or clinical trial result.'

Include natural synonyms ('lay summary', 'plain English', 'simplify medical jargon') so the skill triggers on the phrases users actually say.

DimensionReasoningScore

Specificity

The description names the domain ('complex medical abstracts') and one concrete action ('Converts ... into plain language summaries'), matching the anchor for 1-2 concrete actions but not comprehensive. It does not list several specific actions (jargon replacement, reading-level targeting, key-takeaway extraction), so it falls short of 4; it is more concrete than the domain-only anchor at 2.

3 / 5

Completeness

There is a clear 'what' ('Converts complex medical abstracts into plain language summaries') but no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It cannot score 4 without any 'when' element, and the 'what' is clear enough to exceed the vague anchors at 1-2 — though the sentence is truncated mid-phrase ('summaries for.'), leaving even the 'what' slightly incomplete.

3 / 5

Trigger Term Quality

'medical abstracts' and 'plain language summaries' are relevant natural terms, but common variations users would actually say are missing: 'lay summary', 'plain English', 'patient-friendly', 'simplify'. This matches the 'some relevant keywords but missing common variations or synonyms' anchor, not the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The medical-abstract-to-plain-language niche is mostly distinct with minor overlap risk against general writing/simplification skills. It lacks the distinctive trigger phrase 'lay summary' that would make it fully unambiguous, keeping it below 5, but it is far more specific than the generic anchors at 2-3.

4 / 5

Total

13

/

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.

Validation — 15 / 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

Path

scientific-skills/Academic Writing/lay-summary-gen/SKILL.md

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.