Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计提醒

weibo-publisher微博发布者

Agent Skill

weibo-publisher 用于处理浏览器自动化、网页检查和页面信息提取,适合在 OpenClaw 中需要让 Agent 打开页面、读取网页或验证前端流程时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

19,053

周安装

786

GitHub Stars

公开资料未说明

下载量

6,225
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:weibo-publisher(微博发布者)
来源仓库:https://github.com/azfliao/weibo-publisher
安装命令:
openclaw skills install weibo-publisher
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install weibo-publisher

简介

使用浏览器自动化将帖子发布到微博(新浪微博)。当用户想要将内容发布到微博、在微博上分享更新、发布微博等时使用

SKILL.md

name
weibo-publisher
description
Publish posts to Weibo (Sina Weibo) using browser automation. Use when the user wants to post content to Weibo, share updates on Weibo, publish microblogs, or automate Weibo posting. Supports text posts with emoji, hashtags, and mentions. No API key required - uses browser automation with managed browser profile.

Weibo Publisher

Automate posting to Weibo (Sina Weibo) using browser automation through OpenClaw's managed browser.

Prerequisites

  • Weibo account must be logged in via managed browser (profile="openclaw")
  • Browser must have active session with valid cookies

Quick Start

Basic Post

# 1. Prepare content with Unicode escape (for Chinese text)
content = "刚刚解决了一个技术难题!💪"
escaped_content = content.encode('unicode_escape').decode('ascii')

# 2. Navigate to Weibo homepage
browser(action="navigate", targetUrl="https://weibo.com/", targetId=<tab_id>)

# 3. Get page snapshot to find elements
browser(action="snapshot", targetId=<tab_id>)

# 4. Click the post textbox (ref from snapshot, usually e31 or e136)
browser(action="act", request={"kind": "click", "ref": "e31"}, targetId=<tab_id>)

# 5. Type content with Unicode escape
browser(action="act", request={"kind": "type", "ref": "e31", "text": escaped_content}, targetId=<tab_id>)

# 6. Get fresh snapshot to find send button
browser(action="snapshot", targetId=<tab_id>)

# 7. Click send button (ref from snapshot, usually e32 or e194)
browser(action="act", request={"kind": "click", "ref": "e32"}, targetId=<tab_id>)

# 8. Wait and verify by navigating to profile
sleep(3)
browser(action="navigate", targetUrl="https://weibo.com/u/<your_uid>", targetId=<tab_id>)
browser(action="snapshot", targetId=<tab_id>)

Element References

Common element references on Weibo homepage (as of 2026-03-02):

  • Main post textbox: e31 (placeholder: "有什么新鲜事想分享给大家?")
  • Send button: e32 (text: "发送", becomes enabled after typing)
  • Quick post button (top nav): e10 (text: "发微博")
  • Quick post textbox (popup): e746 (when using quick post popup)
  • Quick post send button: e804

Important Notes:

  • Element references change frequently between sessions
  • Always take a fresh snapshot before each operation
  • Refs may differ between homepage (/) and profile page (/u/<uid>)
  • Send button is disabled until content is entered

Content Features

Supported Content Types

  1. Plain text: Direct text input
  2. Emoji: Include emoji directly in text (e.g., "😊🎉")
  3. Hashtags: Use #topic# format (e.g., "#微博话题#")
  4. Mentions: Use @username format
  5. Line breaks: Use `\

` in text

Content Limits

  • Maximum length: ~2000 characters (Weibo's limit)
  • Recommended length: 140-280 characters for better engagement

Workflows

Workflow 1: Simple Post

Use the main homepage textbox for quick posts:

  1. Open https://weibo.com/
  2. Snapshot to get element refs
  3. Click textbox (e136)
  4. Type content
  5. Click send (e194)
  6. Verify success

Workflow 2: Quick Post (Popup)

Use the "发微博" button for popup posting:

  1. Open https://weibo.com/
  2. Click "发微博" button (usually e75)
  3. Snapshot to get popup element refs
  4. Type in popup textbox (e1028)
  5. Click popup send button (e1086)
  6. Verify success

Workflow 3: Scheduled Post

For posts to be published later:

  1. Follow Workflow 1 or 2 to enter content
  2. Click "定时微博" icon (clock icon, ref varies)
  3. Select date and time
  4. Click send

State Management

Track posting history in memory/weibo-state.json:

{
  "lastPublishTime": 1740880260,
  "lastPublishDate": "2026-03-02T12:38:00+08:00",
  "lastContent": "Your last post content..."
}

Update this file after each successful post.

Error Handling

Common Issues

  1. "request: must be object" validation error

- Symptom: Validation failed for tool "browser": - request: must be object - Cause: Chinese quotation marks in text causing JSON parsing failure - Solution: Use Unicode escape for all Chinese characters (see Technical Details)

  1. Login expired

- Symptom: Redirected to login page - Solution: Manually log in via browser, then retry

  1. Send button disabled

- Symptom: Button has disabled attribute - Solution: Check if textbox is empty or content violates rules

  1. Element refs changed

- Symptom: Elements not found with old refs - Solution: Take fresh snapshot and use updated refs

  1. Content rejected

- Symptom: Error message after clicking send - Solution: Check for sensitive words, adjust content

  1. Post not appearing

- Symptom: No error but post doesn't show on timeline - Solution: Wait 5-10 seconds, refresh page, check if content triggered review

Best Practices

  1. Always use Unicode escape for Chinese: Prevents JSON parsing errors with quotation marks
  2. Always snapshot first: Element refs change frequently between sessions
  3. Separate operations: Click textbox → Type content → Snapshot → Click send (don't combine)
  4. Verify after posting: Navigate to profile page and snapshot to confirm post appears
  5. Rate limiting: Wait at least 60 seconds between posts to avoid restrictions
  6. Content quality: Keep posts engaging, use hashtags for visibility
  7. State tracking: Always update weibo-state.json after successful posts
  8. Handle emoji properly: Emoji work in Unicode escape format (e.g., \�\� for 💪)

Technical Details

Browser Automation

  • Profile: openclaw (managed browser)
  • Method: Chrome DevTools Protocol (CDP)
  • Session: Cookie-based, persists across restarts
  • No API needed: Pure browser automation

Request Format

Critical: The request parameter must be a JSON object, not a string:

// ✅ Correct
request={"kind": "type", "ref": "e136", "text": "content"}

// ❌ Wrong
request="{\"kind\": \"type\", \"ref\": \"e136\", \"text\": \"content\"}"

Unicode Escape for Chinese Content (IMPORTANT!)

Problem: Chinese quotation marks (""、'') in JSON text can cause parsing errors.

Solution: Use Unicode escape (\uXXXX) for all Chinese characters:

# Convert Chinese text to Unicode escape
text = "刚刚解决了一个技术难题,感觉特别有成就感!"
escaped = text.encode('unicode_escape').decode('ascii')
# Result: \刚\刚\解\决\了...

Example:

// ✅ Correct - Unicode escaped
request={"kind": "type", "ref": "e31", "text": "\刚\刚\解\决\了\一\个\技\术\难\题"}

// ❌ Wrong - Direct Chinese with quotes
request={"kind": "type", "ref": "e31", "text": "刚刚解决了一个"技术难题""}

Why: Chinese quotation marks conflict with JSON string delimiters, causing the request parameter to be serialized as a string instead of an object.

Reference Files

Scripts

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

93.23%
按下载量换算5,804

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills