SKILLEMALL.ai
GitHub ↗ RU Sign in

BC kay-xhs

小红书全自动内容创作工作流 - 从爆款研究到草稿发布的完整 pipeline。 使用场景：(1) 研究小红书爆款笔记风格和趋势，(2) 生成 AI 图片/漫画/封面，(3) 自动发布到小红书草稿箱。 **依赖**: 需要安装 kay-image skill 并配置 KIE_API_KEY

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 6 files body ≈ 4 096 tokens Open the sourcegithub.com↗ analyzed 2 d ago

小红书全自动内容创作工作流 - 从爆款研究到草稿发布的完整 pipeline。 使用场景：(1) 研究小红书爆款笔记风格和趋势，(2) 生成 AI 图片/漫画/封面，(3) 自动发布到小红书草稿箱。 依赖: 需要安装 kay-image skill 并配置 KIEAPIKEY

As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
66
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration read-dotenv SKILL.md:33
    Reads a .env file
    cp skills/kay-image/.env.example skills/kay-image/.env

Files scanned: 6. 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")

Process rating: all ten parameters 52/100

  • 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
  • 70Execution cost. Instruction body is 4096 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 108 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations

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
  • -283 emoji in the instructions: noise for the model
  • -42 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 145: enough signal without eating the budget
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 108 items
  • +4Has examples (29 code blocks)

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