Category demand map

RedSkill Data and Analytics Xiaohongshu Skills Demand

18 of the 136 public rows in our snapshot sit in Data and analytics. Highest-scoring entries include Xiaohongshu Cn, Xiaohongshu Deep Research, Xiaohongshutools.

How we read this cluster

Research and measurement rows: trend tracking, keyword surfaces, comment mining, competitor snapshots. Nothing here publishes on your behalf, yet none of it is labelled Low either — which is the interesting part. Reading at volume is its own category of risk, because volume is what platform terms tend to constrain, regardless of intent.

The practical test is not whether a scraper works. It is whether you can keep it working without escalating your request rate every time the source changes shape. Budget for breakage rather than assuming a stable interface, and read the terms before you scale a collection job from a one-off experiment into a schedule.

How demand is distributed

18Rows
10,089Downloads
66Installs
0.7%installs per download

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

Risk mix

Low 0 Medium 10 High 8

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
xiaohongshu-cn 2,630 26 Medium
xiaohongshu-deep-research 2,131 24 Medium
xiaohongshutools 3,876 11 Medium
xiaohongshu-extract 527 0 High
xiaohongshu-reply-assistant 317 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