CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-select-journal

当用户明确要求“推荐投稿期刊”“帮我的论文选 SCI 杂志”“这篇 manuscript 适合投哪些 journal”“期刊匹配/选刊/投稿建议”时必须使用。适用于用户提供全文、摘要、Markdown、LaTeX、PDF、Word 或混合材料的场景;本 skill 会基于 manuscript 与用户偏好,先用内置 `2023IF.xlsx` 做最小硬过滤生成候选池,再由宿主模型自主规划 Set1/Set2/Set3,并联网核验 scope / 质量 / 近 3 个月 PubMed 论文,最后输出 1 份按推荐度排序的 Markdown 选刊报告。⚠️ 不适用:用户只是想润色论文、只想翻译摘要、或只问某个单一期刊的官网信息而不需要系统选刊。

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is a well-structured, actionable multi-step workflow with genuinely executable scripts and clean reference splitting, but it loses points for repeated path verbosity, missing script-failure feedback loops, and four broken template file references.

Suggestions

Create the missing templates/ directory with the four referenced *.template.json files, or replace those template references with inline field definitions so no path dangles.

Add an explicit validate→fix→retry loop for the script steps (e.g., what to do when shortlist_journals.py or fetch_pubmed_recent.py fails or returns empty).

Factor the long .bensz-api/task-…/paper-select-journal/… path into a short variable (e.g., $RUN_DIR) in the command examples to remove repeated token bloat.

DimensionReasoningScore

Conciseness

The body avoids general-knowledge fluff and is well organized, but the full dynamic workspace path is repeated verbatim across multiple command blocks and the 'Set1 is not final' caveat is restated several times, so it could be tightened.

2 / 3

Actionability

Provides real, executable commands (init_workspace.py, shortlist_journals.py, fetch_pubmed_recent.py, render_report.py with concrete flags) plus explicit required JSON field lists; the placeholder date tokens are justified by the dynamic task-directory design.

3 / 3

Workflow Clarity

Steps 1–6 are clearly sequenced with content-validation checkpoints (Set2 scope review, Set3 relevance gate), but for a batch/remote-operation skill there is no explicit validate→fix→retry feedback loop for script failures or empty PubMed results.

2 / 3

Progressive Disclosure

Body correctly points to real one-level-deep reference/script/asset files, but all four referenced templates/*.template.json paths are dangling (the templates/ directory does not exist), which breaks navigation for those steps.

2 / 3

Total

9

/

12

Passed

Description

100%

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 strong, concise, and uses third-person voice while clearly stating both trigger conditions and concrete capabilities with an explicit non-applicability boundary. Every dimension hits the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: hard-filter a candidate pool with built-in 2023IF.xlsx, online-verify scope/quality/recent PubMed papers, and output a sorted Markdown journal-selection report.

3 / 3

Completeness

Explicitly states both when to use it ('当用户明确要求…时必须使用') and what it does (full Set1→Set3 workflow and Markdown report output), with an explicit non-applicability clause.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say such as '推荐投稿期刊', '帮我的论文选 SCI 杂志', '这篇 manuscript 适合投哪些 journal', and '期刊匹配/选刊/投稿建议', covering several variants.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (SCI journal selection backed by 2023IF + live PubMed verification) and the explicit '不适用' boundary distinguishes it from polishing/translation/single-journal lookup skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
huangwb8/ChineseResearchLaTeX
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.