CtrlK
BlogDocsLog inGet started
Tessl Logo

novel-review

小说章节审核 - 当需要校对、审核小说章节质量时触发。关键词:审核、校对、审稿、检查、质量评估。

68

Quality

81%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable review rubric with a clear workflow, concrete cross-check sources, a severity scheme, and a properly separated template reference. Its main weaknesses are mild verbosity across the seven review dimensions and the absence of explicit validation checkpoints in the workflow.

Suggestions

Tighten the 审核维度 section: collapse the seven dimension blocks into a compact checklist, since many bullets ('语言是否流畅自然?') are self-evident to a competent reviewer and add token cost.

Add an explicit validation checkpoint to 审核工作流, e.g. after step 3 ('逐维度分析') insert '确认 7 个维度均已覆盖且无遗漏' before proceeding to grading.

Consider splitting the seven review dimensions and the severity grading rubric into a separate reference file (e.g. references/review-criteria.md), keeping SKILL.md as a lean overview that points to both the criteria and the report template.

DimensionReasoningScore

Conciseness

The body is well-organized and free of generic concept-padding, but at ~130 lines with seven review dimensions each expanded into four bullets, it is somewhat exhaustive and could be tightened. Not a 3 because several bullets are self-evident to a competent reviewer; not a 1 because there is no Claude-already-knows bloat.

2 / 3

Actionability

Provides concrete executable guidance: specific file paths to cross-check ('设定/characters.md', 'summary/'), a defined Red/Yellow/Green severity scheme, a 7-step workflow, and a pointer to a report template. Per the rubric's instruction-only scoring note, the absence of code is not penalized since the guidance is concrete and actionable. Not a 2 because the directions are specific and end-to-end executable.

3 / 3

Workflow Clarity

The numbered 审核工作流 gives a clear 7-step sequence, but there are no explicit validation checkpoints or feedback loops within it (e.g., verifying all dimensions are covered before grading). Not a 1 because the sequence is complete and clear; not a 3 because checkpoints are implicit rather than explicit. The destructive-operation cap is not triggered since this is a read-only review task.

2 / 3

Progressive Disclosure

The body is an overview that delegates the detailed report format to a verified one-level-deep reference ('references/review-template.md'), which exists in the bundle. Not a 2 because the split is appropriate and the reference is clearly signaled rather than inline content that should be separated.

3 / 3

Total

10

/

12

Passed

Description

90%

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 is strong: it explicitly covers both what the skill does and when to trigger it, with a good set of natural-language keywords. The only minor weakness is that it frames a single composite action rather than enumerating several distinct capabilities.

DimensionReasoningScore

Specificity

Names the concrete domain (小说章节审核) and core action (校对/审核质量), but describes a single composite task rather than listing multiple distinct concrete actions. It is not a 1 because it does specify a real domain and action, and not a 3 because it lacks a multi-action enumeration like 'extract/fill/merge'.

2 / 3

Completeness

States what it does ('校对、审核小说章节质量') and explicitly when to trigger ('当需要校对、审核小说章节质量时触发'), satisfying both halves with an explicit 'Use when'-equivalent clause. Not a 2 because the 'when' is explicit rather than implied.

3 / 3

Trigger Term Quality

Explicitly enumerates natural user keywords ('审核、校对、审稿、检查、质量评估') alongside an explicit trigger clause ('当需要...时触发'), covering common natural variations. Not a 2 because the terms are genuinely natural and explicitly listed rather than merely present.

3 / 3

Distinctiveness Conflict Risk

The novel-chapter-review niche is specific and the trigger terms are domain-anchored, making conflict with unrelated skills unlikely. Not a 2 because the domain is clearly bounded despite '检查/质量评估' being somewhat generic on their own.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wanikua/danghuangshang
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.