CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nsfc-research-content-writer

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

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A well-structured, domain-expert writing skill with a clear validated workflow and excellent one-level reference architecture. Its weaknesses are token overhead from inlined infrastructure boilerplate (common constraints, bug policy) and unreferenced bundle scripts, plus reliance on references for concrete examples.

Suggestions

Move the '公共硬约束' boilerplate and bensz-collect-bugs policy into a shared reference file (or trim to the constraints actually relevant to this skill) to reduce token overhead and lift conciseness.

Reference the scripts/ bundle files (e.g., check_project_outputs.py, validate_skill.py) from the body where they support the workflow, so the full bundle is discoverable.

Inline one compact subgoal-triplet or innovation-point example directly in the body (or tighten the preview-mode output spec) to make guidance copy-paste ready without requiring a reference hop.

DimensionReasoningScore

Conciseness

The core writing guidance is dense and domain-specific (page budgets, review-criteria shift, anti-patterns, two-phase planning mode), but the body carries noticeable non-task padding: the long '公共硬约束' boilerplate (security/path/SSRF/BAC auditing clauses), the bug-reporting policy for 'bensz-collect-bugs', and philosophical sections like '一个判断标准' that could be tightened or moved out. Fits 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact target files ('extraTex/2.1.研究内容.tex' etc.), quantified budgets (12–15 pages, 12000–15000 字, 1–3 innovation points), forced subgoal triplet fields (指标/对照/数据来源), and an explicit output-purification rule. Not 5 because inline copy-paste examples are absent — templates and examples are delegated to references — and the preview-mode output format is only loosely specified.

4 / 5

Workflow Clarity

A clear 7-step numbered sequence (locate files → fix subgoal triplets → generate 2.1 → extract 2.2 → derive 2.3 → consistency check → user reminder) with an explicit validation step (step 6 一致性校验 plus 输出净化), a DoD checklist reference, and a 失败与恢复 section defining retry-from-failed-step. Validation is present for the multi-file write operation, so no cap applies. Not 4 because checkpoints and error-recovery behavior are explicit, not implicit.

5 / 5

Progressive Disclosure

Ten reference files are each linked with a one-line label of what they contain, all exist on disk, and are one level deep (no nested references). Not 5 because the body still inlines the shared '公共硬约束' boilerplate that belongs in a separate/common file, and the scripts/ bundle (e.g., check_project_outputs.py, validate_skill.py) is never referenced or navigable from the body.

4 / 5

Total

16

/

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.

A strong description: explicit trigger clause, concrete actions, named deliverables, and a highly distinctive NSFC-specific niche. The only improvement area is broader trigger-term coverage (synonyms like '申报书'/'标书'/'撰写').

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with concrete deliverables: '为 NSFC 正文"(二)研究内容"写作/重构,并同步编排"特色与创新"和"三年年度研究计划",输出可直接落到 LaTeX 模板的三个 extraTex 文件' — it names the exact sections written, the synchronization operation, and the three output files. Not below 4 because coverage is comprehensive for the skill's scope, not vague.

5 / 5

Completeness

Both 'what' (write/refactor section 二, orchestrate 特色与创新 and 三年年度研究计划, output three extraTex files) and 'when' ('当用户明确要求...时使用' with concrete quoted trigger phrases) are explicitly and clearly answered. Voice is neutral third person, satisfying the guideline.

5 / 5

Trigger Term Quality

Explicit natural trigger phrases are quoted: '当用户明确要求"写/改研究内容""研究内容+创新+年度计划编排"时使用' — terms a user would plausibly say. Not 5 because common synonyms and variations (e.g., '申报书', '标书', '国自然', '撰写') are missing; not 3 because the quoted triggers are natural user phrasings rather than jargon.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — NSFC proposal section (二) writing with three named output files — with triggers unlikely to match any other skill. Not 4 because no plausible overlap with neighboring skills exists given the narrow scope.

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.

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-research-content-writer/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.