weibo — Claude Code skill: read and post on Weibo with your cookies
weibo reads and posts on 微博 through your own login cookie: recent entries with repost, comment and like counts, plus publishing a new one.
Apache-2.0 180 installs ★ 17 updated 2026-10-25
npx skills add AceDataCloud/Skills --skill weibo -a claude-codeWhat weibo does
It calls the same weibo.com/ajax endpoints the site itself uses and authenticates with the login cookie you captured through the ACE extension. No browser sits in between. The bundled scripts/weibo.py runs on the Python standard library.
whoami reports the account behind the cookie. posts --limit 20 returns recent 微博 with reposts_count, comments_count and attitudes_count. For publishing, post --content "..." dry-runs the text, and --confirm as the final argument sends it for real.
It was written against the documented web API with no live account to test on, so the first real run doubles as the check. A confirmed 微博 goes public right away, and there is no draft or private mode to fall back on. If whoami returns an auth error the cookie has expired: reconnect at https://studio.acedata.cloud/console/connectors instead of retrying in a loop.
What it helps with
- see how recent 微博 posts performed on reposts, comments and likes
- check which account the stored cookie belongs to
- publish a short post to 微博 from the terminal
- dry-run the exact text and approve it before it goes live
Example prompts for the agent
- Show my last 20 Weibo posts with repost, comment and like counts
- Post this to Weibo, but show me the dry run and wait for my yes
- Which Weibo account am I logged in as?
How to install weibo
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill weibo -a claude-code2Manually: put the files in place
~/.claude/skills/weibo/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/weibo/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill weibo -a codex2Manually: put the files in place
.agents/skills/weibo/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill weibo -a cursor2Manually: put the files in place
.cursor/skills/weibo/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/weibo2Manually: put the files in place
.github/skills/weibo/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill weibo -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/weiboManually: put the files in place
.devin/skills/weibo/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill weibo -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about weibo
How do I install weibo in Claude Code?
Run npx skills add AceDataCloud/Skills --skill weibo -a claude-code. The skill lands at ~/.claude/skills/weibo/SKILL.md.
What does the weibo skill do?
It reads and posts on 微博 as you: lists recent entries with repost, comment and like counts, then publishes new text once you approve it.
What do I need before using it?
A 微博 login cookie, which the connector injects as WEIBO_COOKIES, and python3. That cookie is full account access, so keep it out of the chat.
Source text
SKILL.md · Apache-2.0
---
name: weibo
description: Read and post on 微博 / Weibo (weibo.com) with the user's own login cookies (BYOC) — list their recent posts with repost/comment/like counts and publish a new 微博. Use when the user mentions 微博 / Weibo, "我的微博", reading their post engagement, or 发微博 / posting to Weibo.
when_to_use: |
Trigger for anything on the user's 微博 (weibo.com) account driven by their own
login cookie: show who they are, list their recent 微博 with repost / comment /
like counts, or publish a new 微博. This acts as the user's real account, so
posting is gated behind an explicit confirmation.
connections: [weibo]
allowed_tools: [Bash]
license: Apache-2.0
metadata:
author: acedatacloud
version: "1.0"
connection_method_preferences:
weibo/weibo: [cookie]
---
# weibo — read & post on 微博 via your own cookies
Drives the user's **real** 微博 account through the same `weibo.com/ajax` web API
the site uses, authenticated by the login cookie they captured with the ACE
extension. No browser, no third-party deps — just `urllib`.
> ⚠️ **Not yet E2E-verified.** Unlike the other cookie skills (csdn / juejin /
> bilibili / medium), this one was built from the documented web API but could
> not be tested against a live account (no 微博 connection existed at build
> time). The first live run is the verification; if an endpoint shape drifted it
> will surface as a clear error rather than silent breakage.
The connector injects the cookie jar as an env var:
- `WEIBO_COOKIES` — a JSON array of cookies. **Secret — never echo or print it.**
Writes send the `XSRF-TOKEN` cookie as both the `x-xsrf-token` header and the
`st` form field (the CLI does this for you).
## CLI
The skill ships [`scripts/weibo.py`](scripts/weibo.py) — self-contained, stdlib only.
```sh
# $SKILL_DIR can point at another skill loaded this turn — anchor on our own
# script, and re-run this at the top of every Bash block (fresh shell each time).
WB="$SKILL_DIR/scripts/weibo.py"; [ -f "$WB" ] || WB=$(find /tmp -maxdepth 8 -path '*/skills/*/scripts/weibo.py' 2>/dev/null | head -1)
[ -f "$WB" ] || { echo "weibo script not found (SKILL_DIR=$SKILL_DIR)" >&2; exit 1; }
python3 "$WB" whoami # who is logged in (+ counts)
python3 "$WB" posts --limit 20 # my recent 微博 + engagement
```
Engagement comes straight from 微博: `reposts_count` (转发), `comments_count`
(评论), `attitudes_count` (赞).
## Verify the connection first
```sh
WB="$SKILL_DIR/scripts/weibo.py"; [ -f "$WB" ] || WB=$(find /tmp -maxdepth 8 -path '*/skills/*/scripts/weibo.py' 2>/dev/null | head -1)
python3 "$WB" whoami
# → {"uid": "...", "name": "...", "statuses_count": ...}
```
On an auth error the cookie is expired — have the user reconnect at
<https://studio.acedata.cloud/console/connectors>. Do **not** loop-retry.
## Posting — GATED (dry-run unless trailing `--confirm`)
微博 are short-form, so there is **no draft step** — a confirmed post goes live.
Without a trailing `--confirm` it dry-runs. `--confirm` is honored **only as the
last argument**. Always show the dry-run, get an explicit "yes", then re-run.
```sh
WB="$SKILL_DIR/scripts/weibo.py"; [ -f "$WB" ] || WB=$(find /tmp -maxdepth 8 -path '*/skills/*/scripts/weibo.py' 2>/dev/null | head -1)
python3 "$WB" post --content "你好,这是一条微博" # dry-run
python3 "$WB" post --content "你好,这是一条微博" --confirm # PUBLIC 微博 (immediate)
```
- There is **no draft and no private mode** on 微博 — a confirmed post is
immediately **public**. Always show the dry-run and get explicit approval of
the exact text before adding `--confirm`.
## Gotchas
- **This is the user's real 微博 account.** Confirm before any post — it is
immediate and public by default.
- **Not E2E-verified** (see the warning above) — expect to validate the first run.
- **Never print `WEIBO_COOKIES`** — it is full account access.
- **ToS**: acts only on the user's own account with their own captured cookie.
© acedatacloud · Apache-2.0 · AceDataCloud/Skills