CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nsfc-ref-alignment

检查 NSFC 标书正文引用与参考文献的一致性与真实性风险(只读):核查 bibkey 是否存在、BibTeX 字段与 DOI 等格式问题,并生成结构化输入供宿主 AI 逐条评估“正文表述是否真的在引用该文献”;默认仅输出审核报告,不直接修改标书或 .bib(除非用户明确要求)。

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/nsfc-ref-alignment/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 delivers a genuinely actionable, well-sequenced read-only workflow with real validation checkpoints and correctly delegated script logic, and the referenced bundle files are real and match the documented flags. Its weaknesses are redundancy — the task-directory convention and suffix behavior stated multiple times, duplicated sections, orphaned comparison bullets — and minor forward-reference/path inconsistencies that hurt both conciseness and flow.

Suggestions

State the '.bensz-api/task-{...}/nsfc-ref-alignment/{...}/' directory convention and the '-2/-3' suffix behavior once (in 中间产物) and reference it from elsewhere instead of repeating it in 输出管理 and 公共硬约束.

Delete the orphaned '共同点/不同点' bullets at the end of 步骤 4 (they compare against an unnamed skill with no context) and merge the two '### 输入' sections into one.

Reconcile the run-directory notation: define '{run_dir}' before 步骤 3 uses it, and fix the 'run_{YYYYMMDDHHMMSS}' reference that does not appear in the actual path template.

DimensionReasoningScore

Conciseness

The body restates the '.bensz-api/task-...' directory convention three times (中间产物, 输出管理, 公共硬约束), repeats the '-2/-3/...' timestamp-suffix note verbatim twice, has two '### 输入' sections, and ends step 4 with orphaned '共同点/不同点' bullets. It is mostly efficient but clearly could be tightened, matching anchor 3; not 4 because the redundancy goes beyond minor trimmable instances.

3 / 5

Actionability

The bash commands are concrete and executable (flags --project-root/--main-tex/--report-dir/--prepare/--verify-online match the actual bundled script), with concrete output filenames, path templates, and explicit P0/P1 judgment criteria. Minor gaps hold it at 4: the hardcoded 'cd /path/to/ChineseResearchLaTeX' environment assumption and '{run_dir}' being used in step 3 before it is defined.

4 / 5

Workflow Clarity

步骤 1–4 are clearly sequenced with an explicit 校验 checklist (4 core artifacts present, no .tex/.bib modified, every P0/P1 has file/line + sentence + rationale + action) and a 失败与恢复 retry-from-last-failed-step loop, so the batch-operation cap does not apply. It falls short of anchor 5 due to structural incoherences: duplicate 输入 sections, the orphaned 共同点/不同点 bullets, and a 'run_{YYYYMMDDHHMMSS}' reference that does not match the path template actually shown.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview that keeps script detail out of line and reaches it one level deep via the entry-point command 'scripts/run_ref_alignment.py' (the 6 bundled script files exist and are appropriately not inlined). It sits above the 'content that should be separate is inline' anchor but below 5 due to minor organization gaps from the duplicated sections.

4 / 5

Total

15

/

20

Passed

Description

75%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 highly specific and distinctive, enumerating concrete read-only actions (bibkey existence, BibTeX/DOI format checks, structured input generation for host-AI semantic review) with an explicit non-modification default. Its main weakness is the missing explicit 'when to use' trigger clause, which caps completeness, plus a few natural synonym terms (e.g. '国自然') users might say.

Suggestions

Append an explicit trigger clause such as '使用于:检查 NSFC/国自然标书的引用一致性、核查参考文献真实性与乱引风险时' to answer 'when should this be used' directly.

Add natural synonyms users would actually say — '国自然', '参考文献核对/查证', '乱引' — alongside NSFC/标书 to broaden trigger coverage.

Optionally mention the complementary boundary (bib entry completion belongs to nsfc-bib-manager) in the description to further reduce overlap risk with sibling skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole pipeline — '核查 bibkey 是否存在', 'BibTeX 字段与 DOI 等格式问题', '生成结构化输入供宿主 AI 逐条评估', and an explicit read-only report output policy — matching the comprehensive-coverage anchor. It is not a 4 because there are no notable gaps in the action inventory for this domain.

5 / 5

Completeness

The 'what' is explicit and detailed (consistency/authenticity checks, bibkey existence, field/DOI format, structured input, report-only output), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than present-but-vague.

3 / 5

Trigger Term Quality

Natural trigger terms are present and domain-appropriate: 'NSFC', '标书', '引用', '参考文献', 'bibkey', 'BibTeX', 'DOI', '.bib'. A few natural colloquial variations users would say (e.g. '国自然', '文献核对') are missing, placing it between the anchor-3 and anchor-5 examples but noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

'检查 NSFC 标书正文引用与参考文献的一致性与真实性风险(只读)' carves out a clear niche (NSFC proposal citation auditing with bibkey/BibTeX/DOI triggers) that would not fire for generic document or bibliography skills. Conflict risk is minimal, matching the clear-niche anchor.

5 / 5

Total

17

/

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/nsfc-ref-alignment/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.