Tessl • The management layer for AI agent skills

The body is an exemplary operational skill document: every instruction is an executable command or a concrete stop/recovery rule, the publish workflow is sequenced with explicit validation and confirmation gates, and detail is correctly delegated to two well-signaled one-level-deep references. The only tighten-able spot is mild duplication of the caption-file rules between the body and the reference files.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no concept explanations or filler — commands, exit codes, and stop conditions only. Score 4 rather than 5 because the `--caption @文件` rules paragraph is long and its rules are restated in both references/video.md and references/note.md, so a few sentences could be trimmed or delegated.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with complete flags and absolute paths ("douyin-publish video run --video /绝对路径/video.mp4 --title … --cover-vertical …"), plus concrete exit codes (2/3/4) and named error codes (COVER_BORDER_TOO_LARGE, COVER_UPLOAD_TIMEOUT) each paired with a specific recovery subcommand. The common video and image-text cases are both covered.	5 / 5
Workflow Clarity	The sequence is explicit — check → preview without --confirm → confirm → run → SMS verify (verify-send/verify-code/resume) → get-link → report — with validation gates throughout: preview-before-confirm, stop conditions ("缺视频、标题或双封面即停止，不点击发布"), error-recovery feedback loops ("先用 video status 核查并续编当前草稿，不重传"), and post-submit verification rules ("禁止自动重发", "已尝试提交，正在核实").	5 / 5
Progressive Disclosure	A ~48-line overview with clear sections, appropriately splitting stepwise detail into references/video.md and references/note.md, which are real files referenced one level deep with no nested references. Links are well-signaled at the exact decision points ("视频分步操作、草稿修复与短信续接先读 [视频操作说明](references/video.md)"), and implementation scripts live in scripts/.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is specific and highly distinctive, naming the platform, session mechanism, and six concrete capabilities in a single compact sentence. Its one material weakness is the complete absence of any "Use when…" trigger guidance, which both caps completeness and slightly limits how reliably a user's request would surface this skill.

Suggestions

Append an explicit trigger clause, e.g. "用于需要在抖音发布视频或图文、续接短信验证或取回作品链接时" so the "when" is answered alongside the "what".

Add one or two natural user-side synonyms such as "上传到抖音" or "抖音作品/抖音号" to broaden trigger term coverage toward the top anchor.

Optionally mention the 3:4/4:3 dual-cover requirement in the capability list, since it is a hard precondition for video publishing and currently a coverage gap.

Dimension	Reasoning	Score
Specificity	The description lists six concrete actions — "登录并发布抖音视频或图文", "本地预览", "分步填表与配乐", "短信续接", "取链" — covering the publish lifecycle. Score 4 rather than 5 because coverage has minor gaps (cover preparation, AIGC declaration, draft repair are unmentioned).	4 / 5
Completeness	The "what" is clear and multi-part, but there is no "Use when…" clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because "when" is entirely absent rather than merely imprecise; not 2 because the "what" is concrete.	3 / 5
Trigger Term Quality	Natural phrases a user would say appear verbatim: "抖音", "发布", "视频", "图文", "登录", "取链". Good keyword coverage but not comprehensive — common variants like "上传", "作品" or "抖音号" are missing, so it falls short of the anchor-5 example's synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	"Camoufox 持久化创作者会话" combined with "抖音" defines a clear niche with distinct triggers; no realistic overlap with generic publishing or media skills. Matches the anchor-5 example of a distinct niche with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: TeamWiseFlow/xiaobei
Path: crews/main/skills/expert-douyin/tools/douyin-publish/SKILL.md
Revision: 47aea0b

Reviewed: 6 days ago

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.

douyin-publish

Table of Contents

Is this your skill?