lay-press-release-writer

Transform academic papers into university press releases for general.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./scientific-skills/Academic Writing/lay-press-release-writer/SKILL.md

Quality

Discovery

32%

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

This description identifies a clear use case (academic paper to press release conversion) but is incomplete and lacks sufficient detail. The truncated ending ('for general') suggests an error, and the absence of explicit trigger guidance significantly limits Claude's ability to select this skill appropriately. The description needs expansion on both capabilities and usage triggers.

Suggestions

Complete the truncated description and add a 'Use when...' clause with trigger terms like 'press release', 'media announcement', 'publicize research', 'science news'

Add specific capabilities such as 'simplifies technical jargon', 'writes attention-grabbing headlines', 'highlights key findings for lay audiences'

Include keyword variations like 'research paper', 'journal article', 'scientific study', 'media release', 'news release' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (academic papers, press releases) and one action (transform), but lacks detail on what transformation entails - no mention of specific capabilities like summarizing findings, writing headlines, adapting technical language, etc.	2 / 3
Completeness	Only addresses 'what' at a high level (transform papers to press releases) but completely lacks any 'Use when...' clause or explicit trigger guidance. The description also appears truncated ('for general' is incomplete).	1 / 3
Trigger Term Quality	Contains relevant keywords like 'academic papers', 'university', and 'press releases' that users might say, but missing common variations like 'research paper', 'journal article', 'media release', 'news release', or 'science communication'.	2 / 3
Distinctiveness Conflict Risk	The academic-to-press-release niche is fairly specific, but could overlap with general writing/editing skills or other document transformation skills. The incomplete ending ('for general') weakens distinctiveness.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

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

This skill is heavily over-engineered with excessive boilerplate that obscures the core task. It treats a content transformation task (academic paper → press release) as primarily a script execution task, providing no actual guidance on press release writing craft. The document is roughly 3-4x longer than necessary due to redundant sections and generic templates.

Suggestions

Remove redundant sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't help Claude write better press releases

Add concrete guidance on press release writing: how to identify key findings, craft headlines, write accessible explanations of technical concepts, and structure the inverted pyramid

Consolidate the scattered workflow sections into a single, clear sequence with quality validation checkpoints for the generated content

Remove self-referential text like 'See ## Usage above' and organize content so each section stands alone

Dimension	Reasoning	Score
Conciseness	Extremely verbose with massive redundancy - the same information is repeated across multiple sections (e.g., 'Example Usage' references 'Usage' above, 'Implementation Details' references 'Workflow' above). Contains extensive boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add little value for the core task of writing press releases.	1 / 3
Actionability	Provides concrete CLI commands and JSON output format, but the actual press release transformation logic is entirely delegated to an opaque `scripts/main.py`. No guidance on how to actually write a good press release, extract key findings, or craft compelling headlines - just wrapper instructions for running a script.	2 / 3
Workflow Clarity	Multiple workflow sections exist but are redundant and scattered. The 'Example run plan' and 'Workflow' sections provide steps, but validation is limited to syntax checking (`py_compile`) rather than output quality validation. No feedback loop for reviewing press release quality or iterating on content.	2 / 3
Progressive Disclosure	References external files (references/audit-reference.md, requirements.txt) appropriately, but the main document itself is a monolithic wall of text with poor organization. Many sections are redundant or self-referential ('See ## Usage above'), creating confusion rather than clarity.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: aipoch/medical-research-skills
Commit: 4a48721

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.