SKILLEMALL.ai

BD content-rewriter

自媒体人必备 | 丢个视频链接,自动出小红书+头条+抖音三套可直接发布的改写文案。 支持抖音/B站/小红书。不是学术分析,是"扒下来→分析为什么爆→改成你的版本"。 实测能省 80% 的爆款分析时间。花大叔出品。 触发场景:分析视频文案、视频文案改写、扒文案改文章、爆款分析、 内容改写、文案提取改写、视频转文章、爆款拆解、改写输出、一键扒爆款、 自媒体文案、小红书爆款、今日头条改写、短视频文案、内容搬运、仿写、 选题拆解、对标账号分析、文案去重、二创改写

ClawHub Hermes author: roseryztzhoutong v0.6.1 MIT-0 3 files body ≈ 1 823 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
D
41/100
Unfinished process
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.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 230 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "display_name"
  • note frontmatter-key unknown frontmatter key "agent_created"

Process rating: all ten parameters 41/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
  • 40Consistency. Frontmatter name (content-rewriter) differs from the folder (yijian-ba-baokuan)
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 36 steps
  • 100Execution cost. Instruction body is 1823 tokens
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 229: enough signal without eating the budget
  • +4Structure: 24 headings
  • +3Step-by-step instructions: 36 items
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: suspicious
The skill is mostly a disclosed content-extraction and rewriting workflow, but it asks users to use platform cookies and downloader-based scraping while giving inconsistent download/data-handling guidance.
LLM: suspicious (medium) · VirusTotal: · 28 May 2026