Category demand map

RedSkill Content Creation Xiaohongshu Skills Demand

27 of the 136 public rows in our snapshot sit in Content creation. Highest-scoring entries include Xhs Note Creator, Xhs Content Creator, Auto Redbook Skills.

How we read this cluster

This is the widest and most commoditised cluster in the snapshot. Most rows rewrite, expand or restructure text a creator already owns, so the marginal value sits in the review loop around the skill rather than in the skill itself. Two creators who install the same note-writing skill will get near-identical drafts unless one of them wraps it in a brand voice file, a claim list and a human approval step.

Because the output is prose, mistakes are cheap to catch and cheap to undo. Treat the risk here as editorial rather than operational: the failure mode is publishing a bland or off-brand note, not losing an account.

How demand is distributed

27Rows
7,887Downloads
41Installs
0.5%installs per download

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

Risk mix

Low 25 Medium 2 High 0

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-note-creator 1,659 15 Low
xhs-content-creator 1,092 13 Low
auto-redbook-skills 1,933 3 Low
xiaohongshu-title 1,236 3 Low
xhs-viral-note-writer 292 2 Low

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