CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-import

逆向导入已有小说。将已写好的小说(半成品或完本)反向解析为标准项目目录结构,兼容 story-long-write / story-short-write 后续写作流程;内部复用 story-long-analyze / story-short-analyze 的拆解管道,按篇幅自动分流。触发方式:/story-import、「导入小说」「反向解析」「导入」「把我的书导进来」。

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-engineered orchestration skill: crystal-clear phased workflow with real validation checkpoints and resume support, and a clean one-reference-per-phase bundle whose files all exist. Weaknesses are minor — an overlong version-notice paragraph, some duplicated constraints, and second-level reference chaining in Phase 4.

Suggestions

Split the run-on "Spawn 版本提示" blockquote into 2-3 short bullet rules (read version → compare → action) so the version-mismatch handling costs fewer tokens and parses on first read.

State the 对标 separation rule once (either in 名词与目录边界 or in Phase 1 Step 3) and cross-reference it from the other spot instead of restating it.

Note in the Phase 4 table row or section that import-tracking.md additionally requires tracking-initialization.md and character-state-reverse.md, so the second-level reads are visible from the schedule table.

DimensionReasoningScore

Conciseness

The body is dense with operational constraints and explains nothing Claude already knows, but a few passages could be trimmed: the "Spawn 版本提示" blockquote is a single run-on sentence packing five conditions, and the 对标 separation rules appear both in "名词与目录边界" and again in Phase 1 Step 3. Not 3 because there is no padding or concept explanation anywhere; not 5 because those overlong/duplicated passages still cost tokens without adding instructions.

4 / 5

Actionability

Gives exact paths ({书目录}/.story/work/导入记录.md), a full copy-paste import-record template, verbatim author-facing prompts with scripted decision branches (选 1 → …; 选 2 → …), and a concrete command (scripts/tracking_commit.py init). Not 5 because Phases 2, 3, and 5 are pure delegations ("读 X,按它做") whose executable detail lives entirely one level down in reference files; not 3 because everything in the body itself is directly executable rather than pseudocode or high-level hints.

4 / 5

Workflow Clarity

Clear Phase 1–5 sequence with a schedule table mapping each phase to its inputs, confirmations, and on-disk outputs; file-based handoff via the 导入记录 read and written at every phase boundary; explicit validation checkpoints ("结构迁移验收后" before outline batches, "check 通过后勾进度", batch acceptance "已验收到第 {B} 章") and error-recovery loops ("卷纲缺失…先回结构迁移补卷纲", non-blocking version-mismatch handling), plus a progress checklist and a documented resume protocol. This matches the anchor-5 pattern including feedback loops for a batch operation.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview: the schedule table points to exactly one reference per phase, all ten referenced files and all five scripts exist on disk, and every bundle file is reachable (wordcount_core.py is a shared module of two scripts). Not 5 because some reference files fan out to further reference files (import-tracking.md → tracking-initialization.md + character-state-reverse.md; outline-reverse.md → outline-reverse-rules.md), creating 2-level chaining, and the dense agent-compatibility blockquotes at the top obstruct entry-point navigation; not 3 because the chaining is explicitly signaled by listing all files to read upfront and each phase's reference is clearly motivated in the table.

4 / 5

Total

17

/

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: it states a concrete, well-scoped capability and gives explicit trigger phrases in the user's natural language. The main residual risks are the overly generic bare trigger 「导入」 and mild blur with the story-*-analyze skills whose pipelines it reuses.

DimensionReasoningScore

Specificity

Lists several concrete actions — "反向解析为标准项目目录结构", "按篇幅自动分流", "兼容 story-long-write / story-short-write 后续写作流程" — plus scope (半成品或完本). Not 5 because the reused-analyze-pipeline detail is internal plumbing rather than a user-facing action, and the target structure's contents (设定/大纲/正文/追踪) are not enumerated; not 3 because it goes beyond 1-2 actions with explicit routing behavior and integration scope.

4 / 5

Completeness

Explicitly answers what ("将已写好的小说(半成品或完本)反向解析为标准项目目录结构,兼容…后续写作流程") and when ("触发方式:/story-import、「导入小说」「反向解析」「导入」「把我的书导进来」") with concrete trigger phrases. Matches the anchor-5 example structure exactly; the when-clause is fully explicit, not merely implied, so 4 does not fit.

5 / 5

Trigger Term Quality

"触发方式:/story-import、「导入小说」「反向解析」「导入」「把我的书导进来」" gives natural phrases a user would actually say, with synonym variation across casual and formal registers. Not 5 because common variants like 「续写」「把这本书导进来」 are missing and there are no file-type cues; not 3 because coverage includes multiple natural synonyms rather than a few generic keywords.

4 / 5

Distinctiveness Conflict Risk

Stakes a clear niche — reverse-importing an already-written novel into a continuing project — distinct from fresh-writing skills. Not 5 because the bare trigger 「导入」 is generic and the description explicitly reuses the story-*-analyze pipelines, creating mild adjacency with those analyze skills; not 3 because the intent (import existing book, not write or analyze) is clearly separated.

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-import/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.