OpenCLI Douyin Automated Content Publishing

Problem

Publishing to the Douyin creator center involves manual copy-paste, file uploads, transcoding waits, and verification codes. Naive scripts also break easily because of React forms, popups, and hidden file inputs. This skill turns those steps into a repeatable browser-automation workflow for article, image, and video publishing.

How It Works

• OpenCLI-driven: It controls an already logged-in Chrome/Chromium session using commands such as browser fill, browser upload, and browser eval.
• Form handling: Titles and summaries use browser fill; the article body is injected as HTML to avoid literal line breaks; type=number verification fields use native setters.
• Content types: Articles, image posts, and videos are supported. Image posts use standard uploads; article covers require intercepting Semi Design hidden file inputs and confirming the final state; videos can use the optional douyin adapter for a simpler publish command.
• Workflow closure: It covers publish buttons, SMS verification, expired sessions, and page-state checks to reduce repeated failures.

Boundaries

• The browser extension must be connected, and the creator.douyin.com session must remain valid.
• Publishing may trigger SMS verification, requiring manual code entry.
• The workflow is sensitive to DOM changes; when selectors or cover confirmation fail, inspect the current page state and re-check buttons.