Weibo Microblogging CLI

以 Bash CLI 封装微博开放平台 API，支持 OAuth2 授权、令牌信息查询、公共与用户时间线、话题搜索及通用接口调用，输出 JSON 供下游自动化；并附带基于 Brave 搜索的备用检索技能。需微博应用凭据与回调地址，依赖 curl 与 python3。

热度 67.40

最近更新 2026-05-18 12:09:39

分类：搜索依赖：代码执行 / 第三方 API应用场景：社交媒体 / 研究 / API 集成 / 自动化脚本 ...

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add weibo

Metadata

name: weibo
description: Use Weibo Open Platform for OAuth2 authentication, timeline retrieval, topic search, and structured social sentiment collection. Trigger this skill when tasks involve Weibo API calls, token setup, endpoint debugging, or Chinese social trend monitoring through the official Weibo API.
metadata: {"openclaw":{"skillKey":"weibo","homepage":"https://open.weibo.com/","requires":{"bins":["bash","curl","python3"],"env":["WEIBO_APP_KEY","WEIBO_APP_SECRET","WEIBO_REDIRECT_URI"]},"primaryEnv":"WEIBO_APP_SECRET"}}

Use this skill to collect Weibo signals with reproducible Weibo Open Platform API calls and CLI automation.

Review references/api_guide.md for current official endpoints and constraints.
Provide credentials through OpenClaw skill config or secure environment injection.
Generate an authorization URL: bash scripts/weibo_cli.sh oauth-authorize-url
Exchange code for a token: bash scripts/weibo_cli.sh oauth-access-token --code "<code>"
Call endpoints: bash scripts/weibo_cli.sh public-timeline --count 20

Use the Bash CLI first:

scripts/weibo_cli.sh: OAuth2 + direct API command interface, optimized for agentic runs.

Optional companion skill:

weibo-brave-search: separate fallback skill for site:weibo.com search through Brave Search API.

Validate provider requirements in references/api_guide.md.
Run oauth-authorize-url, open URL, capture code.
Run oauth-access-token --code ... and store token securely.
Use endpoint helpers (public-timeline, user-timeline, search-topics) or call.
If API access is blocked and you explicitly want a separate commercial fallback, use the weibo-brave-search skill instead of this one.

Run bash scripts/weibo_cli.sh --help for details.

Credential classes:

Variable	Required	Sensitive	Used for
`WEIBO_APP_KEY`	Yes	No	OAuth client identifier
`WEIBO_APP_SECRET`	Yes	Yes	OAuth token exchange
`WEIBO_REDIRECT_URI`	Yes	No	OAuth callback
`WEIBO_ACCESS_TOKEN`	Optional	Yes	Authenticated API calls after token issuance

OpenClaw configuration guidance:

Set skills.entries.weibo.apiKey to a SecretRef or plaintext value only for WEIBO_APP_SECRET, because this skill declares WEIBO_APP_SECRET as its primaryEnv.
Set skills.entries.weibo.env.WEIBO_APP_KEY and skills.entries.weibo.env.WEIBO_REDIRECT_URI as regular env config.
If you want pre-issued token flows, set skills.entries.weibo.env.WEIBO_ACCESS_TOKEN from your external secret manager or deployment environment.

Warnings:

WEIBO_APP_SECRET and WEIBO_ACCESS_TOKEN are sensitive and must not be committed.
OpenClaw's documented SecretRef audit path covers skills.entries.<skillKey>.apiKey; it does not give the same visibility for arbitrary ad hoc env vars.
If you inject WEIBO_ACCESS_TOKEN through plain environment variables, store it in your external secrets manager or deployment environment and do not treat it as registry-managed unless you have configured it that way intentionally.
This skill makes network calls to https://api.weibo.com.

Prefer JSON output for downstream automation.
Keep requests minimal and paginated to reduce rate-limit pressure.
Use the official docs linked in references/api_guide.md as source of truth when endpoint behavior conflicts with old SDK examples.