CtrlK
BlogDocsLog inGet started
Tessl Logo

viral-video-copywriting

自媒体创作者与运营专员在缺乏爆款方法论、需拆解对标视频时使用。当需要创作短视频文案时,自动提取抖音视频信息并深度拆解开头钩子等爆款因素,一键生成符合爆款规律的原创文案,助你轻松打造高赞爆款内容。

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/viral-video-copywriting/viral-video-copywriting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The skill delivers a well-sequenced, actionable five-step workflow with concrete constraints, a fallback path, and validation checkpoints — genuinely strong on actionability and workflow clarity. Its two real weaknesses are token efficiency (frontmatter and reference content duplicated inline, plus a triple-repeated output template) and progressive disclosure (an orphan script file, an external absolute script path, and inline duplication of the analysis reference).

Suggestions

Cut the ~50 lines of step-2 analysis questions and the duplicated 前置准备 dependency block; replace them with a one-paragraph summary plus the existing pointer to references/analysis-framework.md, and state the output template once with 'repeat for versions B and C' instead of implying it three times.

Fix the script invocation to use the bundle-relative path (scripts/extract_douyin_video.py) instead of the hardcoded '/workspace/projects/viral-video-copywriting/...' absolute path in both the step-1 command and the 测试命令 section.

Either reference scripts/test_workflow.py from the 测试验证 section (it exists in the bundle but is never mentioned) or remove it from the bundle so every file is discoverable.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the dependency list is duplicated verbatim from the frontmatter, the six-dimension analysis question lists in step 2 (~50 lines) duplicate references/analysis-framework.md, the step-4 output template is spelled out three times over, and the 注意事项 section repeats earlier '重要说明' content plus filler like '充分利用智能体的语言分析和创作能力'. Not 3 because the duplication is structural rather than loose wording; not 1 because the content is domain-specific rather than explaining concepts Claude already knows.

2 / 5

Actionability

Mostly executable guidance: an exact bash invocation for the extraction script, a concrete manual-fallback input list, hard numeric constraints (±5% on word counts and duration), a parameter comparison table, and a worked end-to-end example. The gap is that the script is invoked via a hardcoded absolute path ('/workspace/projects/viral-video-copywriting/scripts/extract_douyin_video.py') that does not match the skill's actual bundle location, so the command as written can fail. Not 5 because of the path mismatch; not 3 because commands, constraints, and templates are concrete, not pseudocode.

4 / 5

Workflow Clarity

The five-step sequence is clearly ordered with real checkpoints: an explicit fallback loop in step 1 (script blocked by anti-scraping → mode B manual input), an originality check plus a quantitative ±5% deviation table in step 4, and an iteration loop in step 5. Minor gaps: no validation that the step-2 analysis report matches the framework's template, and no guidance on what to do when the user skips the step-3 clarification. Not 5 because error-recovery beyond step 1 is implicit; not 3 because validation is explicit in steps 1 and 4, not missing.

4 / 5

Progressive Disclosure

Structure exists and the 资源索引 section signals each bundle file with purpose and read-when ('何时读取:第二步拆解分析时'), but step 2 inlines ~50 lines of analysis-dimension content that duplicates references/analysis-framework.md instead of deferring to it, scripts/test_workflow.py is an orphan bundle file never referenced from SKILL.md, and both script invocations point to an external absolute path rather than the bundle's own scripts/ directory. Not 4 because the duplication and orphan script exceed minor gaps; not 2 because references are clearly signaled with an explicit index rather than buried.

3 / 5

Total

13

/

20

Passed

Description

83%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 names the audience, gives three concrete capabilities, and includes two explicit 'use when' trigger clauses with natural domain keywords. Its main flaws are the second-person marketing flourish ('助你轻松打造高赞爆款内容') and the '一键生成' over-claim, which pad without adding capability information.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('自动提取抖音视频信息', '深度拆解开头钩子等爆款因素', '生成符合爆款规律的原创文案'), approaching the comprehensive anchor, but the second-person marketing tail '助你轻松打造高赞爆款内容' (a specificity penalty per guidelines) and the over-claim '一键生成' keep it below 5.

4 / 5

Completeness

It explicitly answers both questions: 'what' via three concrete capabilities (extract video info, deconstruct viral factors, generate original copy) and 'when' via explicit trigger clauses ('当需要创作短视频文案时', '在缺乏爆款方法论、需拆解对标视频时使用'), matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage for the domain (短视频文案, 爆款, 抖音, 对标视频, 开头钩子, 高赞), but common user variations like '写文案', '口播稿', or platform alternatives are missing, so it stops short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

The Douyin benchmark-deconstruction niche is distinct with specific triggers, but a bare request like '帮我写个文案' could overlap with generic copywriting or writing skills, so minor overlap risk remains.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anbeime/skill
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.