CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

77%

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.

The body delivers a clear, actionable journal-recommendation workflow with well-organized one-level-deep references to real bundle files. Its main weakness is a substantial amount of generic, non-journal-specific boilerplate that inflates token cost without adding skill-specific value.

Suggestions

Trim or collapse the generic boilerplate sections ('When Not to Use', 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', 'Quick Validation') into a concise, journal-specific checklist, since much of it overlaps and is not specific to this skill.

Replace the generic 'Required Inputs' table with the actual required inputs (manuscript title + abstract, EMAIL config, optional API_KEY) and their if-missing handling.

Show a small filled-in example of the journal_recommendation_template.csv output so the recommendation step is copy-paste concrete rather than described abstractly.

DimensionReasoningScore

Conciseness

The skill-specific sections are efficient, but a large block of generic boilerplate ('When Not to Use', 'Required Inputs' table, 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', 'Quick Validation') is not journal-specific and could be tightened.

3 / 5

Actionability

Provides a concrete runnable command ('python scripts/pubmed_journal_recommender.py') and references real bundle files (script, CSV template, guide); minor gaps include manual CONFIG editing and abstract template-usage instructions.

4 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced (Example Usage 1–5, Implementation Details 1–4) with explicit user checkpoints and validation guidance, though the validation steps are somewhat generic rather than concrete.

4 / 5

Progressive Disclosure

References to the bundled script, CSV template, and guide.md are one level deep and clearly signaled, with content appropriately split; minor gaps from inlined generic boilerplate and a sparse guide.md.

4 / 5

Total

15

/

20

Passed

Description

87%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 well-crafted description that clearly states a specific capability and its triggering conditions in third person. It is concrete, distinct, and answers both what and when explicitly.

DimensionReasoningScore

Specificity

Names the concrete mechanism ('analyzing the paper topic/abstract and the journal distribution of similar PubMed literature') rather than a generic action, with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Recommends target journals for manuscript submission…') and when ('use when users ask for…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('journal recommendation/matching', 'submission strategy', 'PubMed search', 'similar-literature statistics'); good coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (manuscript-to-journal matching via PubMed literature analysis) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

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.

Validation15 / 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
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.