BC browser-douyin-post
Use OpenClaw's browser control to publish images or videos to Douyin (抖音) creator platform. Uploads a local image/video file to Douyin creator center via the web UI. Prerequisites: (1) Chrome must be running with remote debugging enabled (--remote-debugging-port=9222), (2) user must be logged into Douyin creator platform (creator.douyin.com). Activates when user asks to post something to Douyin, publish to Douyin, or upload to Douyin.
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use OpenClaw's browser control to publish images or videos to Douy… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1182 tokens
- 100Running it twice. Mutating operations check current state
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 438: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.