CtrlK
BlogDocsLog inGet started
Tessl Logo

nsfc-code

根据 NSFC 标书正文内容,结合申请代码推荐库,为你给出 5 组申请代码1/2(主/次)推荐与理由;输出到 NSFC-CODE-vYYYYMMDDHHmm.md(只读,不修改标书)

59

Quality

68%

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-code/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 skill body is actionable and well-structured with real bundle references and a clear workflow, but is held back by generic boilerplate padding and a vague validation step. Tightening the common-constraints block and pointing validation at the existing validate_skill.py script would improve it.

Suggestions

Replace the generic "校验" description with a concrete validation command, e.g. running scripts/validate_skill.py, to close the validation gap for the batch/ranking operation.

Move or summarize the "公共硬约束" infrastructure boilerplate into a shared reference file rather than inlining it, to reduce token overhead.

Clean up the inlined report-skeleton markdown block so the deliverable structure is clearly separated from the workflow narrative.

DimensionReasoningScore

Conciseness

The core workflow is lean and task-relevant, but the inlined "公共硬约束" boilerplate (BAC audit, API keys, path traversal/SSRF policy) is generic infrastructure padding that could be tightened or referenced.

3 / 5

Actionability

Provides concrete, copy-paste-ready bash/python commands with specific flags and paths (nsfc_code_rank.py, mkdir, cp), with only minor placeholders like "A...." in the report skeleton.

4 / 5

Workflow Clarity

Clear sequenced flow (timestamp/workspace → read-only read → rank script → 5 recommendations → write file) with a 校验 step and 失败与恢复 retry guidance, though the validation step is generic rather than a concrete command despite validate_skill.py existing.

4 / 5

Progressive Disclosure

Body is an overview pointing to real, one-level-deep bundle files (nsfc_code_recommend.toml, two scripts, validate_skill.py) with the 678KB data externalized; minor organization gaps from the inlined report skeleton.

4 / 5

Total

15

/

20

Passed

Description

70%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 specific and occupies a clear niche, but omits an explicit trigger/"when to use" clause, which caps completeness. Adding a "Use when..." sentence would raise the score.

Suggestions

Add an explicit "Use when..." clause stating when Claude should invoke this skill (e.g., when the user has an NSFC proposal and is unsure which application code to choose).

Include common synonyms or trigger variations such as "国自然", "基金申请代码", or "application code" to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Names the NSFC proposal domain and several concrete actions — giving 5 groups of 申请代码1/2 主/次 recommendations with reasons, outputting to a timestamped MD file, and operating read-only — but not a long list of varied actions as in the 5 anchor.

4 / 5

Completeness

The "what" is clearly stated (5 code-pair recommendations with reasons, read-only, output file) but there is no explicit "Use when..." trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural domain terms a Chinese NSFC applicant would say ("NSFC 标书正文", "申请代码1/2", "推荐"), though it lacks synonyms and file-extension variations.

4 / 5

Distinctiveness Conflict Risk

"NSFC 标书正文 + 申请代码1/2 推荐" is a narrow, distinct niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.