CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-long-analyze

长篇网文拆文。保留黄金三章、逐章摘要、剧情、情绪、节奏、角色、设定和文风接口,以连续章节块完成因果、双时间线、关系与三维节奏分析;兼容旧成果直接使用、按需增强和断点续跑。含可选三层灵感库管道(灵感库、跨书灵感聚合、更新灵感库)。触发方式:/story-long-analyze、/长篇拆文、「帮我拆这本书」「拆这本书」「分析黄金三章」「深度拆解」「完整拆解」或提供小说文本文件路径。

Quality

93%

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

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.

The body is an exceptionally lean orchestrator for a complex multi-stage pipeline: a moment-based loading table with one-level-deep references (all verified to exist), checker-driven decision tables with explicit validation and repair feedback loops, and stage markers that checkpoint progress and enable resume. The main gap is that only the asset-inspection command is fully inline, while the plan/digest/mark-stage subcommands and the GBK→UTF-8 conversion step lack copy-paste-ready forms in the body itself.

Suggestions

Inline a one-line copy-paste skeleton for the core manage_analysis_run.py subcommands (e.g. plan --intent continue, digest, mark-stage) with their required arguments, so the common continue/repair paths are executable without opening pipeline-ops.md.

Add the concrete encoding-conversion command (e.g. iconv -f GBK -t UTF-8) next to the 原文.txt setup note, since the body currently only states that non-UTF-8 (常见为 GBK) input must be converted before subagents read it.

DimensionReasoningScore

Conciseness

The ~90-line body orchestrates a 7-stage pipeline with zero filler: no general concepts are explained, and every line carries operational content (e.g. "已有摘要一律不覆盖:要重拆某章就删掉它的 `章节/第N章_摘要.md` 和覆盖它的 `_analysis_cache/批次-*.md`"). It matches the score-5 anchor — lean, assumes competence, every token earns its place — with nothing to trim down to score 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Phase 1 provides a fully executable checker command ("{PYTHON}" .../scripts/inspect_existing_assets.py --root "拆文库/{书名}" --compact) plus the Python-resolution and directory conventions, and subcommands are named with intent flags (plan --intent continue, digest, mark-stage). However, full invocations for those stage commands are deferred to reference files rather than being copy-paste ready in the body, matching score 4 ('mostly executable; concrete commands with minor gaps') rather than 5.

4 / 5

Workflow Clarity

The multi-stage sequence is explicit (Stage 0→1→stop-and-ask→2–6, gated by Phase 1/2 checker output) with validation checkpoints throughout: the read-only checker, index validation rules ("落表前校验章号连续、无重复和边界有效"), "路径错误必须停止", per-stage disk markers (标 stageN), and final-checks.md. Feedback loops are present for error recovery (repair_stages/enhance_existing paths, index-rebuild fallback with author-facing options, invalid_topic_decision_contract → rerun story-long-scan Phase 5), and batch extraction is bounded ("Stage 2 默认每轮 3 批有限并行") with cache-based resume — matching the score-5 anchor.

5 / 5

Progressive Disclosure

The 按时刻读 table routes each working moment to exactly the reference file needed, all 12 referenced files exist in references/, and the structure is hub-and-spoke: every reference is one level deep, directly linked from SKILL.md (sibling cross-links are conveniences, not hidden chains), with scripts bundled and invoked by path. This matches the score-5 anchor — clear overview, well-signaled one-level-deep references, easy navigation.

5 / 5

Total

19

/

20

Passed

Description

96%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 clearly and explicitly answers both what the skill does and when to use it, with a comprehensive, concrete capability list and an explicit trigger section containing slash commands, six natural phrases, and a file-path condition. The only weakness is minor overlap risk with the companion short-analysis skill through form-agnostic phrases like 「拆这本书」.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "保留黄金三章、逐章摘要、剧情、情绪、节奏、角色、设定和文风接口,以连续章节块完成因果、双时间线、关系与三维节奏分析" — plus resume/enhance paths and a three-layer inspiration-library pipeline, covering the whole analysis workflow. It exceeds the score-4 anchor ('several specific actions; minor gaps') because coverage spans extraction through synthesis through optional pipelines with no obvious capability left vague.

5 / 5

Completeness

Both questions are answered explicitly: 'what' via the concrete capability list (逐章摘要、剧情、情绪、节奏、角色、设定、文风、因果/双时间线/关系/节奏分析), and 'when' via the dedicated "触发方式:" clause with concrete trigger phrases and a file-path condition. This matches the score-5 anchor exactly; a 'Use when...' style clause is present, so the completeness cap of 3 does not apply.

5 / 5

Trigger Term Quality

An explicit trigger section gives two slash commands (/story-long-analyze, /长篇拆文), six natural user phrases (「帮我拆这本书」「拆这本书」「分析黄金三章」「深度拆解」「完整拆解」), and a file-path trigger, which is comprehensive synonym coverage of how a Chinese web-novel author would naturally request this. It fits the score-5 anchor better than score 4 because the phrase set includes multiple synonymous variations rather than just 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (长篇网文拆文 — long-form web novel deconstruction with named deliverables), but generic trigger phrases like 「拆这本书」「深度拆解」 do not distinguish long-form from the companion short-form skill referenced in the body (/story-short-analyze), creating minor overlap risk with a closely related skill. This fits the score-4 anchor ('mostly distinct; minor overlap risk with closely related skills') rather than 5, whose example triggers are unambiguously domain-specific.

4 / 5

Total

19

/

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