CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-literature-review

当用户明确要求"做系统综述/文献综述/related work/相关工作/文献调研",或为研究想法核对强近邻与新颖性时使用;兼容旧名 systematic-literature-review。标准模式执行查询、检索、评分、相关性选文、写作、引用校验与 PDF/Word 导出,novelty-check 模式只交付强近邻、反方证据和未确认项。查询缺失或无效时默认停止,不静默降级为单查询。支持 en/zh/ja/de/fr/es。

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, highly actionable pipeline skill: explicit sequencing, validation and fail-closed gates, resume semantics, and real referenced scripts and reference files. Its main cost is length — repeated policy statements and a duplicated reference list could be consolidated to save context.

Suggestions

State the multi-query fail-closed and single-query-fallback rules once (e.g., in 多查询检索) and reference that section from 准备 and 约束 instead of repeating them three times.

Delete or annotate the bare reference list at lines 167–172, since the same files are already listed with purpose in the 准备 section.

Move the operational details of output-directory layout and pipeline_cost.py usage into a reference file (e.g., development-validation-guide.md), keeping SKILL.md to the pipeline itself.

DimensionReasoningScore

Conciseness

The body is information-dense with no basic-concept padding, but it is noticeably long and repetitive: the multi-query fail-closed / single-query-fallback rules are restated in the 准备, 多查询检索, and 约束 sections, and the 公共硬约束 block plus the dangling bare list of reference paths (lines 167–172, duplicating the annotated list in 准备) could be consolidated. This fits 'mostly efficient but could be tightened' better than the lean anchor.

3 / 5

Actionability

The bash block gives copy-paste-ready commands for the main entry, two-step prepare/resume flow, explicit single-query fallback, legacy entry, and search-skill-root override, all with real flag names; specifics continue throughout (query JSON schema shapes, 5–25 query bounds, 1–10 scoring, 20–40% high-score distribution, exact script and artifact filenames). All named scripts and reference files exist in the bundle.

5 / 5

Workflow Clarity

The pipeline is explicitly sequenced (准备 → 检索 → 去重 → 评分 → 选文 → 子主题/字数预算 → 写作 → 扩写与验证 → 导出) with validation checkpoints (validate_counts.py, validate_review_tex.py, generate_validation_report.py), fail-closed gates at stage 1, a defined retry path in 失败与恢复, and a feedback loop in 有机扩写与验证 (expand only weak sections, re-validate).

5 / 5

Progressive Disclosure

Detailed prompts and templates are correctly split into references/ one level deep (ai_query_generation_prompt.md, ai_scoring_prompt.md, expert-review-writing.md, review-tex-section-templates.md, multilingual-guide.md — all verified present), and heavy logic lives in scripts/. However, the bare unannotated reference list at lines 167–172 and inlined operational policy (output management, cost tracking) leave minor organization gaps versus the well-signaled ideal.

4 / 5

Total

17

/

20

Passed

Description

96%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 dense, high-quality description: explicit bilingual trigger phrases, a concrete enumeration of both operating modes, and stated fail-closed behavior. The only weakness is minor overlap risk with its sibling search skill on survey-style trigger terms.

DimensionReasoningScore

Specificity

The description enumerates the concrete pipeline actions — "执行查询、检索、评分、相关性选文、写作、引用校验与 PDF/Word 导出" — and separately specifies what novelty-check mode delivers ("只交付强近邻、反方证据和未确认项"), giving comprehensive, non-abstract coverage. It is not merely naming the domain; each stage is a concrete capability.

5 / 5

Completeness

It explicitly answers both questions: 'when' via "当用户明确要求…时使用" with concrete trigger phrases, and 'what' via the enumerated standard-mode pipeline and the distinct novelty-check deliverables. Behavior on missing input ("查询缺失或无效时默认停止") adds operational clarity without padding.

5 / 5

Trigger Term Quality

Trigger phrases include natural synonyms in both languages users would actually say: "做系统综述/文献综述/related work/相关工作/文献调研", plus the novelty-check phrasing "为研究想法核对强近邻与新颖性时". It even covers the legacy name "systematic-literature-review", matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The review/writing/export niche is clear and mostly distinct, but the skill explicitly depends on the closely related research-literature-search, and terms like "文献调研" could plausibly fire a search-oriented skill too. This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor.

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

huangwb8/ChineseResearchLaTeX

Path

skills/research-literature-review/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.