CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-publish

小说发布准备:调用即生成并保存发布资料,缺失字段留空;按平台整理书名、笔名、分类、标签及所需简介。触发方式:/story-publish、/发布资料、「填写平台建书资料」「建书表单」「起书名/写简介/选标签用于发布」;正文累计约 2 万字、准备上架时也适用。当前适配番茄长篇与短故事(短故事无需简介),不代替后台填表或实际发布。

Quality

94%

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

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 dense, highly operational skill body: concrete file contracts, a complete output template, explicit status semantics, and a validation script with fix-and-rerun feedback loops and manual fallback. The only weaknesses are mild redundancy across sections and a two-hop reference chain for platform tag data.

Suggestions

Consolidate the leave-blank rule into one authoritative statement (e.g., in 原则) and reference it from the workflow and file-format sections instead of restating it, trimming the repeated '番茄短故事无需简介' mentions to one.

Split the long multi-clause sentences in 封面 and 发布资料文件 into bulleted rules so each constraint (tool probing, mode selection, fallback behavior) is individually scannable.

In SKILL.md's 平台 section, briefly name the tag reference files that fanqie.md dispatches to (e.g., 阅读标签/内容标签 files) so the second-level references are visible from the entry point.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — no concept explanations, all operational rules — but a few rules are restated across sections (the leave-blank rule appears in 原则, 工作流程 step 5, and 发布资料文件; "短故事无需简介" appears three times), and sentences in 封面 and 发布资料文件 pack 5+ rules each. These are minor tightening opportunities, matching 'efficient with minor instances that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact file names (发布资料-<平台>.md), exact source files to read (设定/题材定位.md, 大纲/大纲.md), a fixed set of field states (已确认/建议/待确认/待平台核实), a complete output template in a code block, and a concrete check command with interpreter probing order (python3/python/py). This matches the top anchor for copy-paste-ready, common-case-covering guidance.

5 / 5

Workflow Clarity

The 6-step 工作流程 is clearly sequenced, and validation is explicit with a feedback loop: 格式检查 runs scripts/check-publish-format.py after save, FAIL means fix and re-run, WARN is relayed to the author, and there is a documented manual fallback when the script cannot run plus handling for write failures. Existing author edits are protected by the read-first/conflict-branch rule, so the risky file-overwrite path is validated.

5 / 5

Progressive Disclosure

Structure is good and all referenced files exist (references/fanqie.md, four tag files, scripts/check-publish-format.py), with SKILL.md keeping bulky tag vocabularies out of the main body and the platform section explaining how to extend to new platforms. However, reaching tag data requires two hops (SKILL.md → fanqie.md → fanqie-reading-*.md / fanqie-content-tags.md), so references are not strictly one-level-deep from the entry point — a minor organization gap versus the top anchor.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: it states the concrete deliverable and field set, gives an explicit trigger list with natural user phrases and a usage milestone, defines platform scope, and explicitly bounds what the skill does not do. Both 'what' and 'when' are answered clearly and in third person.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "调用即生成并保存发布资料,缺失字段留空" and "按平台整理书名、笔名、分类、标签及所需简介" — naming the exact field set it produces. Coverage of the skill's scope is comprehensive for its niche, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

Both what and when are explicit: the opening sentence states the concrete deliverable, and "触发方式:..." gives a full trigger list with concrete phrases. It also adds scope boundaries (supported platforms, what it does not replace), exceeding the anchor's requirement.

5 / 5

Trigger Term Quality

Trigger phrases are comprehensive and natural: "/story-publish、/发布资料、「填写平台建书资料」「建书表单」「起书名/写简介/选标签用于发布」" plus the milestone trigger "正文累计约 2 万字、准备上架". These cover slash commands, task phrases, and synonyms (发布资料/建书/上架) a user would actually say.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (publishing-prep materials for web-novel platforms) and actively reduces conflict risk with "不代替后台填表或实际发布", distinguishing it from a publishing/submission skill; triggers like "建书表单" are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 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

Total

14

/

16

Passed

Repository

zenstory-ai/oh-story-claudecode

Path

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