SKILLEMALL.ai

BF xiaohongshu-ops

小红书相关操作,覆盖账号定位、选题研究、内容生产、发布执行与复盘修复的小红书全链路运营技能。凡是小红书的浏览/搜索/发布/评论任务,默认必须使用 OpenClaw 内置浏览器流程并指定 profile="openclaw";除非用户明确要求,否则不要使用系统 open 或外部浏览器。

ClawHub Agent Skills author: ZOOZOO v0.1.2 MIT-0 16 files body ≈ 1 063 tokens Open the sourceclawhub.ai analyzed 5 d ago

As a process F 33/100 · Will not run — References files that are not bundled: examples/<vertical>/<vertical>.md, examples/<vertical>/README.md, examples/lifestyle/

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: examples/<vertical>/<vertical>.md, examples/<vertical>/README.md, examples/lifestyle/
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ClawHub

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: examples/<vertical>/<vertical>.md
  • warning missing-ref reference to a missing file: examples/<vertical>/README.md
  • warning missing-ref reference to a missing file: examples/lifestyle/
  • warning missing-ref reference to a missing file: examples/cosmetics/
  • warning missing-ref reference to a missing file: examples/fitness/

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: examples/<vertical>/<vertical>.md, examples/<vertical>/README.md, examples/lifestyle/
  • 0Tools and files. 5 referenced file(s) missing: examples/<vertical>/<vertical>.md, examples/<vertical>/README.md, examples/lifestyle/
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 100Steps. 94 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1063 tokens
  • low 19 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 142: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 94 items
  • +4Reference files are cited in the instructions (9 of 9)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.

External checks

ClawHub: suspicious
This skill mostly matches Xiaohongshu account operations, but needs review because it can act through a logged-in social account while persisting and potentially sharing account/feed data without tight user-controlled boundaries.
LLM: suspicious (high) · VirusTotal: benign · 27 May 2026