CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-know-journal

当用户给出期刊/杂志名并希望了解投稿要求、投稿形式/格式清单、期刊官网信息、社区评价、审稿速度、费用、文章类型、格式细节或“这个 journal 怎么投/是否靠谱/投稿指南调研”时必须使用。联网核验期刊官网与社区评测,默认把全部中间文件隔离到当前工作目录的 `.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/paper-know-journal/`,最终只交付 `KnowJournal-{杂志名}.md`。⚠️ 不适用:用户要根据 manuscript 选择投稿期刊(用 paper-select-journal)、写论文正文、下载全文 PDF,或只问一个无需成稿的简单事实。

68

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

73%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, actionable workflow with explicit validation and recovery loops and appropriate externalization of templates and source policy. Main weaknesses are mild conciseness redundancy and inline detail that could be pushed deeper into references.

Suggestions

De-duplicate the 投稿形式要求 guidance between the 调研 and 成稿 sections — keep the canonical spec in one place and reference it from the other to trim tokens.

Move the long 调研 checklist and 成稿 report-requirements list into a reference file (e.g. references/research-checklist.md) so SKILL.md stays a lean overview.

Tighten or externalize the 公共硬约束 boilerplate block so only skill-specific constraints remain inline in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient and task-specific with no basic-concept padding, but there is noticeable redundancy (投稿形式要求 detailed in both the 调研 checklist and the 成稿 requirements) and a sizable boilerplate 公共硬约束 block that could be tightened; not a 4 because these could be trimmed without losing clarity.

3 / 5

Actionability

Provides executable init_workspace.py and validate_report.py invocations with arguments, a concrete sources.json schema, and pointers to complete templates/policies; minor gaps remain because the research steps themselves are instructional guidelines rather than deterministic code, and script paths use a /path/to/ placeholder.

4 / 5

Workflow Clarity

Clear sequenced pipeline (输入→初始化→调研→成稿→验证→输出→校验) with an explicit validate_report.py checkpoint, a 失败与恢复 feedback section, and concrete checklists (报告必须包含, 可执行清单); validation is present so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with clearly signaled one-level-deep references (references/source-policy.md, references/report-template.md) that are real bundle files, and scripts are split out; not a 5 because substantial inline checklists (调研 list, 成稿 requirements) could partly be externalized to reference files.

4 / 5

Total

16

/

20

Passed

Description

95%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, trigger-rich description that clearly states both what it does and when to use it, with explicit boundary guidance against adjacent skills. Voice is declarative/third-person, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists several concrete coverage areas (投稿要求、投稿形式/格式清单、期刊官网信息、社区评价、审稿速度、费用、文章类型、格式细节) plus a concrete action (联网核验) and deliverable (KnowJournal-{杂志名}.md); not a 5 because the core action is essentially 'research and produce a report' rather than multiple distinct discrete operations.

4 / 5

Completeness

Explicitly answers both 'when' ('当用户...时必须使用') and 'what' (联网核验期刊官网与社区评测并交付 KnowJournal-{杂志名}.md) with concrete trigger phrases, and adds an explicit non-applicability clause.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and colloquial triggers users would actually say — '这个 journal 怎么投/是否靠谱/投稿指南调研' alongside formal terms like 投稿要求、审稿速度、费用、文章类型.

5 / 5

Distinctiveness Conflict Risk

Clear niche (journal submission-requirements research) with explicit disambiguation against paper-select-journal, paper writing, and PDF download, minimizing wrong-skill triggers.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

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.