post-to-weibo_skill

Overview

This skill posts text and images to Weibo using a real Chrome browser instance to bypass anti-automation measures. It supports text posts with up to nine images, preview mode, and an explicit submit flag to publish. The tool runs scripts via bun and preserves login sessions after the first manual sign-in. It works on macOS, Linux, and Windows.

How this skill works

The skill launches a real Chrome/Chromium instance controlled through Chrome DevTools Protocol (CDP) to interact with Weibo like a human browser. Scripts live in the scripts/ directory and handle composing posts, uploading images, and optionally submitting the post. On first run you sign in manually; the session is saved so subsequent runs reuse the logged-in profile. There is a preview mode by default; use the --submit flag to actually publish.

When to use it

• Automating regular Weibo posts that include text and images.
• Publishing multiple images (up to nine) with one post.
• Integrating Weibo posting into a local automation or content pipeline.
• Testing post composition without publishing using preview mode.
• Using a real browser session to avoid anti-bot detection.

Best practices

• Run the first script interactively to complete the manual login and save the session.
• Always use preview mode for verification, then rerun with --submit to publish.
• Keep image files local and verify paths before running the script.
• Limit images to nine per post and respect Weibo's 2000 character limit for text.
• Use --profile to isolate or reuse specific Chrome profiles when needed.

Example use cases

• Post a short announcement with one image from a local script: npx -y bun scripts/weibo-browser.ts "Announcement" --image ./img.png
• Prepare a multi-photo update in preview mode before publishing: run without --submit to inspect the draft.
• Automate daily content updates by invoking the script from a cron job that passes text and image paths.
• Share event photos by supplying multiple --image flags (max 9) and then run with --submit.
• Use a custom Chrome profile directory with --profile to keep sessions and cookies separate.