CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-short-write

短篇网文写作。辅助短篇小说创作,从构思到成稿,聚焦情绪拉扯与节奏把控。触发方式:/story-short-write、/写短篇、「帮我写一篇短篇」「写个盐言故事」。

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 disciplined operational skill body: a phase router with hard gates and runnable validation commands, verbatim interaction scripts, and well-signaled one-level-deep references verified against the actual bundle. The sole meaningful criticism is density — the mandatory-reading paragraph and the inline agent-version blockquote carry time-sensitive, hard-to-parse detail that could be simplified or relocated.

DimensionReasoningScore

Conciseness

The body teaches nothing Claude already knows — every line is operational (per-phase reading lists, execution rules, gates, runnable checks), and the craft methodology is pushed to references. It is not 5 because the「写前必读」paragraph is convoluted enough to need re-reading, and the agent-host blockquote inlines time-sensitive version handling (「agents_version: 44」) that is not in a deprecated section; it is well above 3 because there is no padded or explanatory filler.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands like「node {skill 根}/scripts/check-ai-patterns.js --check --fail-on=blocking {短篇目录}/正文.md」and「scripts/author_memory_commit.py query --workspace {工作区} --book-root {项目目录} --kind prose_style --kind story_design」, a verbatim user question「你想让读者读完什么感觉?有没有想写的题材方向或灵感?」, and a concrete emotion-selection table covering the common Phase 1 cases.

5 / 5

Workflow Clarity

Phases 1–4 are explicitly sequenced with hard gates (「Phase 3 完成门槛(进入 Phase 4 前必须通过)」), an explicit feedback loop (「不通过 → 回退补足,不得进入精修」), a runnable completion checklist, and handoff rules between phases (「交接只靠落盘」「换上下文」). This matches the top anchor: clear sequence, explicit validation, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

SKILL.md is a true overview/router: the mandatory-reading table routes each phase to specific files and even named sections (e.g. emotional-methods.md「情感拉扯节奏设计」and dialogue-mastery.md「什么时候读这份」, both verified present in the bundle), every referenced file exists (19 reference files, 10 genre-styles packs, 8 scripts), and references stay one level deep with markdown links and explicit conditional triggers. Only a hair short of perfect: the multi-host agent-dispatch blockquote inlined in the body could arguably live in agent-calls.md, but it is main-session behavior that the overview legitimately needs.

5 / 5

Total

19

/

20

Passed

Description

82%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 compact, well-formed description: it states the domain and pipeline span, gives two concrete craft focuses, and provides explicit trigger guidance with both slash commands and natural user phrases. The only weakness is that the capability list stays high-level instead of enumerating the concrete actions (conception, outlining, drafting, revision) the body actually performs.

DimensionReasoningScore

Specificity

「辅助短篇小说创作,从构思到成稿」names the domain and a conception-to-finished-draft span, and「聚焦情绪拉扯与节奏把控」adds two concrete craft focuses, but the description never enumerates several distinct actions (outlining, drafting, revision are only implied by the span). This matches 'Names domain and 1-2 concrete actions, but not comprehensive' rather than the level above, which requires a list of several specific actions.

3 / 5

Completeness

The 'what' is explicit (「辅助短篇小说创作,从构思到成稿,聚焦情绪拉扯与节奏把控」) and the 'when' is explicit via「触发方式」with four concrete trigger phrases, exactly matching the top anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases'. A score of 4 would require the 'when' to be less explicit than it is here.

5 / 5

Trigger Term Quality

「触发方式:/story-short-write、/写短篇、「帮我写一篇短篇」「写个盐言故事」」combines slash commands with natural phrases a user would actually say, including the platform-specific「写个盐言故事」. Not 5 because common variations such as「写个短篇」or「短篇小说」are absent; not 3 because multiple natural, user-realistic trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (短篇网文 short-form web fiction) and the triggers are distinctive —「帮我写一篇短篇」「写个盐言故事」and /写短篇 clearly signal short-form fiction and would not fire for long-form or analysis sibling skills. This matches 'Clear niche with distinct triggers; minimal conflict risk'.

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