douyin-publish

通过浏览器自动化发布视频到抖音创作者中心。纯浏览器操作方案。

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/douyin-publish/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 highly actionable with a clear, validated multi-step workflow and rich operational guidance, but it suffers from repeated explanations of the same strategy and a broken external reference that undermines its progressive-disclosure structure.

Suggestions

Create the referenced docs/post-deploy-verification.md (or remove/fix the citation) so the two inline references resolve to a real file.

Consolidate the get-link/work_list aweme_id strategy and the AI-declaration flow into single authoritative sections instead of restating them in 使用方式, aweme_id 捕获, and the ai_declaration_confirm pitfall.

Move dated incident notes (2026-07-17) into a 'Postmortems / old patterns' section so time-sensitive detail does not dilute the main instructions.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly operational (exit codes, selectors, API paths Claude would not already know), but the get-link/work_list strategy and the AI-declaration flow are each restated across multiple sections, and dated inline incident notes (2026-07-17) are not isolated in a deprecated section, so it could be tightened.	2 / 3
Actionability	It provides copy-paste-ready commands (douyin-publish run/upload/fill/publish/get-link with flags), exact creator-center URLs, concrete localStorage keys, and an exit-code table mapping each code to a caller action.	3 / 3
Workflow Clarity	The upload → fill → publish → get-link sequence is explicit, with validation checkpoints (draft-popup cleanup, aweme_id capture, login-expiry detection) and feedback loops (exit 2 → login-manager re-login, exit 3 → manual verification).	3 / 3
Progressive Disclosure	Sections are organized (使用方式, 必做约束, Exit codes, Pitfalls, Notes), but the only external reference, docs/post-deploy-verification.md, is cited twice and does not exist in the bundle, and detailed pitfall/strategy content that could live in separate files is kept inline.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 third-person, accurate, and narrowly scoped to a distinct Douyin-publishing niche, but it names only one action and omits any explicit 'Use when' trigger clause, leaving completeness and trigger coverage at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when publishing or scheduling a video to Douyin's creator center, or when the user asks to post/upload a video to 抖音.'

Enumerate the concrete actions (e.g. upload video, fill title/caption, set AI-generated declaration, publish, retrieve the video link) to raise specificity from a single action to multiple.

Include common natural trigger variations ('发抖音', '上传视频到抖音', 'douyin publish') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (抖音创作者中心) and one concrete action (发布视频 via 浏览器自动化), but lists only a single action rather than multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms a user might say ('发布视频', '抖音创作者中心', '浏览器自动化'), but coverage is limited to one phrasing with no common variations, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The niche is highly specific (Douyin creator-center video publishing via a named persistent session) and is unlikely to trigger for or conflict with other skills.	3 / 3
	Total	9 / 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/douyin-publish/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.