CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-skills

Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal recommendation/matching, submission strategy, PubMed search, or similar-literature statistics.

Quality

79%

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/Evidence Insight/journal-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured skill with a clear sequenced workflow, concrete runnable command, and a properly disclosed three-file bundle (script, CSV template, reference guide) all verified to exist. The main drag is a large block of generic template boilerplate (Output Contract, Input Validation, Quick Validation, Required Inputs) that pads the token budget and blunts both conciseness and the overview's focus.

Suggestions

Delete or collapse the generic Output Contract / Input Validation / Quick Validation sections into a few skill-specific lines (e.g., name the exact core fields the final table must contain).

Add one example row filled into assets/journal_recommendation_template.csv so the expected output is copy-paste concrete.

Add an explicit validation loop for the PubMed step: what to do when the query returns too few similar records (e.g., broaden MeSH terms / retry) before proceeding to screening.

DimensionReasoningScore

Conciseness

The core sections (When to Use, Dependencies, Example Usage, Implementation Details) are efficient, but roughly a third of the body is generic template boilerplate ("Output Contract: ...Structured result or target file aligned with this skill's objective", "Input Validation", "Quick Validation", "Required Inputs" rows like "Depends on task") that adds tokens without journal-specific information and overlaps the Failure Handling / User Checkpoints sections. Not a 2 because no section explains concepts Claude doesn't know and the padding is formulaic rather than rambling.

3 / 5

Actionability

Gives an executable command ("python scripts/pubmed_journal_recommender.py"), concrete config items (EMAIL, API_KEY), a real template path, and a five-step usage flow tied to actual bundle files. Not a 5 because details like the exact config format, an example filled template row, or expected script output are missing, and "Output directory (if the script supports/requests it)" is vague.

4 / 5

Workflow Clarity

The workflow is clearly sequenced twice (Example Usage steps 1-5 and the four-phase Implementation Details), with user checkpoints before batch/long-running PubMed queries and a Quick Validation section. Not a 5 because validation steps are generic assertions rather than explicit verify-then-proceed loops (e.g., checking the script's journal distribution output before screening, or how to handle an empty PubMed result set).

4 / 5

Progressive Disclosure

The body is an overview that cleanly points one level deep to real, clearly signaled bundle files: scripts/pubmed_journal_recommender.py, assets/journal_recommendation_template.csv, and references/guide.md (verified to exist, with no nested references). Not a 5 because Implementation Details partially duplicates guide.md content (output columns, quality checks) and the generic sections dilute the overview's navigational clarity.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description: concrete third-person capability statement paired with an explicit 'use when' trigger clause covering natural phrasings. The only weaknesses are slightly incomplete trigger synonym coverage and the somewhat broad 'PubMed search' trigger that marginally raises conflict risk.

Suggestions

Add common user phrasings as triggers, e.g. 'which journal should I submit to', 'journal selection', or 'find a suitable journal'.

Narrow the 'PubMed search' trigger (e.g. 'PubMed-based similar-literature search') so it does not fire for generic literature-search requests.

DimensionReasoningScore

Specificity

"Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature" names the domain and several concrete actions (recommend journals, analyze topic/abstract, compute journal distribution of similar literature) in third person. Not a 5 because coverage stops short of the downstream actions the body actually supports (screening constraints, ranked output with rationale/risks).

4 / 5

Completeness

It explicitly answers both: what ("Recommends target journals... by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature") and when ("use when users ask for journal recommendation/matching, submission strategy, PubMed search, or similar-literature statistics") with concrete trigger phrases, matching the anchor-5 pattern. Not below 5 since neither half is vague or merely implied.

5 / 5

Trigger Term Quality

Natural trigger phrases like "journal recommendation/matching", "submission strategy", and "PubMed search" are ones users would plausibly say. Not a 5 because common variations such as "which journal should I submit to", "journal selection", or "find a journal for my paper" are missing.

4 / 5

Distinctiveness Conflict Risk

The journal-recommendation/PubMed-distribution niche is clear and mostly distinct. Minor overlap risk comes from the broad "PubMed search" trigger, which could fire for a generic literature-search request that does not want journal matching; not a 5 for that reason, clearly above the 3 anchor whose overlap risk is with many similar 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.

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/Evidence Insight/journal-skills/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.