CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huashu-script-polish

视频脚本口语化审校,去书面腔让脚本适合说出来。当用户提到"口语化"、"太书面了"、"像说话一样"、"脚本审校"时使用。

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./huashu-script-polish/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured, genuinely actionable instruction skill with a clear three-pass workflow, concrete rewrite examples, and useful numeric constraints. Its weaknesses are external: the reference section points at machine-local absolute paths that don't exist in the bundle, and the promotional footer plus a hard-coded update date waste tokens.

Suggestions

Progressive disclosure: copy the referenced materials (AI味审校指南, subtitle samples, 素材库) into a references/ folder inside the skill and point to them with relative paths (e.g., references/ai-flavor-guide.md) so they resolve wherever the skill is installed.

Progressive disclosure: if the external resources cannot be bundled, replace the absolute paths with a one-line description of what each resource provides so Claude knows what it is missing and can ask the user for it.

Conciseness: remove the personal-branding footer and the "最后更新: 2025-11-07" line — they consume tokens without guiding execution, and a hard-coded date goes stale.

DimensionReasoningScore

Conciseness

The body is lean — tight checklists, ❌/✅ rewrite pairs, and a 20-char sentence rule with no explanations of concepts Claude already knows. Not a 5 because the trailing branding footer ("花叔出品 | 公众号... | 代表作...") and the "最后更新: 2025-11-07" line are tokens that earn no place in a skill file; not a 3 because beyond that footer the content is efficient, merely padded rather than explanatory.

4 / 5

Actionability

Gives concrete, executable guidance for an instruction-only skill: specific rewrite pairs ("接下来我们将进行..." → "我们来..."), named filler words to add ("其实", "你看"), a worked before/after example, and numeric constraints (≤20 chars per sentence, 150-180 chars/minute). Not a 5 because key execution details are missing — e.g., how to handle unavoidable technical terms, how much filler is too much, and what to do when the source draft is a video lacking a demo to annotate.

4 / 5

Workflow Clarity

The three-pass sequence (内容审校 → 口语化审校 → 演示标注) is clearly ordered with checklists, and "大声读一遍,卡顿的地方重写" plus "模拟实际录制流程" act as validation checkpoints with a fix-retry loop. Not a 5 because the first pass's fact-accuracy and demo-feasibility checks have no stated verification method, leaving those checkpoints implicit; not a 3 because the sequence and most checkpoints are explicit.

4 / 5

Progressive Disclosure

Sections are well-organized and inline content is appropriately sized, but the "参考资源" section points at absolute paths outside the bundle ("/写作参考/AI味审校指南.md", "/视频创作/_srt/", "/写作参考/个人素材库/") and no references/ directory exists in the skill, so the references are unusable for anyone without that exact filesystem. This matches the anchor of references present but not effectively usable/signaled; not a 4 because broken non-bundle paths are more than a minor organization gap.

3 / 5

Total

15

/

20

Passed

Description

78%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 that states what the skill does and when to use it with concrete, naturally-spoken Chinese trigger phrases in proper third-person voice. The main gap is that it undersells the skill's scope, mentioning only two of the several actions the body actually performs.

DimensionReasoningScore

Specificity

"口语化审校" and "去书面腔让脚本适合说出来" name the domain plus two concrete actions (de-bookish the tone, make it speakable), but the description omits other capabilities the skill performs (multi-pass review, adding spoken-word fillers, demo/screen-cue annotation), so coverage is not comprehensive. Not a 4 because it lists only two actions rather than several; not a 2 because the actions given are concrete, not generic.

3 / 5

Completeness

Explicitly answers both: what ("视频脚本口语化审校,去书面腔让脚本适合说出来") and when ("当用户提到...时使用") with concrete quoted trigger phrases. Matches the anchor for clearly and explicitly answering both what and when with concrete triggers, in third-person verb-phrase voice.

5 / 5

Trigger Term Quality

Quotes four natural user phrases — "口语化", "太书面了", "像说话一样", "脚本审校" — that a user would plausibly say verbatim, giving good keyword coverage with synonym variation. Not a 5 because common variants like "AI味", "读起来别扭", or "视频脚本改写" are absent; not a 3 because multiple natural phrasings and their variations are already covered.

4 / 5

Distinctiveness Conflict Risk

The video-script colloquialization niche with quoted triggers like "太书面了" is mostly distinct and unlikely to fire for unrelated skills. Not a 5 because it could overlap with general writing/proofreading or SRT-subtitle editing skills that share the "脚本审校" trigger; not a 3 because the specific spoken-tone framing keeps overlap minor.

4 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alchaincyf/huashu-skills

Path

huashu-script-polish/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.