viral-chaser

下载分析抖音/B站/小红书爆款视频，生成追爆报告。仅产出报告，脚本另外使用 video-product 技能根据追爆报告.md 生成。

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/viral-chaser/SKILL.md

Quality

Content

77%

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

The body is a strongly actionable, well-sequenced production workflow with explicit error-recovery checkpoints and a complete output schema, but it is front-loaded with verbose ASR provisioning prose and carries a broken _shared/* reference that holds back conciseness and progressive disclosure.

Suggestions

Move the detailed 火山 ASR provisioning/auth guide into a separate reference file (e.g., references/asr-setup.md) and keep only the essential env-var table + a one-line link in SKILL.md.

Fix or remove the inline references to _shared/check-session.ts and _shared/xhs-html-note.ts, which do not exist in the provided scripts bundle; either add those files or point to the actual session.ts / platforms/xhs.ts paths.

Trim explanatory rationale (e.g., why subagents help) to one line so the operational steps stay token-efficient.

Dimension	Reasoning	Score
Conciseness	The core workflow is operational and Claude-specific, but the front-loaded ASR provisioning prose (console navigation, auth-quirk blockquotes, interface-selection rationale) and the subagent rationale are padded enough to keep it at "mostly efficient but could be tightened."	2 / 3
Actionability	It provides copy-paste-ready commands (mkdir, viral-chaser <url> [--no-frames]), the exact stdout JSON schema, explicit env vars, and concrete Read-tool usage, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (workspace → analyzer → frames → framework → handoff) with explicit validation checkpoints: exit codes 0/1/2, SESSION_EXPIRED retry-once via login-manager, SIGN_UNAVAILABLE escalation, and the transcript.estimated flag handling.	3 / 3
Progressive Disclosure	There is section structure and a real scripts bundle, but content that could be split (the long ASR provisioning guide) is inline, and inline references to _shared/check-session.ts and _shared/xhs-html-note.ts do not exist in the bundle, so references are present but not cleanly signaled/organized.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 concretely lists download/analyze/report actions over a named platform niche with a clear scope boundary against the video-product skill, but it omits any explicit "Use when..." trigger guidance, which caps completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user provides a 抖音/B站/小红书 viral video link and wants to analyze its structure or make a similar video."

Include common natural variations of trigger terms (短链接、爆款分析、追爆、viral video) alongside the platform names.

Keep the video-product handoff but ensure the trigger guidance is stated in the description, not only implied by the niche.

Dimension	Reasoning	Score
Specificity	Concretely lists distinct actions ("下载分析...生成追爆报告") over a named platform domain (抖音/B站/小红书爆款视频), matching the multi-action anchor; it is not 2 because it enumerates specific concrete actions rather than naming only a domain.	3 / 3
Completeness	The "what" is clear (download/analyze viral videos and generate 追爆报告), but there is no explicit "when to use" trigger clause — per the guideline a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural platform keywords (抖音、B站、小红书、爆款视频) are present, but there is no "Use when..." phrasing and some common variations (e.g., short-link, viral analysis) are missing, so it stops at "some relevant keywords but missing variations."	2 / 3
Distinctiveness Conflict Risk	The platform niche is specific and the explicit boundary "仅产出报告...脚本另外使用 video-product 技能" cleanly distinguishes it from sibling skills, making conflict unlikely; voice is correctly third person.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: TeamWiseFlow/xiaobei
Path: crews/main/skills/viral-chaser/SKILL.md
Commit: bcef823

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.