CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-club-presenter

Generate journal club slides with background, critique, and discussion.

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/journal-club-presenter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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, verifiable bundle (working script and reference file) and a reasonably clear workflow with fallback handling, but it is buried in substantial template boilerplate. Roughly half the content adds no journal-club-specific value, and the actual end-to-end usage of the script (a concrete invocation with inputs and expected output) is never demonstrated.

Suggestions

Cut the boilerplate sections (Key Features, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and the duplicated py_compile command blocks to reduce the body to the workflow, parameters, and error handling.

Show one complete executable example, e.g., `python scripts/main.py --paper paper.pdf --audience graduate --time 20`, along with the output it produces.

Either give `references/audit-reference.md` distinct content (e.g., journal-club critique frameworks or slide-design guidance) or fold its two commands into the body and drop the reference.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded sections: 'Key Features' merely restates the description ('Scope-focused workflow aligned to: Generate journal club slides...'), the same py_compile command appears three times (Example Usage, Quick Check, Audit-Ready Commands), and boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status with a 'Next Review Date', 'Dependencies' followed later by 'Prerequisites: No additional Python packages required') add tokens without adding skill-specific knowledge. It is not 1 because the commands and parameters given are accurate and some sections do carry task-relevant content.

2 / 5

Actionability

There is concrete, executable guidance (`python -m py_compile scripts/main.py`, `python scripts/main.py --help`, a parameters table with `paper_pdf`, `audience_level`, `time_limit`), but key details are missing: no example invocation showing how the parameters are actually passed, no statement of what output the script produces or where it writes it. Much of the body is high-level process direction ('validate the request, choose the packaged workflow, and produce a bounded deliverable') rather than executable steps.

3 / 5

Workflow Clarity

The Workflow section lists a clear 5-step sequence (confirm objective, validate scope, execute, structured result, fallback) with a pre-execution validation checkpoint (Quick Check py_compile), output review in the example run plan, and explicit error-recovery handling ('If execution fails... switch to the fallback path and state exactly what blocked full completion'). It is not 5 because there is no validate-then-fix feedback loop on the produced output, and parts of the sequence are generic process boilerplate rather than journal-club-specific steps.

4 / 5

Progressive Disclosure

Bundle structure is sound on the surface — `scripts/main.py` and `references/audit-reference.md` both exist and are one level deep, and the reference is clearly signaled in a References section. However, the ~190-line body inlines large amounts of generic audit/security/lifecycle material that belongs elsewhere (or nowhere), and `references/audit-reference.md` largely duplicates body content (scope restatement and the same two audit commands), so the structure could be notably better organized.

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 is concise and names a distinct niche with a clear 'what', but it has no explicit 'when to use' clause and omits natural synonyms like 'paper' or 'presentation'. It is serviceable but sits at the mid-level on all dimensions rather than excelling.

Suggestions

Append an explicit trigger clause, e.g., 'Use when the user needs to present a research paper at a journal club, lab meeting, or literature review session.'

Add natural synonyms and keywords such as 'paper', 'presentation', 'article critique', and 'PDF' to broaden trigger coverage.

Enumerate the concrete deliverables (slide outline, background context, key figure explanations, critical evaluation points, discussion questions) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('journal club slides') and one concrete action ('Generate') with three content elements ('background, critique, and discussion'), matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions (e.g., producing slide outlines, figure explanations, or discussion questions), which keeps it below 4, but it is concrete enough to exceed the minimal/generic level 2.

3 / 5

Completeness

The 'what' is clear ('Generate journal club slides with background, critique, and discussion') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and complete, not vague.

3 / 5

Trigger Term Quality

'journal club' and 'slides' are natural, relevant keywords a user would say, but common variations and synonyms are missing ('paper presentation', 'article critique', 'presenting a paper', 'PDF'). This matches the anchor for some relevant keywords while missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

'journal club' is a distinct niche trigger with minor overlap risk only against closely related presentation skills. It is not 5 because the description lacks explicit 'use when' triggers that would fully separate it from generic presentation/slide-generation skills.

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/journal-club-presenter/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.