Use this skill to collect Weibo signals with reproducible Weibo Open Platform API calls and CLI automation.
Quick Start
- 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
codefor a token:bash scripts/weibo_cli.sh oauth-access-token --code "<code>" - Call endpoints:
bash scripts/weibo_cli.sh public-timeline --count 20
Primary Interface
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 forsite:weibo.comsearch through Brave Search API.
Recommended Workflow
- Validate provider requirements in references/api_guide.md.
- Run
oauth-authorize-url, open URL, capturecode. - Run
oauth-access-token --code ...and store token securely. - Use endpoint helpers (
public-timeline,user-timeline,search-topics) orcall. - If API access is blocked and you explicitly want a separate commercial fallback, use the
weibo-brave-searchskill instead of this one.
CLI Command Surface
oauth-authorize-urloauth-access-token --code <code>oauth-token-infopublic-timeline [--count N] [--page N]user-timeline --uid <uid> [--count N]search-topics --q <query>call --method GET --path /2/... --param key=value
Run bash scripts/weibo_cli.sh --help for details.
Credentials And Secret Handling
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.apiKeyto aSecretRefor plaintext value only forWEIBO_APP_SECRET, because this skill declaresWEIBO_APP_SECRETas itsprimaryEnv. - Set
skills.entries.weibo.env.WEIBO_APP_KEYandskills.entries.weibo.env.WEIBO_REDIRECT_URIas regular env config. - If you want pre-issued token flows, set
skills.entries.weibo.env.WEIBO_ACCESS_TOKENfrom your external secret manager or deployment environment.
Warnings:
WEIBO_APP_SECRETandWEIBO_ACCESS_TOKENare sensitive and must not be committed.- OpenClaw's documented
SecretRefaudit path coversskills.entries.<skillKey>.apiKey; it does not give the same visibility for arbitrary ad hoc env vars. - If you inject
WEIBO_ACCESS_TOKENthrough 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.
Notes
- 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.