Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use Weibo Open Platform for OAuth2 authentication, timeline retrieval, topic search, and structured social sentiment collection. Trigger this skill when task...
Use Weibo Open Platform for OAuth2 authentication, timeline retrieval, topic search, and structured social sentiment collection. Trigger this skill when task...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
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.
oauth-authorize-url oauth-access-token --code <code> oauth-token-info public-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.
Credential classes: VariableRequiredSensitiveUsed forWEIBO_APP_KEYYesNoOAuth client identifierWEIBO_APP_SECRETYesYesOAuth token exchangeWEIBO_REDIRECT_URIYesNoOAuth callbackWEIBO_ACCESS_TOKENOptionalYesAuthenticated 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.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.