CtrlK
BlogDocsLog inGet started
Tessl Logo

nsfc-qc

当用户明确要求"标书QC/质量控制/润色前质检/引用真伪核查/篇幅与结构检查"时使用。对 NSFC 标书进行只读质量控制:并行多线程独立检查文风生硬、引用假引/错引风险、篇幅与章节分布、逻辑清晰度等,最终输出标准化 QC 报告;中间文件默认归档到 `project_root/.bensz-api/task-{yyyymmdd-hhmm}-{简短描述}/nsfc-qc/{yyyy-mm-dd-hh-mm}/`,并兼容 legacy `.nsfc-qc/` 读取/清理。

67

Quality

82%

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

65%

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 skill body with real executable scripts and a clear 5-step flow. Its main gaps are missing validate-fix-retry feedback loops for the batch operation and an unsignaled reference whose content is duplicated inline.

Suggestions

Add an explicit validation checkpoint in 主流程 (e.g., run scripts/validate_final_outputs.py after materialization, with a fix-and-revalidate loop) so the batch workflow has a clear validate→fix→retry feedback loop.

Replace the inline thread-coverage checklist in step 3 with a signaled link to references/qc_checklist.md (e.g., "每个 thread 按 [qc_checklist.md](references/qc_checklist.md) 执行,至少覆盖…") to remove duplication and make the reference discoverable.

Define the task-path template once (e.g., in 输入/输出) and reference it by short name elsewhere to remove the three near-identical path repetitions.

DimensionReasoningScore

Conciseness

The body is mostly lean and bulleted with no general-concept padding, but the task-path template is repeated three times ("./.bensz-api/task-{yyyymmdd-hhmm}-…/", lines 35/47/92) and the workspace conventions overlap 主流程, so it could be tightened; not the every-token-earns-its-place bar at 3.

2 / 3

Actionability

Provides copy-paste-ready bash invocations with real script paths and flags (nsfc_qc_run.py --project-root --main-tex --deliver-dir --threads --execution), plus concrete inputs/outputs and a fixed report skeleton, matching the executable/copy-paste-ready anchor.

3 / 3

Workflow Clarity

主流程 lists five clearly sequenced steps, but this is a batch/multi-thread operation with no explicit validate→fix→retry feedback loop inside the flow; per the rubric's batch-operation note that caps the score at 2 rather than 3.

2 / 3

Progressive Disclosure

Scripts are referenced one level deep by path, but references/qc_checklist.md is never signaled/linked from the body and its thread-coverage content is duplicated inline in step 3 ("每个 thread 至少覆盖…"), fitting the 2-anchor of inline content that should be split.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person description that pairs an explicit use-when trigger with several concrete read-only QC actions and a clearly scoped NSFC-proposal niche. It is concise and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("并行多线程独立检查文风生硬、引用假引/错引风险、篇幅与章节分布、逻辑清晰度" plus "输出标准化 QC 报告"), matching the anchor for multiple specific concrete actions rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly states both when ("当用户明确要求…时使用") and what (read-only QC producing a standardized report), satisfying the what+when-with-explicit-trigger bar; the missing-trigger cap at 2 does not apply.

3 / 3

Trigger Term Quality

Embeds natural user phrasing ("标书QC/质量控制/润色前质检/引用真伪核查/篇幅与结构检查") with good variation coverage, not jargon-only; it is not the 2-anchor which misses common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (NSFC 标书只读 QC) with distinct, domain-specific triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

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.