CtrlK
BlogDocsLog inGet started
Tessl Logo

nsfc-research-content-writer

当用户明确要求"写/改研究内容""研究内容+创新+年度计划编排"时使用。为 NSFC 正文"(二)研究内容"写作/重构,并同步编排"特色与创新"和"三年年度研究计划",输出可直接落到 LaTeX 模板的三个 extraTex 文件。

66

Quality

80%

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-research-content-writer/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, actionable instruction-only skill with a clear sequenced workflow and a strong reference bundle. It loses points mainly on conciseness due to redundant motivational prose and generic boilerplate.

Suggestions

Collapse the '专家写作的核心特征' and '一个判断标准' sections into the relevant steps or move to a reference; they restate points already made in steps 3–5.

Trim the generic '公共硬约束' boilerplate to only the constraints specific to this skill, or link it as a shared reference instead of inlining.

Add an explicit verify-before-write gate in apply mode (e.g., run the dod_checklist / validate_skill.py before writing the three .tex files) to strengthen the workflow's validation feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance, but the '专家写作的核心特征' and '一个判断标准' sections restate concepts already covered in the steps, and the '公共硬约束' boilerplate adds generic padding.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: specific file paths (extraTex/2.*.tex), page/word budgets (12–15 pages, 12000–15000 字), framework options, and explicit output-purification rules.

4 / 5

Workflow Clarity

Clear 7-step sequence with a consistency-check checkpoint (step 6) and a two-phase planning/writing model; validation is present though somewhat implicit rather than a hard verify-before-write gate.

4 / 5

Progressive Disclosure

Good structure with 10 well-signaled one-level-deep markdown references (all real files), but some philosophical prose is inlined in the body that could live in a reference.

4 / 5

Total

15

/

20

Passed

Description

92%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 states concrete actions, an explicit 'Use when' trigger with natural phrasing, and a distinctive niche. The only minor gap is limited synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Names multiple concrete actions—'写作/重构'研究内容, '同步编排特色与创新', '编排三年年度研究计划', and outputting '三个 extraTex 文件'—with comprehensive coverage of the niche.

5 / 5

Completeness

Explicitly answers both: '当用户明确要求…时使用' gives the when, and the writing/arrangement/output actions give the what, with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('写/改研究内容', '研究内容+创新+年度计划编排') but offers limited synonym variation; good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (NSFC 研究内容 section writing with specific LaTeX extraTex outputs) with distinct triggers and minimal overlap risk with other skills.

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

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.