Category demand map

RedSkill Login and CLI Xiaohongshu Skills Demand Map

19 of the 136 public rows in our snapshot sit in Login, MCP, Mac and CLI. Highest-scoring entries include Rednote, Xiaohongshu Mcp Skill, Xhs Mac Mcp.

How we read this cluster

This cluster is about plumbing: session handling, local clients, and MCP servers that expose Xiaohongshu actions as tools to an agent. Worth flagging explicitly — the official RedSkill install document never mentions MCP, so MCP-based rows in this snapshot come from the wider agent ecosystem rather than from the platform's own distribution path.

These rows are the ones most likely to hold credentials. Before installing, find out where the session token is written and whether anything transmits it anywhere other than the platform itself.

How demand is distributed

19Rows
6,128Downloads
36Installs
0.6%installs per download

The single highest-scoring row accounts for 41% of this cluster's downloads.

Risk mix

Low 0 Medium 0 High 19

These labels ship with the snapshot. They are not an official grading and they are not ours. Our reading is to treat the label as a question: does this row only read public content, or does it need your session, or does it publish for you? Low roughly means "never touches your account"; High roughly means "touches it in a way other people can see".

Top rows by opportunity score

SkillDownloadsInstallsRisk
rednote 2,502 10 High
xiaohongshu-mcp-skill 1,053 10 High
xhs-mac-mcp 318 4 High
rednote-cli 323 3 High
browser-relay-xiaohongshu 519 1 High

Where these numbers come from

Every row in this snapshot resolves to the same aggregated source page: gitcode.csdn.net. The dataset carries no per-row provenance, so this page does not pretend otherwise. Verify any skill against its own repository or official documentation before installing it.

How to verify a row before you install it

  1. Check the skill's own repository or documentation. The shared source page behind this snapshot is a starting point; it is not evidence that the row is still maintained.
  2. Read the risk label as an action question: does it only read public content, or does it need a logged-in session, or does it publish on your behalf?
  3. Run it once in an isolated session or a test account. Do not make the first attempt on your main account.
  4. Write down the single smallest thing you want it to do, then check only that after the first run.

Related research