SKILLEMALL.ai

BF xiaohongshu-ops

End-to-end Xiaohongshu operations including positioning, topic research, content production, publish execution, and post-incident recovery. Reusable across verticals with templates and a concrete 陪你看剧 case preset.

modbender/skill-library-mcp Agent Skills author: modbender MIT 11 files body ≈ 774 tokens Open the sourcegithub.com analyzed 2 d ago

End-to-end Xiaohongshu operations including positioning, topic research, content production, publish execution, and post-incident recovery.

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/

TemplateInfrastructureMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
78/100
safety, quality, tests
Safety 60%
90
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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Dangerous commands cmd-pipe-to-shell-known-host Openclaw一键安装.md:37
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -fsSL https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.0/install.sh | bash
  • medium Broad scope meta-agent-memory-dump SOUL.md
    Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
    SOUL.md

Files scanned: 11. 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. 73 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 774 tokens
  • low 15 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 213: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 73 items
  • +4Reference files are cited in the instructions (4 of 4)

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