douyin-publish

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

Quality

62%

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

78%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 body is highly actionable with concrete commands, URLs, exit codes, and retry loops, and the publish workflow is clearly sequenced with validation. It loses points on conciseness (dated postmortems and duplicated strategy notes) and progressive disclosure (monolithic file plus a referenced doc that is absent from the bundle).

Suggestions

Extract the dated incident notes (2026-07-17 get-link, 2026-08-04 _check_logged_in mute) into a short 'CHANGELOG / historical context' reference file or a clearly labeled deprecation block so they stop competing with the main instructions.

Provide the referenced docs/post-deploy-verification.md (or drop the dead link) so the bundle's navigation resolves; consider moving the Pitfalls and Notes sections into a separate reference file.

Deduplicate the aweme_id capture explanation — it currently appears both in the get-link note and the 'aweme_id 捕获 + debug 日志' section — keeping it in one place.

Dimension	Reasoning	Score
Conciseness	Mostly efficient prose, but several dated incident postmortems (2026-07-17, 2026-08-04) and repeated explanations of the aweme_id capture strategy across sections pad the body; could be tightened without losing meaning.	3 / 5
Actionability	Fully executable: copy-paste ready bash commands for open-page, run, upload/fill/publish/get-link, plus concrete URLs, exit-code tables, and selector-level detail that cover the common cases.	5 / 5
Workflow Clarity	Clear multi-step sequence (open-page → login check → run, or stepwise upload→fill→publish→get-link) with explicit validation via exit codes, retry/backoff guidance for work_list status_code=8, and fail-first session handling — feedback loops present for this batch/network-fragile operation.	5 / 5
Progressive Disclosure	The body has reasonable section structure but is a single long SKILL.md with no reference files split out; it points to docs/post-deploy-verification.md which is not present in the bundle, so navigation is partly dangling.	3 / 5
	Total	16 / 20 Passed

Description

46%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 states a concrete, narrow domain but omits any 'Use when...' trigger guidance and only lightly enumerates capabilities. Adding explicit trigger phrases and a few concrete sub-actions (upload, fill metadata, publish, get-link) would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to publish or post a video to Douyin (抖音) / 抖音创作者中心, upload a video to Douyin, or retrieve a published Douyin video link.'

Expand the capability list beyond the single phrase '发布视频' to concrete actions such as upload video, fill title/caption, set AI declaration, publish, and retrieve the video link.

Include synonyms and the helper command surface (douyin-publish run/upload/fill/publish/get-link) so the description doubles as activation vocabulary.

Dimension	Reasoning	Score
Specificity	Names the domain ('发布视频到抖音创作者中心') and one concrete mechanism ('通过浏览器自动化'), but stops there — no enumerated actions like upload, fill, publish, get-link.	3 / 5
Completeness	Has a clear 'what' (publish videos to Douyin creator center via browser automation) but no 'when' — the missing 'Use when...' clause caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes the core natural terms 抖音/创作者中心/发布 but is missing the 'Use when...' trigger clause, common synonyms, and any mention of sub-actions; not comprehensive enough for a 3.	2 / 5
Distinctiveness Conflict Risk	The narrow niche (Douyin creator center publishing via camoufox) is clearly distinct from other skills with only minor overlap risk; not a 5 because no explicit triggers delineate it further.	4 / 5
	Total	12 / 20 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: fdc03d6

Reviewed: 11 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.