CtrlK
BlogDocsLog inGet started
Tessl Logo

transfer-old-latex-to-new

当用户明确要求“迁移 LaTeX 模板”“把旧项目接入 ChineseResearchLaTeX”“把旧标书/论文/毕业论文/简历套进当前模板”“把 Word/PDF/Markdown/零散 tex 整理进现有项目”,或直接提到 `transfer-old-latex-to-new` 时使用。旧别名 `migrating-latex-templates` 可兼容理解。该 skill 只负责把正文内容迁移到当前仓库现有模板的内容层;绝不能修改 `packages/` 内公共包源码、也绝不能修改 `projects/` 内模板样式或入口骨架,只能写入目标项目允许承载正文的内容文件。

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/transfer-old-latex-to-new/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 is a well-structured, mostly actionable overview with a clear workflow and validation checkpoint, but it is padded by repeated boundary restatements and canonical boilerplate, and it surfaces only a minority of its available reference files. Tightening redundancy and indexing the full reference set would raise quality.

Suggestions

Consolidate the repeated "只迁移内容/不改模板骨架/样式差异只报告" boundary into a single 约束 section and reference it once from the workflow instead of restating it five times.

Replace the canonical 公共硬约束 boilerplate block with a one-line pointer to the shared constraints source so per-skill tokens stay lean.

Add a short "参考文档" index listing all 12 references/ files (e.g. troubleshooting.md, migration_patterns.md, faq.md) so the bundle is navigable from SKILL.md, not just the 4 currently linked.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain guidance, but the template-protection boundary is restated ~5 times (输出原则, 执行步骤, 做内容层映射, 执行迁移, 约束) and the "公共硬约束" block is canonical boilerplate shared across skills, so it could be noticeably tightened.

3 / 5

Actionability

Concrete, copy-paste-ready official build commands (e.g. `python packages/bensz-nsfc/scripts/nsfc_project_tool.py build --project-dir <项目路径>`) and specific project paths / content-layer globs (`extraTex/*.tex`, `references/*.bib`) are present; the core mapping logic itself is deferred to scripts rather than shown.

4 / 5

Workflow Clarity

A clear sequenced flow (识别产品线 → 清点 → 内容层映射 → 执行迁移 → 官方入口验证 → 校验 → 失败与恢复) with an explicit build-validation checkpoint and a restore path; the validation→fix→retry loop is only partially spelled out (build failure says "如实报告" rather than iterate).

4 / 5

Progressive Disclosure

Well-organized sections with one-level-deep, clearly signaled references (scripts/README.md, references/quickstart.md, config_guide.md, api_reference.md — all real files), but only 4 of the 12 reference bundle files are linked from the body, leaving most of the reference set undiscoverable from the overview.

4 / 5

Total

15

/

20

Passed

Description

91%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 is strong: it explicitly states both the trigger conditions and the scoped capability, with rich natural trigger terms and explicit boundary exclusions. Minor overlap risk from the alias and broad document-organization phrasing keeps distinctiveness just below maximum.

DimensionReasoningScore

Specificity

Lists several concrete actions and input types — "把正文内容迁移到当前仓库现有模板的内容层" and "把 Word/PDF/Markdown/零散 tex 整理进现有项目" — with a concrete writable target, falling just short of comprehensive distinct actions (the verbs are variations of migrate/organize).

4 / 5

Completeness

Explicitly answers both: when ("当用户明确要求…时使用" with concrete trigger phrases) and what ("该 skill 只负责把正文内容迁移到当前仓库现有模板的内容层"), matching the anchor for clearly explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including synonyms (标书/论文/毕业论文/简历), file types (Word/PDF/Markdown/tex), the skill name `transfer-old-latex-to-new`, and a legacy alias, matching the anchor for full coverage with synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

Carves a clear content-migration niche with explicit exclusion of template/package modification, but the legacy alias `migrating-latex-templates` and the broad "整理进现有项目" phrasing create minor overlap with template-development and general document-conversion skills.

4 / 5

Total

18

/

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.