CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-matchmaker

Analyzes academic paper abstracts to recommend optimal journals for submission, considering impact factors, scope alignment, and domain expertise.

Quality

63%

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-matchmaker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 contains genuinely actionable material — a parameter table, runnable commands, a validated workflow with fallback handling, and real reference files — but it is wrapped in heavy template boilerplate and self-referential filler that roughly doubles its length. Tightening it to the domain-specific sections (Usage, How It Works, References, Workflow, Error Handling) and moving meta-content out of SKILL.md would substantially improve it.

Suggestions

Cut the boilerplate and duplication: remove the verbatim description repeats in "When to Use"/"Key Features" and delete or split out generic sections (Key Features, Implementation Details, Lifecycle Status, Security Checklist, Evaluation Criteria, Response Template) into a separate file or remove them.

Fix navigation defects: replace forward-dangling "See `## Prerequisites` above" pointers (which appear before their targets), remove the hardcoded cd into "20260318/scientific-skills/Evidence Insight/journal-matchmaker", and ship or delete the missing requirements.txt.

Reconcile the CLI documentation: document the script's actual --file flag and correct the "--abstract \"abstract.txt\"" example so examples are copy-paste consistent with the parameter table.

DimensionReasoningScore

Conciseness

The frontmatter description is repeated verbatim four times ("Analyzes academic paper abstracts to recommend optimal journals..." in the intro, When to Use, and Key Features), and generic boilerplate sections (Key Features, Implementation Details, Lifecycle Status, Security Checklist, Evaluation Criteria) add no skill-specific knowledge. A stale date ("Next Review Date: 2026-03-06") also pads the body, making this noticeably verbose rather than just loosely tighten-able.

2 / 5

Actionability

The body gives concrete, mostly executable commands ("python scripts/main.py --abstract \"...\" --format json") whose flags match the actual argparse in scripts/main.py, plus a complete parameter table. Minor gaps keep it below 5: the script's "--file" flag is undocumented, the example "--abstract \"abstract.txt\"" contradicts the table's "abstract text" description, and requirements.txt is referenced but absent from the bundle.

4 / 5

Workflow Clarity

The Workflow section sequences five steps with an early-stop validation ("stop early if the task would require unsupported assumptions"), a py_compile Quick Check, and an explicit failure/fallback path with stated blocking causes. It falls short of 5 because two competing process descriptions (the generic "Workflow" and the domain-specific "How It Works") dilute which sequence to follow, and the domain steps lack checkpoints.

4 / 5

Progressive Disclosure

Bundle references are real, one level deep, and clearly listed ("references/journals.json - Journal database with impact factors and scopes"), but roughly a hundred lines of meta-content (Risk Assessment, Security Checklist, Evaluation Criteria, Response Template, Output Requirements) are inlined in SKILL.md where they belong in separate files. Forward-dangling pointers ("See `## Prerequisites` above" appearing before that section exists) further blur navigation, so structure is present but not well organized.

3 / 5

Total

13

/

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 states a clear, third-person "what" with a specific academic-publishing niche, but it omits any "when to use" trigger guidance and misses natural user phrasings like "journal recommendation" or "where to submit". It is serviceable but below the quality of the good examples, which pair capabilities with explicit trigger clauses.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks where to submit a manuscript, wants journal recommendations, or mentions impact factors or journal fit."

Add natural synonyms users actually say — "journal recommendation", "manuscript", "where to publish" — to broaden trigger coverage without adding vagueness.

Optionally enumerate the concrete actions performed (field classification, scope matching, IF filtering, ranking) to raise specificity beyond analyze/recommend.

DimensionReasoningScore

Specificity

"Analyzes academic paper abstracts to recommend optimal journals for submission" names the domain and two concrete actions, but the trailing "considering impact factors, scope alignment, and domain expertise" lists evaluation criteria rather than additional actions, so coverage is not comprehensive. It is above a minimal 2 (which would lack real actions) but below 4 (which would list several specific actions).

3 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines, a missing trigger clause caps completeness at 3. A 4 would require at least a weakly explicit "when".

3 / 5

Trigger Term Quality

"academic paper abstracts", "journals", "submission", and "impact factors" are relevant keywords a user might say, but common natural variations such as "journal recommendation", "where to submit", "manuscript", or "find a journal" are missing. This is better than a 2 (which would have only generic keywords) but lacks the fuller coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

Journal-submission recommendation is a fairly distinct niche unlikely to fire for unrelated skills, with only minor overlap risk against closely related literature-search or citation skills. Not 5, because the description relies on domain wording alone rather than distinct trigger phrases to disambiguate.

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