CtrlK
BlogDocsLog inGet started
Tessl Logo

nsfc-ref-alignment

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

60

Quality

72%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, validated workflow, but it carries some repetition and keeps detailed reference material inline rather than splitting it into signaled separate files. Tightening duplication and extracting a reference doc would push conciseness and progressive disclosure to 3.

Suggestions

De-duplicate the task-directory path and the read-only modification-boundary rules, which are restated across the 输出, 修改边界, and 验证清单 sections.

Move the detailed per-citation AI judging rubric and report schema into a signaled one-level reference file (e.g. `references/judging_guide.md`) and link to it from the body.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude knows LaTeX/BibTeX, but the task-directory path and read-only modification boundaries are restated multiple times, which keeps it just short of the lean score-3 anchor.

2 / 3

Actionability

It provides fully executable bash commands with concrete flags pointing at the real script `scripts/run_ref_alignment.py`, plus explicit structured input/output file names — copy-paste ready guidance matching the score-3 anchor.

3 / 3

Workflow Clarity

The 4-step workflow is clearly sequenced with explicit validation checkpoints — a 静态自检 checklist, forced evidence-priority rules, and P0/P1 triage — providing the feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

It references a real script bundle, but detail that could live in one-level-deep reference markdown (report schema, field-by-field AI judging rubric) is inline in a single SKILL.md with no clearly signaled separate reference files.

2 / 3

Total

10

/

12

Passed

Description

67%

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 specific and well-scoped to a clear niche, but omits an explicit "Use when…" trigger clause, which caps completeness and trigger-term quality. Adding natural-language trigger phrasing would lift both dimensions.

Suggestions

Append an explicit trigger clause such as "Use when reviewing an NSFC/LaTeX proposal's citations for missing bibkeys, bad DOI/year fields, or misattributed references — and you want a read-only report before editing."

Soften technical-only terms (bibkey, BibTeX, DOI) by pairing them with the natural phrases users actually say (引用核查, 参考文献一致性, 文献真实性).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "核查 bibkey 是否存在", "BibTeX 字段与 DOI 等格式问题", "生成结构化输入供宿主 AI 逐条评估" — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It clearly answers "what" but the "when" is only implied (the 适用场景 triggers live in the body, not the description); per the rubric a missing explicit "Use when…" clause caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces domain terms a user might say (NSFC 标书, 引用, 参考文献, .bib), but leans technical (bibkey, BibTeX, DOI) and lacks natural "Use when…" phrasing with common variations, fitting the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The NSFC 标书引用/参考文献一致性核查 niche is sharply scoped with read-only/report-only framing, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

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.