CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huashu-douyin-script

抖音爆款脚本创作工作流。从竞品视频拆解到脚本生成的完整流程:下载抖音视频→Gemini视频分析→爆款公式提炼→脚本+分镜生成→AI味审校。 当用户提到"抖音脚本"、"爆款拆解"、"竞品分析"、"带货脚本"、"千川素材"、"种草脚本"、"视频拆解"、"抖音视频分析"时使用此技能。

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced workflow skill with real executable commands, complete prompt templates, confirmation checkpoints, and a clean one-level-deep bundle. Its main weakness is token efficiency: the inline Step 3 prompt duplicates a reference file, and promotional footer content pads the file.

Suggestions

Replace the ~55-line inline Step 3 analysis prompt with a pointer to references/analysis-dimensions.md (e.g., 'build the --prompt from the 7-dimension framework in references/analysis-dimensions.md'), eliminating the duplicated hook taxonomy and cutting roughly 60 lines.

Remove the personal branding footer (「花叔出品 | 公众号…」) — it consumes context tokens without contributing to task execution.

Either bundle the two sibling skills referenced in Step 6 (「视频脚本口语化审校」, 「ai-taste-proofreading」) or replace those name references with the actual rules inlined in Step 6, so no instruction depends on unavailable resources.

DimensionReasoningScore

Conciseness

The 373-line body carries genuine domain knowledge Claude lacks (Douyin ad-compliance rules, oral-style constraints), but the ~55-line Step 3 analysis prompt substantially duplicates references/analysis-dimensions.md (same 7 dimensions, same hook-type taxonomy), hook-type lists are repeated again in Step 5's Part B requirements, and the personal branding footer (「花叔出品 | 公众号…」) is pure padding. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'; it is above 2 because the verbosity is duplication rather than explaining concepts Claude already knows, and below 4 because the duplication is structural, not minor.

3 / 5

Actionability

Commands are copy-paste ready (`uv run SKILL_DIR/scripts/download_douyin.py --urls "URL1" "URL2" --output-dir _temp/douyin-downloads`), both script-generation prompt templates are complete with clearly marked fill-in variables, output paths are specified, and failure fallbacks (manual download, MCP fallback) cover the common failure case. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'; the SKILL_DIR placeholder is explicitly instructed to be resolved first, so it is not a gap.

5 / 5

Workflow Clarity

The 6 steps are strictly sequenced with two explicitly flagged user-confirmation checkpoints (Step 4 「← 用户确认节点」, Step 6), a 5-item review checklist in Step 6, error-recovery fallbacks in Step 2, parallelization guidance (run_in_background=true), and two complete alternate paths (with/without competitor videos) in 快速使用. This matches the score-5 anchor's 'explicit validation steps; feedback loops for error recovery; checklists'; there are no validation gaps to drop it to 4.

5 / 5

Progressive Disclosure

All five referenced bundle files exist, are one level deep, and are indexed in a 参考资源 table with per-file purpose — good navigation. It is not 5 because the Step 3 analysis prompt should live in (or defer to) references/analysis-dimensions.md instead of duplicating it inline, and Step 6 cites two sibling skills by name (「视频脚本口语化审校」skill, 「ai-taste-proofreading」skill) without paths, which is a dangling reference. It is well above 3 because the split between SKILL.md, references/, and scripts/ is otherwise appropriate and clearly signaled.

4 / 5

Total

17

/

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.

An exemplary description: a concrete multi-step capability statement paired with an explicit 'use when' clause containing eight natural trigger terms. The only minor weakness is that two trigger phrases (竞品分析, 视频拆解) are generic enough to invite overlap with adjacent skills.

DimensionReasoningScore

Specificity

The description enumerates a concrete end-to-end pipeline — 「下载抖音视频→Gemini视频分析→爆款公式提炼→脚本+分镜生成→AI味审校」 — five specific, distinct actions rather than vague domain language. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because no meaningful capability in the workflow is left unlisted.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the named pipeline steps and 'when' via 「当用户提到…时使用此技能」 with concrete trigger phrases — the exact pattern of the score-5 anchor example. It is not score 4 because the 'when' clause is fully explicit with enumerated triggers, not merely present.

5 / 5

Trigger Term Quality

It lists eight natural trigger phrases users would actually say: 「抖音脚本」「爆款拆解」「竞品分析」「带货脚本」「千川素材」「种草脚本」「视频拆解」「抖音视频分析」, covering domain synonyms across both content styles (种草/千川). This matches the comprehensive-synonyms anchor; score 4 would require noticeable missing natural terms, and none are evident.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (Douyin e-commerce short-video scripts) and most triggers are platform-specific, but 「竞品分析」 and 「视频拆解」 are generic terms that could overlap with non-Douyin marketing-analysis or video-analysis skills. This fits 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because two of the eight triggers are not domain-locked, and not 3 because the dominant triggers (抖音脚本、千川素材、种草脚本) are unmistakably specific.

4 / 5

Total

19

/

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-douyin-script/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.