Multi-Platform Self-Media Publisher

Problem

Publishing self-media content often means repeatedly logging into back offices such as Qiehao, Sohu, Dayu, and Sina, then manually entering the title, body text, cover image, and category. This skill turns that repetitive workflow into a browser-automation process, reducing manual switching and duplicate form entry across platform dashboards.

How It Works and Limits

• It requires a local graphical environment and OpenClaw browser tool; headless cloud servers cannot run the browser automation directly.
• Target platform accounts must already be logged in through a local browser, and the skill reuses the saved login state.
• The core flow opens each platform’s publish URL, waits for the page to load, fills in the title and body, uploads a cover image when needed, selects a category or content type, and then clicks publish.
• It supports publishing to a specific platform, batch publishing across platforms, and creating then publishing content; the documented concrete steps are mainly for article-style back offices.
• Platform constraints vary: Qiehao and NetEase recommend images, Dayu requires a cover image and suggests 800+ characters, Sina has Weibo-style length limits, and NetEase suggests 500+ characters.
• Keep risk control in mind: avoid large bursts of publishing, duplicate content, or sensitive terms; if publishing fails, check content rules, title length, login state, and the local browser environment.