CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-long-write

长篇网文规划与写作。支持只讨论结构、只写大纲或指定细纲,明确要求正文后再写章节。触发方式:/story-long-write、/写长篇、「帮我开书」「定设定」「出卷纲」「规划剧情」「写大纲」「补细纲」「日更」「续写」「继续写」「修改第X章」「回炉」「重写第X章」。

Quality

88%

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

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

An exceptionally well-engineered orchestration body: dense, fully operative, with concrete commands, defaults, validation gates, and a disciplined hub-and-spoke reference structure where all referenced files exist. The only weakness is repeated restatement of the same guardrails across sections, which costs some tokens without adding new information.

DimensionReasoningScore

Conciseness

The 135-line body contains zero concept explanations and no filler — every line is operative rules, commands, or routing. Minor trimmable redundancy: the "不自动写正文/完成即停" guardrail is restated roughly five times (scene table, 对象优先, 规划续接, 裸调用, 正文批量上限) and the 写前必读 pointer is repeated in Phase 1-3 and the closing index section. Fits 'efficient; minor instances that could be trimmed'; not 5 because of that guardrail repetition, not 3 because nothing is padding or over-explained.

4 / 5

Actionability

For an instruction-orchestration skill the guidance is copy-paste ready: exact commands with enumerated parameters ("author_memory_commit.py query --workspace … --book-root … --kind story_design、workflow、interaction,改稿查 prose_style"), "outline_view.py --unit {单元ID} {卷纲路径}" with --contract/--toc flags, "tracking_commit.py check" as a gate, a {PYTHON} fallback chain (python3 → python → py -3), explicit defaults (单章默认 1 章,日更默认 2-3 章,单轮最多 3 章), and a concrete three-tier escalation table for new story elements. Specific guidance covers the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: stop-on-missing-reference ("任一必需路径不存在、不可读或未读完时立即停止,报告准确路径"), the tracking gate ("使 tracking_commit.py check 通过,任一未完成就停止"), a delivery checklist (字数、必发生、禁止发生、时间锚、停笔点、章尾新债 逐项复核), ambiguity fallback ("给 2-4 个白话选项让用户选"), a matching order for overlapping triggers, and a runtime degradation path (solo/direct fallback for missing agents). Batch prose writing (2-3 chapters) is covered by these validations, so the batch cap does not apply. Matches the 5 anchor.

5 / 5

Progressive Disclosure

A 135-line hub pointing to 45 reference files and 13 scripts — every path referenced in the body was verified to exist on disk — organized as one-level-deep spokes with moment-based loading conditions and explicit anti-preload rules ("只读当前时刻的"; "只在排查具体问题时读,不预读"; "只读该文件的「决策路由」和它指向的那一节"). reference-index.md acts as a well-signaled navigation layer with per-symptom routing. Content is appropriately split, nothing that belongs in a reference is inlined; matches the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

83%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: concrete capability statement, an explicit consent rule for prose writing, and a rich trigger list with synonyms. Main gaps are the omission of chapter-writing/revision capabilities from the what-statement and the missing natural triggers 「写第N章」/「写正文」.

Suggestions

Add 「写第N章」/「写正文」 (and 「写第1章」) to the trigger list — it is the core capability's most natural request phrasing and currently only appears in the body's trigger table.

Mention revision/rework support (「修改第X章」「回炉」「重写第X章」) in the capability statement, not just in the trigger list, so the what-claim covers all advertised modes.

DimensionReasoningScore

Specificity

"长篇网文规划与写作。支持只讨论结构、只写大纲或指定细纲,明确要求正文后再写章节" names the domain and several concrete modes (structure discussion, outline, detailed outline, chapter writing), which matches 'lists several specific actions; minor gaps'. Not 5 because the capability statement omits revision work even though 「修改第X章」「回炉」「重写第X章」 appear as triggers; not 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what — "长篇网文规划与写作。支持只讨论结构、只写大纲或指定细纲,明确要求正文后再写章节" (including the consent gate for writing prose), and when — "触发方式:/story-long-write、/写长篇、「帮我开书」「定设定」「出卷纲」…" with a dozen concrete trigger phrases. Matches the 5 anchor (clear what AND when with concrete triggers); voice is third person, no penalty applies.

5 / 5

Trigger Term Quality

Twelve natural user phrases including synonyms (「续写」「继续写」; 「修改第X章」「回炉」「重写第X章」) fit 'good keyword coverage; a few natural terms missing'. Not 5 because the core action's most direct request — 「写第N章」/「写正文」 (listed in the body's trigger table) — is absent from the description's trigger list, along with variants like 「写第1章」.

4 / 5

Distinctiveness Conflict Risk

Clear niche (long-form serialized web novels) with domain-specific triggers like 「出卷纲」「补细纲」「日更」「回炉」 that sibling skills would not claim, but generic terms 「写大纲」「规划剧情」「续写」 overlap with closely related skills in the same suite (story-short-write, story-long-analyze). Fits 'mostly distinct; minor overlap risk'; not 5 due to that overlap.

4 / 5

Total

17

/

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

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

zenstory-ai/oh-story-claudecode

Path

skills/story-long-write/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.