CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

story-deslop

网文去AI味。从表达、叙事用笔、故事因果三层诊断并修复文本,保留作者文风与已定剧情。触发方式:/story-deslop、/去AI味、「去AI味」「这篇太AI了」「网文去AI味」。

Quality

92%

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.

A well-engineered process skill: five clearly sequenced phases with backups, scripted validation, bounded feedback loops, and disciplined load-on-demand references, all backed by real bundle files. The single weakness is density — the agent-compatibility/version blockquote and a few duplicated handoff rules could be moved or trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense with operational rules and contains no padding or explanation of concepts Claude already knows; nearly every sentence is a boundary, decision rule, or step. However, the Agent-compatibility blockquote (four hosts' config paths and the multi-branch agents_version notice) is detail that could be trimmed or moved into agent-calls.md, and some rules (e.g. the /story-long-write handoff) appear in both 执行边界 and 流程衔接. This lands at anchor 4 (efficient, minor trimmable instances) rather than 5.

4 / 5

Actionability

Guidance is fully executable: exact commands with flags and exit-code semantics ("node scripts/check-ai-patterns.js --check --fail-on=blocking <正文文件...>", "退出 1 表示有 blocking,退出 2 是命令或文件错误"), a concrete backup path convention (".story/work/去味原稿/{YYYYMMDD}_{原文件名}"), explicit loop limits ("全文扫描最多三轮"), quote-mode flags, and two copy-paste report templates. All cited scripts and reference files exist in the bundle. This matches anchor 5 (copy-paste ready commands covering common cases).

5 / 5

Workflow Clarity

The five phases (Phase 1–5) are clearly sequenced, and the file-editing workflow has explicit validation and feedback loops: backup before edit, Phase 4 回读 against the original and set designs, re-scan with --fail-on=blocking, regenerate damaged segments on degeneration blocking, and bounded retry ("没有新问题即停…最多三轮"). This matches anchor 5 (clear sequence, explicit validation, error-recovery loops).

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview: a table maps the three method files to what each checks, and every reference is load-on-demand with an explicit read condition ("完整词条仅在需要定位某种表达时查 banned-words.md", "只在此时读 agent-calls.md", "短篇另读 short-deslop.md"). All 8 referenced files and 4 scripts exist, and references are one level deep with no pointer chains hiding content — matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

92%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 exactly what the skill does across three named layers, what it preserves, and when to invoke it, with natural Chinese trigger phrases and slash commands. The only gap is minor synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

"从表达、叙事用笔、故事因果三层诊断并修复文本,保留作者文风与已定剧情" names the domain and multiple concrete operations — diagnose, fix, and preserve — organized across three explicitly named layers, giving comprehensive coverage of the skill's function. It fits the 5 anchor (multiple specific concrete actions, comprehensive) better than 4, since nothing material about the skill's capability is left out.

5 / 5

Completeness

The 'what' is explicit ("从表达、叙事用笔、故事因果三层诊断并修复文本,保留作者文风与已定剧情") and the 'when' is explicit with concrete trigger phrases ("触发方式:/story-deslop、/去AI味、「去AI味」「这篇太AI了」「网文去AI味」"), which is the equivalent of a 'Use when…' clause. This clearly matches anchor 5 (both what and when with concrete triggers), not anchor 4 where the 'when' could be more explicit.

5 / 5

Trigger Term Quality

Triggers include "去AI味", "这篇太AI了", "网文去AI味" plus slash commands "/story-deslop" and "/去AI味" — natural phrases a web-novel author would actually say. A few common variants (e.g. 「AI味太重」「机器味」「AI感」) are missing, which matches anchor 4 (good coverage, a few natural terms missing) rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is precise (AI-flavor removal for serialized web fiction) and the trigger terms ("去AI味", "这篇太AI了") are unique to this skill, so it occupies a clear niche with distinct triggers and minimal conflict risk — anchor 5. It is far more specific than the anchor 3/4 examples whose domain words overlap with sibling skills.

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