<< All versions

Skill v1.0.1

currentAutomated scan100/100
qinyuanpei/mcp-server-weibo/weibo-personality

+3 new

──Details
PublishedSeptember 26, 2026 at 07:00 AM
Content Hashsha256:60c78b59448104b3...
Git SHAa98f61159004
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 2.8 KB)
SKILL.md2.8 KBactive
SKILL.md · 48 lines · 2.8 KB

version: "1.0.1"



name: weibo-personality description: Generate a horoscope-style personality report for a Weibo user. Fetch the user's profile and recent posts with weibo-cli, then act as the LLM yourself - apply the bundled prompt template and deliver a Chinese JSON report plus a readable summary. Use when the user asks to analyze a Weibo personality, generate a Weibo profile report or personality analysis, or provides a Weibo UID/name for personality analysis.


Weibo Personality Report

Turn a Weibo user's public profile and recent posts into an entertainment-grade personality report: strengths, weaknesses, love/money/health predictions, pickup lines, roast, and more. You are the LLM - no API key, no backend service. Data comes from the Weibo CLI, reasoning comes from you.

Prerequisites

Workflow

  1. Resolve the UID. If the user gives a nickname instead of a UID, find it with weibo-cli users "<name>" -n 5. Verify by description and follower count; confirm with the user when ambiguous.
  2. Fetch the profile.

``bash weibo-cli profile <uid> ``

  1. Fetch posts.

``bash weibo-cli feeds <uid> -n 50 --no-include-pics ``

  • Prefer each item's raw_text; otherwise strip HTML tags from text.
  • Known limit: guest sessions return only the ~10 most recent posts. For a deeper report, ask the user to run weibo-cli login (QR scan), then retry with -n 50.
  • If the user asks for a time window (e.g. last six months), drop older posts after fetching and say how many posts survived.
  1. Generate the report. Fill the template's profile and tweets slots with the fetched data, follow the output schema exactly, and write all generated content in Chinese.
  • name, avatar_hd, description, profile_url, follow_count, followers_count must be copied from the fetched profile. Never invent them.
  1. Deliver. Present a readable formatted report first. Offer the raw JSON as a follow-up (save to file or inline) rather than dumping it by default.

Guardrails

  • This is horoscope-style entertainment, not a psychological assessment. Say so when delivering the report.
  • Only analyze public accounts. Refuse locked/private accounts.
  • The roast should be edgy and witty about the persona's expressed traits - never slurs, never attacks on protected characteristics.
  • Ground every claim in the fetched posts. If the sample is small (fewer than ~15 posts), say so and note the report is based on a thin sample.
← v1.0.0All versions