CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chinese-novelist

当用户要求写小说、创作故事、分章节写作、连续剧情、长篇小说,或需要续写/校验未完成的小说项目时使用。支持悬疑/言情/奇幻/科幻/历史等全题材中文创作。

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 orchestrating SKILL.md: lean, clearly sequenced, with explicit user-confirmation gates and an automated validation loop, and verified progressive-disclosure links to real flow files. The only notable gaps are unnamed validation scripts in phase 4 and the guides/ directory being buried one level deeper than necessary.

DimensionReasoningScore

Conciseness

The ~50-line body is lean throughout: one-line phase summaries with links, terse craft rules ("展示而非讲述 - 用动作和对话表现"), and no explanation of concepts Claude already knows. Every section carries functional instruction, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete, executable specifics are given (folder format `./chinese-novelist/{timestamp}-{小说名称}/`, `01-大纲.md`, mode identifiers `serial`/`subagent-parallel`/`agent-teams`, "最多3轮"), with detail correctly delegated to flow files. Not 5 because phase 4 says "调用脚本检查章节状态和字数" without naming the actual scripts (e.g., `scripts/check_chapter_wordcount.mjs`, `scripts/validate_project.mjs`).

4 / 5

Workflow Clarity

Phases are explicitly numbered and sequenced (第0步 through 第四阶段) with confirmation gates ("等待用户确认") and explicit no-confirm directives for phases 3-4. Phase 4 is a full validate→fix→retry feedback loop with a retry limit ("最多3轮") and an escalation path ("标记 needs_attention"), matching the top anchor.

5 / 5

Progressive Disclosure

The body is a clean overview with well-signaled, one-level-deep links ("详见 [phaseX-….md]"), and all seven referenced flow files exist in references/flows/. Not 5 because the guides/ files are only reachable through a second hop via the flow documents (never surfaced or listed from SKILL.md), and phase3-writing.md is linked twice.

4 / 5

Total

18

/

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 has an explicit and well-populated 'use when' trigger clause and occupies a clear niche, but the capability ('what') side is under-specified: it leans on trigger scenarios instead of stating what the skill concretely produces. Adding one sentence naming its concrete outputs would lift it to the top anchors.

Suggestions

State the skill's concrete capabilities explicitly (e.g., '生成大纲、人物档案,逐章创作长篇小说,自动校验字数与质量') rather than relying on the generic '支持全题材中文创作'.

Add common trigger synonyms such as '网文' or '写故事' to broaden natural keyword coverage.

Mention key deliverables (project folder, 大纲/人物档案 files, finished chaptered manuscript) so the 'what' is as explicit as the 'when'.

DimensionReasoningScore

Specificity

The domain is named and a couple of concrete capabilities appear ("续写/校验未完成的小说项目", "分章节写作"), but they are framed as user-request triggers rather than a list of the skill's actions, and the only capability statement is the generic "支持…全题材中文创作". Not 4 because it does not enumerate several specific skill actions (e.g., outline generation, character profiles, automated validation) the way the top anchors do.

3 / 5

Completeness

Both parts are present: an explicit when-clause ("当用户要求…时使用") with concrete trigger scenarios, and a what-statement ("支持…全题材中文创作"). Not 5 because the 'what' is thin — it never states concrete deliverables like outlines, character files, or chapter-by-chapter generation.

4 / 5

Trigger Term Quality

Good coverage of natural phrases a user would say — "写小说", "创作故事", "分章节写作", "长篇小说", "续写" — plus genre keywords ("悬疑/言情/奇幻/科幻/历史"). Not 5 because common synonyms such as "网文" or "写故事" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Chinese long-form, chapter-based novel creation with resume/validate support) with distinct triggers, giving minimal conflict risk with unrelated skills. Not 5 because it could still overlap with a generic story-writing or creative-writing skill covering the same trigger phrases.

4 / 5

Total

15

/

20

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.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 7 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 7 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

PenglongHuang/chinese-novelist-skill

Path

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.