Category demand map

RedSkill Interaction Xiaohongshu Skills Demand Map

5 of the 136 public rows in our snapshot sit in Interaction and comments. Highest-scoring entries include Xhs Auto Reply, Xiaohongshu Comment, Xhs Note Health.

How we read this cluster

A small cluster with an outsized risk per row. Replies, likes and comment flows are individually trivial and collectively the clearest example of behaviour a platform reads as automation.

There is no version of this cluster we would recommend running unattended. Keep the skill at drafting suggested replies and let a person send them.

How demand is distributed

5Rows
268Downloads
0Installs
0.0%installs per download

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

Risk mix

Low 0 Medium 0 High 5

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
xhs-auto-reply 129 0 High
xiaohongshu-comment 133 0 High
xhs-note-health 6 0 High
phy-xiaohongshu-gtm 0 0 High
xiaohongshu-proxy-manager 0 0 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