CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lay-press-release-writer

Transform academic papers into university press releases for general.

Quality

60%

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-press-release-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill has a genuinely useful core — the input parameter table, output JSON schema, usage commands, and a real one-level reference — buried under heavy generic template padding, duplicated sections, broken cross-references, and contradictory metadata. It reads as an auto-generated scaffold rather than curated guidance, roughly doubling the token cost of what the content actually delivers.

Suggestions

Remove the generic template sections (Security Checklist, Risk Assessment, Evaluation Criteria, Lifecycle Status, Response Template, Output Requirements) or move them to references/; they add tokens without task-specific value.

De-duplicate repeated sections (Quick Check vs Audit-Ready Commands, When to Use vs Input Validation, Example Usage vs Usage) and fix the broken "See `## Usage` above" / "See `## Workflow` above" cross-references, which point to sections that appear later.

Replace the abstract template workflow with the actual task sequence (ingest paper text, extract core findings, draft headline/lead/body, verify scientific accuracy against the notes) and reconcile the contradictory metadata (authors AIPOCH vs OpenClaw, two different descriptions).

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate ("Security Checklist", "Risk Assessment", "Lifecycle Status", "Evaluation Criteria", "Response Template", "Output Requirements") unrelated to the task, plus duplicated sections ("Quick Check" vs "Audit-Ready Commands", "When to Use" vs "Input Validation"). This is noticeably-to-heavily padded, sitting between anchors 1 and 2; it earns 2 because it does not explain concepts Claude already knows, but the padding is extensive.

2 / 5

Actionability

Concrete executable commands are present ("python -m py_compile scripts/main.py", "python scripts/main.py --help", a real CLI invocation with documented flags), backed by an input parameter table and a JSON output schema. Minor gaps: the main example uses a "..." placeholder for paper text, keeping it below anchor 5.

4 / 5

Workflow Clarity

A 5-step workflow is listed and an explicit validation checkpoint (py_compile) plus error-handling/fallback guidance exists, but the steps are generic template language ("Confirm the user objective", "Return a structured result") rather than task-specific steps, and cross-references are broken ("See `## Usage` above" appears before the Usage section). Not 4 because the actual paper-to-press-release sequence is never laid out.

3 / 5

Progressive Disclosure

The body has section structure and a real, clearly signaled one-level reference (references/audit-reference.md, which exists), but substantial boilerplate and duplicated content are inlined in SKILL.md that belongs elsewhere or nowhere, and contradictory metadata (author "AIPOCH" vs "OpenClaw", two different descriptions) hurts navigation. Not 4 because the organization gaps are more than minor.

3 / 5

Total

12

/

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 communicates a clear, concrete purpose but stops there: it is grammatically truncated, lists only one action, and entirely lacks a "Use when..." trigger clause. It is serviceable but clearly below the standard of the good examples, which pair a what with explicit when-to-use triggers.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to turn a paper, abstract, or research findings into a press release, news release, or lay summary for the public."

Fix the truncated ending "for general." to "for general audiences" and mention the audience variants (public, alumni, media) the skill supports.

Broaden natural trigger terms to include synonyms such as "press release", "news release", "science news", and "research summary".

DimensionReasoningScore

Specificity

"Transform academic papers into university press releases for general." names the domain and one concrete action, matching anchor 3. It is not 4 because only a single action is described and the sentence is truncated ("for general."), leaving coverage incomplete.

3 / 5

Completeness

The "what" is clear (transform academic papers into university press releases) but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

"academic papers" and "university press releases" are relevant natural keywords, but common variations users would say ("press release", "science news", "news release", "lay summary") are missing, matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The academic-paper-to-press-release niche is fairly distinct and unlikely to trigger the wrong skill, but the truncated phrasing and potential overlap with general science-writing/summarization skills keep it below anchor 5.

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-press-release-writer/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.