CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-select-journal

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

Quality

84%

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

63%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 well-sequenced, largely executable journal-selection pipeline with real scripts, concrete commands, and clearly signaled reference files. Its main weaknesses are broken references to a nonexistent `templates/` directory, redundant restatement of workspace-path rules, and generic framework boilerplate (output/validation/constraints sections) that adds tokens without skill-specific guidance.

Suggestions

Ship the four referenced `templates/*.template.json` files (or remove/inline those references) — every step currently points Claude at files that do not exist in the bundle.

State the hidden-workspace path convention once and reference it thereafter; the same `.bensz-api/task-{...}` path rules appear in 核心原则, 输入与工作区, 输出管理, and 公共硬约束.

Replace the generic "校验" section with explicit per-step checks, e.g. a command or checklist validating that `set1_candidates.json`, `set2_scope_review.json`, and `final_recommendations.json` match their schemas before proceeding.

DimensionReasoningScore

Conciseness

The process core is tight, but the workspace-path rules are repeated in three places ("核心原则", "输入与工作区", "公共硬约束") and the closing framework boilerplate ("输出", "校验", "输出管理", "公共硬约束") is generic filler not specific to this skill — it could be tightened noticeably.

3 / 5

Actionability

Concrete copy-paste commands are given for all four scripts with arguments and expected output files (e.g. `python3 <skill_root>/scripts/shortlist_journals.py --workspace ... --profile ...`), plus required JSON fields and enum values. Falls short of 5 because all four referenced `templates/*.template.json` files do not exist in the bundle, and long placeholder paths appear repeatedly inline.

4 / 5

Workflow Clarity

The sequence (manuscript profile → Set1 hard filter → Set2 web verification → 4a PubMed fetch → 4b AI similarity → final JSON → render) is clearly ordered with stage gates (e.g. "`include_in_set3` 为 `false` 的期刊,不要进入最终推荐", warning-journal elimination). Not 5 because the "校验" section is generic ("完成后执行 Skill 已有的静态检查…") rather than explicit per-step validation commands or feedback loops.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled (模板:`templates/…`, 写法:`references/manuscript-profile.md`, 核验口径:`references/journal-quality-checklist.md`), but four referenced `templates/` paths plus `config.yaml` and `CHANGELOG.md` do not exist in the bundle, breaking navigation for key steps.

3 / 5

Total

14

/

20

Passed

Description

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

Excellent description: it states a concrete multi-stage pipeline, gives explicit natural-language trigger phrases in both Chinese and mixed Chinese/English, and clearly bounds scope with an explicit 'not applicable' clause. Third-person voice is used and every clause carries information, so no penalties apply.

DimensionReasoningScore

Specificity

The description lists a full concrete pipeline: "先用内置 `2023IF.xlsx` 做最小硬过滤生成候选池", "再由宿主模型自主规划 Set1/Set2/Set3", "联网核验 scope / 质量 / 近 3 个月 PubMed 论文", "输出 1 份按推荐度排序的 Markdown 选刊报告" — multiple specific concrete actions with comprehensive coverage of what the skill does.

5 / 5

Completeness

It explicitly answers both 'what' (the full filter → plan → verify → report pipeline) and 'when' ("当用户明确要求…时必须使用" with concrete trigger phrases), and even adds an explicit non-applicability clause (润色论文、翻译摘要、单一期刊查询).

5 / 5

Trigger Term Quality

It quotes natural trigger phrases users would actually say — "推荐投稿期刊", "帮我的论文选 SCI 杂志", "这篇 manuscript 适合投哪些 journal", "期刊匹配/选刊/投稿建议" — covering synonyms and input-format terms (全文、摘要、Markdown、LaTeX、PDF、Word).

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (systematic SCI journal selection for a manuscript) with distinct triggers and an explicit exclusion list, so overlap with polishing/translation/single-journal-lookup skills is minimal.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

huangwb8/ChineseResearchLaTeX

Path

skills/paper-select-journal/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.